Compliance Software Audit Trails: Mandatory Content 2026
TL;DR
- Per log entry: UTC timestamp, user ID, action (read/write/delete), affected record (hash), result, IP address
- GDPR: log access to personal data; for special categories add purpose annotation
- NIS2: privileged-access logs, configuration changes, failed logins; 90 days operational plus 12 months archive
- Whistleblower Protection (HinSchG): every action in reporting-channel software; immutable; retain 3 years after case closure
- Evidentiary value: immutable (append-only) logs plus hash-chains and time-stamping carry the strongest weight in court
1. Mandatory content per log entry
Timestamp in UTC, user ID, action (read / write / delete / export), affected record (hashed identifier rather than raw data), result (success / fail), source IP address. For privileged actions add session ID and approval reference.
2. GDPR-specific requirements
Log access to personal data. For special categories under Art. 9 GDPR (health, biometric, religion): add purpose annotation. Retention typically 3-10 years depending on the underlying processing activity. Logs themselves are personal data and need their own retention concept.
3. NIS2-specific requirements
Privileged-access logs, configuration changes, failed login attempts. Retention: 90 days operational plus 12 months archive (per BSI guidance under Section 30 BSIG, the German Cybersecurity Act). SIEM integration expected for organizations within scope.
4. Whistleblower Protection (HinSchG) requirements
Every action in reporting-channel software (read access, status change, comment) must be logged. Logs must be immutable. Retain 3 years after case closure under Section 11 HinSchG. Confidentiality protections apply: only the case owner may see who accessed which case.
5. Tooling options
Microsoft Sentinel (included in M365 E5), ELK stack (open-source, self-hosted), Splunk (enterprise), Datadog (mid-market). For SMEs: Sentinel is usually the path of least resistance if M365 is already in place.
6. Evidentiary value in court
Immutable logs (append-only with cryptographic chaining) carry stronger evidentiary weight than mutable logs. Hash chains plus qualified time-stamping provide the highest level of integrity evidence. For HinSchG and DPIA-relevant processing, immutability is the practical baseline.
Summary
Audit Trails are the backbone of defensible compliance. Each domain (GDPR, NIS2, HinSchG) layers its own requirements on top of a common baseline (timestamp, user, action, record, result, IP). Use a SIEM or equivalent log platform; for HinSchG and high-risk GDPR processing, prefer immutable storage.
View Compliance-Kit overview →
Frequently Asked Questions
How long must they be retained?
Tool for SMEs?
Sources
- Regulation (EU) 2016/679 (GDPR) — Art. 5(2), Art. 32 logging (As of: 2026-05-02)
- BSI Act 2025 (BSIG) — Section 30 risk management (As of: 2026-05-02)
- HinSchG Section 11 — documentation and retention (As of: 2026-05-02)