AL-JANEF/janef-forge / skills/security/security-logging
security-logging
VerifiedDesign and review security audit logging and detection: record who did what and when for auth events, data changes, and admin actions; never log passwords, tokens, or PII; keep logs tamper-evident; add a few high-value alerts such as failed-login thresholds. Use for audit trails, log redaction, monitoring, or incident investigation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.8 KB |
| capability.json | config | 1.9 KB |
| references/patterns.md | markdown | 3.1 KB |
| references/privacy-and-retention.md | markdown | 1.2 KB |
references/privacy-and-retention.md
View on GitHub# Privacy and Retention
Security logs must be useful without becoming a permanent collection of personal
data. Treat IP addresses, user identifiers, device identifiers, and location as
sensitive operational data even when they are not application secrets.
## Minimize
- Record only fields needed for a defined detection or investigation use case.
- Prefer stable internal actor IDs over names or email addresses.
- Truncate or pseudonymize IP addresses when exact values are unnecessary.
- Do not copy request bodies or database records into audit events.
## Retain deliberately
Set a documented retention period based on incident-response needs and applicable
legal requirements. Apply shorter retention to high-volume or more identifying
telemetry. Expire data automatically; an unwritten "keep forever" policy is not a
policy.
## Restrict and audit access
Limit log access to operational roles that need it, record access to sensitive
audit data, encrypt transport and storage, and separate production logs from
developer-facing diagnostics.
## Verify
Sample emitted events and confirm that sensitive fields are absent or minimized.
Test retention deletion and access controls rather than relying on configuration
screenshots alone.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |