Security Log
What is Security Log?
A record of security-relevant events generated by operating systems, applications, and network devices for monitoring and audit purposes.
Terms that appear alongside security log
Each of these is named in at least one of the same controls as security log. The number is how many controls name both.
- log management 3 shared controls
- incident response 2 shared controls
- policy 2 shared controls
Frameworks that govern security log
What the standards actually require on security log
Requirements naming security log across 5 standards, quoted from the control text.
Aggregate security logs in Microsoft Sentinel or equivalent SIEM with documented detection rules and analyst workflows.
LT-5 · Centralize security log management and analysis →Collect and review SCADA security logs and operational anomalies to detect potential cyber incidents.
API1164-11 · Logging and Monitoring →Establish a log management programme per NIST SP 800-92 Chapter 2 (Introduction to Computer Security Log Management) + Chapter 4 (Log Management Planning).
NISTSP92-1 · Log Management Programme, Policy, Roles, and Operational Runbooks →Operate logging + monitoring + incident response + DoS resilience per O-RAN WG11 Security Log Management Specifications and incident response specifications.
ORANWG11-7 · Logging, Monitoring, Incident Response, and Denial-of-Service Resilience →Implement security monitoring including IDS/IPS, SIEM, and log analysis. Retain security logs for at least 1 year. Review logs regularly for anomalies.
ISMSP-SYS-03 · Security Monitoring and Log Management →Questions people ask about security log
What is Security Log?
Why is Security Log important for compliance?
Which compliance frameworks address Security Log?
Where can I learn more about Security Log?
See how Security Log applies across compliance frameworks
Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.