LOG-13 Access Control Logs
Monitor and record physical access through an access control system whose records can be audited.
Source: CSA CCM v4.1, LOG-13. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Badge system access logs for data centre and sensitive areas · Physical access / facilities
- Retention settings for physical access logs · Physical access / facilities
- Alerts for forced doors or denied access · SIEM / log platform
periodic reviewEvidence produced at each review
- Physical access log review records · Physical access / facilities
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Visitor access recorded on paper and not reconciled
- Logs not reviewed
- Shared badges in use
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetLOG-12 Transaction/Activity Logging · LOG-14 Failures and Anomalies Reporting