Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Produce, store, protect and analyse logs of activities, exceptions and security events.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Teams should treat logs as evidence-bearing records, not just technical noise. The emphasis is on deciding what must be logged, who reviews it, how integrity is protected, and which events require escalation into incident handling or corrective action. Tie logging to time synchronisation and access control, because logs that cannot be trusted for sequence, source, or immutability often become weak evidence during investigation or review.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Important systems log authentication, privilege changes, and security events, but the policy omits review ownership, so nobody is accountable for investigating anomalies.
Log retention is shorter than the business need for investigations or legal requests, leaving gaps in retrospective analysis and response evidence.
Administrative users can alter or delete logs on the same host they manage, undermining trust in records and weakening incident reconstruction.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Define log sources by risk: identity systems, privileged actions, critical servers, cloud control planes, firewalls, remote access, and security tools. The logging policy should say what is mandatory, what is conditional, and what can be sampled. Give the SOC, system owner, or service desk a clear review route so alerts are not orphaned.
Specify retention, protection, and integrity controls in operational terms. Use central collection, restricted write access, tamper-evident storage, and role-separated administration. If a platform allows local log deletion, add compensating controls such as forwarding to a separate repository and monitoring for missing-event patterns or time gaps.
Define review cadence that fits the threat and business impact. Daily review may apply to privileged access and security exceptions, while lower-risk operational events can be reviewed weekly. Each review should record what was checked, what threshold or rule triggered attention, and whether an incident, problem ticket, or false positive was raised.
Link logging outputs to incident management and corrective action. When a review identifies a repeated configuration fault or suspicious pattern, preserve relevant records, assign a responder, and log the containment decision. Use management review to assess whether log coverage still matches the environment after new services, cloud changes, or remote work expansion.
What an auditor will ask to see
Logging & Monitoring Policy defining event classes, ownership for review, retention periods, protection requirements, and escalation paths.
SIEM or central logging dashboard extracts showing source systems onboarded, alert rules active, and evidence of missing-log detection.
Weekly or daily log review records with reviewer name, date, exceptions observed, incident references, and closure notes.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.15. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.