20 May 2026 4 min read Security
What to log and monitor so you can detect, report and prove handling of security events.
What to capture
- Security-relevant events (auth, config change, update).
- Enough context to investigate.
- Tamper-resistant, time-synced records.
Why it matters for compliance
Reporting duties under the CRA and NIS2 assume you can detect and reconstruct incidents. Logs are the foundation.
Mind privacy
Balance logging with GDPR data-minimisation — log what you need, protect what you keep.
This is an educational explainer. For the canonical regulation reference, see the dedicated Security page — or run an assessment to see how it applies to your product.