# 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: Media 3 lenguajes cubiertos
- Impact: Alto 1 reglas de severidad alta
- Prevention: Documentada 3 ejemplos de corrección

**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

Estrategias de prevención para Information Exposure Through Logs basadas en 1 reglas de detección de Shoulder.

### Go

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

## Consequences

- Leer datos de la aplicación
- Obtener privilegios

## Mitigations

- Nunca registres información sensible como contraseñas o tokens
- Implementa clasificación y filtrado de los datos de log
- Enmascara o redacta los datos sensibles antes de registrarlos

## 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