# Insertion of Sensitive Information into Log File (CWE-532)

Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.

**Stack:** Go

- Prevalence: Moyenne 3 langages couverts
- Impact: Élevé 1 règles de sévérité élevée
- Prevention: Documentée 3 exemples de correctifs

**OWASP:** Security Logging and Monitoring Failures (A09:2021-Security Logging and Monitoring Failures) - #9

## Description

When sensitive information like passwords, tokens, or personal data is logged, it becomes accessible to anyone with access to the logs. Log files are often stored with less security than the data they contain.

## Prevention

Stratégies de prévention pour Information Exposure Through Logs basées sur 1 règles de détection Shoulder.

### Go

Never log passwords, tokens, or PII; log presence/absence instead

## Consequences

- Lecture des données de l'application
- Obtenir des privilèges

## Mitigations

- Ne journalisez jamais d'informations sensibles telles que mots de passe ou jetons
- Mettez en place la classification et le filtrage des données de journal
- Masquez ou expurgez les données sensibles avant de les journaliser

## Detection

- Total rules: 3
- Languages: go, javascript, typescript, python

## Rules by Language

### Go (1 rules)

- **Logging Sensitive Data** [MEDIUM]: Passwords, tokens, or PII logged via log.Printf or similar functions.
  - Remediation: Never log sensitive values. Log presence/absence instead of actual values.

```go
// Log only that API key is configured, not the value
if apiKey != "" {
    log.Println("API key configured")
}
```

Learn more: https://shoulder.dev/learn/go/cwe-532/sensitive-data-logging