How do I install the 047 Threat E2ab4fb7 skill?

Run npx skillmds@latest add tools-only/047-threat-e2ab4fb7 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the 047 Threat E2ab4fb7 skill do?

It is listed under Security on SkillMD.

Is 047 Threat E2ab4fb7 safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 047 Threat E2ab4fb7?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 047 Threat E2ab4fb7 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published 047 Threat E2ab4fb7?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

047 Threat E2ab4fb7 by tools-only — Agent Skill

Name: 047 Threat E2ab4fb7
Author: tools-only

File contents

description: Logging & monitoring (structured telemetry, redaction, integrity, detection & alerting) languages:

c
javascript
yaml alwaysApply: false

rule_id: codeguard-0-logging

Logging & Monitoring

Produce structured, privacy‑aware telemetry that supports detection, response, and forensics without exposing secrets.

What to Log

Authn/authz events; admin actions; config changes; sensitive data access; input validation failures; security errors.
Include correlation/request IDs, user/session IDs (non‑PII), source IP, user agent, timestamps (UTC, RFC3339).

How to Log

Structured logs (JSON) with stable field names; avoid free‑form text for critical signals.
Sanitize all log inputs to prevent log injection (strip CR/LF/delimiters); validate data from other trust zones.
Redact/tokenize secrets and sensitive fields; never log credentials, tokens, recovery codes, or raw session IDs.
Ensure integrity: append‑only or WORM storage; tamper detection; centralized aggregation; access controls and retention policies.

Detection & Alerting

Build alerts for auth anomalies (credential stuffing patterns, impossible travel), privilege changes, excessive failures, SSRF indicators, and data exfil patterns.
Tune thresholds; provide runbooks; ensure on‑call coverage; test alert flows.

Storage & Protection

Isolate log storage (separate partition/database); strict file/directory permissions; store outside web‑accessible locations.
Synchronize time across systems; use secure protocols for transmission; implement tamper detection and monitoring.

Privacy & Compliance

Maintain data inventory and classification; minimize personal data in logs; honor retention and deletion policies.
Provide mechanisms to trace and delete user‑linked log data where required by policy.

Implementation Checklist

JSON logging enabled; log injection sanitization active; redaction filters active; correlation IDs on all requests.
Isolated log storage with tamper detection; centralized log pipeline with integrity protections; retention configured.
Security alerts defined and tested; dashboards and reports in place.

Validation

Unit/integration tests assert presence/absence of key fields; redaction unit tests.
Periodic audits for secret/PII leakage; tabletop exercises for incident workflows.

---name: 047-threat-e2ab4fb7description: ------description: Logging & monitoring (structured telemetry, redaction, integrity, detection & alerting)languages:- c- javascript- yamlalwaysApply: false---rule_id: codeguard-0-logging## Logging & MonitoringProduce structured, privacy‑aware telemetry that supports detection, response, and forensics without exposing secrets.### What to Log- Authn/authz events; admin actions; config changes; sensitive data access; input validation failures; security errors.- Include correlation/request IDs, user/session IDs (non‑PII), source IP, user agent, timestamps (UTC, RFC3339).### How to Log- Structured logs (JSON) with stable field names; avoid free‑form text for critical signals.- Sanitize all log inputs to prevent log injection (strip CR/LF/delimiters); validate data from other trust zones.- Redact/tokenize secrets and sensitive fields; never log credentials, tokens, recovery codes, or raw session IDs.- Ensure integrity: append‑only or WORM storage; tamper detection; centralized aggregation; access controls and retention policies.### Detection & Alerting- Build alerts for auth anomalies (credential stuffing patterns, impossible travel), privilege changes, excessive failures, SSRF indicators, and data exfil patterns.- Tune thresholds; provide runbooks; ensure on‑call coverage; test alert flows.### Storage & Protection- Isolate log storage (separate partition/database); strict file/directory permissions; store outside web‑accessible locations.- Synchronize time across systems; use secure protocols for transmission; implement tamper detection and monitoring.### Privacy & Compliance- Maintain data inventory and classification; minimize personal data in logs; honor retention and deletion policies.- Provide mechanisms to trace and delete user‑linked log data where required by policy.### Implementation Checklist- JSON logging enabled; log injection sanitization active; redaction filters active; correlation IDs on all requests.- Isolated log storage with tamper detection; centralized log pipeline with integrity protections; retention configured.- Security alerts defined and tested; dashboards and reports in place.### Validation- Unit/integration tests assert presence/absence of key fields; redaction unit tests.- Periodic audits for secret/PII leakage; tabletop exercises for incident workflows.

Frequently asked questions

047 Threat E2ab4fb7