Domain: Security and Access Control |
Level: MUST | Type: Preventive
Statement of Requirement:
Logs containing sensitive information, such as cryptographic keys or
personally identifiable information (PII), MUST be suppressed,
sanitized, or otherwise secured to prevent unauthorized access.
Ensure that sensitive data is not made available to malicious
actors
Audit Procedures
Verify that
logging procedure defines what constitutes sensitive information
(crypto keys, PII, auth tokens), how logging is prevented (suppression,
sanitization, secured categories), and responsible parties.
responsible staff understand why and how to prevent sensitive data
appearing in logs, any incidents of sensitive data in logs, and how they
would detect and respond to such incidents.
sensitive data is logged in a secured manner (e.g.,
restricted-access debug logs), with strict access controls and separate
from general logs.
Key Evidence
Sensitive data logging policy; log sanitization procedures and
configurations
Re-performance submitting PII, showing no sensitive data is
logged
Log pipeline configuration showing sanitization filters and
redaction rules
Node client configuration flags disabling verbose/debug logging of
sensitive data
Automated sensitive data detection tool outputs
Success Criteria
Policy or procedure addresses sensitive data in logs
Technical controls in place to suppress, sanitize, or secure
sensitive data
Auditor review of sampled logs finds no unprotected sensitive
data
Sensitive data stored is held securely in access-controlled
segregated streams
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
No policy or practice for handling sensitive data in logs
Cryptographic key material found in accessible logs
PII is present in general access logs
Authentication tokens or passwords appear in log entries
Common Failure Patterns
Verbose/debug logging enabled in production outputting key
material;
error stack traces include environment variables with secrets;
access logs capture full request bodies with unsanitized sensitive
data;
sanitization at aggregation layer but unsanitized logs remain on
source host;
password/token rotation events log old and new values.