# Sensitive Data in Logs

> Detects passwords, tokens, credit card numbers, and other sensitive data written to log files.

- Skill: `zakirkun/sensitive-data-in-logs` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add zakirkun/sensitive-data-in-logs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zakirkun/sensitive-data-in-logs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zakirkun (https://skillmd.com/u/zakirkun)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/zakirkun/sensitive-data-in-logs

---


# Sensitive Data in Logs

## Overview
Logging sensitive information creates secondary exposure risks:
- Log files are often stored less securely than databases
- Log aggregation services (ELK, Splunk) may have broader access
- Logs may be shipped to third parties (monitoring vendors)
- Compliance violations: PCI-DSS (card data), GDPR (PII), HIPAA (health data)

Sensitive data that must not be logged:
- Passwords, PINs, secrets
- Credit card numbers, CVV
- Authentication tokens, session IDs
- Social Security Numbers, health data

## Remediation
- Use structured logging and explicitly list safe fields
- Implement a log sanitizer/redactor middleware
- Never log request bodies wholesale — extract only safe fields
- Use `[REDACTED]` placeholders for sensitive fields