Access Log
What is Access Log?
A record of all access attempts to a system or resource, including successful and failed attempts, used for security monitoring and audit purposes.
Frameworks that govern access log
What the standards actually require on access log
Requirements naming access log across 6 standards, quoted from the control text.
Administrator access logs. Level 1: administrator and operator activities logged and reviewed regularly. Level 2: logs protected against tampering and unauthorised access and event logs kept and reviewed.
mtcs-singapore::22.9 · Administrator access logs →Logs of physical access are kept, at least in an ad hoc way, manually such as a paper register or automatically through an access control system.
australian-energy-sector-cyber-security-framework-aescsf::ACCESS-3c · ACCESS-3c: Physical access logs kept →Maintain audit logs recording physical access to facilities holding organizational systems.
PE.L2-3.10.4 · Physical Access Logs →CMMC 2.0 Level 1 (Foundational) practice PE.L1-3.10.4: Physical Access Logs - safeguarding Federal Contract Information per FAR 52.204-21(b)(1)(ix) (3.10.4).
PE.L1-3.10.4 · Physical Access Logs →Identification data may be kept in the active base while the person is authorised; access logs generated by the device should be deleted three months after recording;
cnil-guidance-on-employee-monitoring-and-workplace-video-surveillance::ACC-5 · ACC-5 Keep identification data for the authorisation period, access logs three months and time-tracking data up to five years →Retain physical access logs of entry of individuals with authorized unescorted physical access into each PSP for at least ninety calendar days.
nerc-cip::CIP-006 R1.9 · CIP-006-6 R1.9: Retain physical access logs for 90 days →Questions people ask about access log
What is Access Log?
Why is Access Log important for compliance?
Which compliance frameworks address Access Log?
Where can I learn more about Access Log?
See how Access Log applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.