Audit Logging
The short answer · 11 words
In short
Traceable recording of security-, access- or audit-relevant actions in a system.
Flow-alerta.cab (2026): Audit Logging. https://flow-alerta.cab/en/glossar/audit-logging. Editorially reviewed on: 09 October 2026.
How much detail would you like?
Practical
Basis for troubleshooting, security analysis, accountability and robust controls. However, protocols do not automatically provide protection against manipulation or legal compliance.
Example scenario: A CRM logs logging, role change, mass export and deletion with user account, time, affected object and result.
For critical actions, set protocol scope, protection, access rights, retention, alerting and periodic checking risk-based.
At a glance
- Core
- Audit logging typically captures actor, action, target object, time, outcome, and relevant context. The resulting entries form an audit trail. General application logging, telemetry and monitoring can pursue further goals.
- Use
- Basis for troubleshooting, security analysis, accountability and robust controls. However, protocols do not automatically provide protection against manipulation or legal compliance.
- Example
- Example scenario: A CRM logs logging, role change, mass export and deletion with user account, time, affected object and result.
- Limits
- Passwords, tokens or unnecessary personal data write; lack of time synchronization; too short or unlimited storage; allow logs to be changed subsequently; make no one responsible for evaluation and alarming.
Questions about this term
Is audit logging the same as monitoring?
No.
Are logs automatically tamper-proof?
No.
Does everything have to be logged?
No, scope and retention must take into account purpose, risk and data protection.
All details and background
Audit logging typically captures actor, action, target object, time, outcome, and relevant context. The resulting entries form an audit trail. General application logging, telemetry and monitoring can pursue further goals.
ELI5 – Explained simply
The system keeps a traceable logbook of who executed which important action with which result when.
Why it matters in practice
Basis for troubleshooting, security analysis, accountability and robust controls. However, protocols do not automatically provide protection against manipulation or legal compliance.
Example
Example scenario: A CRM logs logging, role change, mass export and deletion with user account, time, affected object and result.
Pitfalls and limits
- Passwords, tokens or unnecessary personal data write; lack of time synchronization; too short or unlimited storage; allow logs to be changed subsequently; make no one responsible for evaluation and alarming.
Origin & history
NIST SP 800-92 published organization-wide guidelines for the establishment and operation of log management in 2006.
Use in mid-sized companies
- For critical actions, set protocol scope, protection, access rights, retention, alerting and periodic checking risk-based.
Related terms
- SIEM
- Observability
- Incident response
Matching Flow-alerta service
Websites & web applicationsWebsites & web applications: technical implementation and testing of a suitable web application.Matching tool / use case
View use casesTools: Cloud audit logs or SIEM; Use Case: Examination of privileged data exports and role changesSources
- csrc.nist.govNIST SP 800-92, Guide to Computer Security Log Management
- csrc.nist.govNIST, Log Management Project
Quellenprüfung: 09.10.2026. Definition und dokumentierte Einordnung abgeglichen; Beispiele beschreiben mögliche Anwendungen.
Editorially reviewed on: