ISO/IEC 27001:2022·Annex A A.8.15·high·Component: Technological controls

What this control requires

Logs that record activities, exceptions, faults and other relevant events shall be produced, stored, protected and analysed.
— ISO/IEC 27001:2022, Annex A A.8.15

In plain English

Logs that record activities, exceptions, faults and other relevant events shall be produced, stored, protected and analysed. In practice, this means you can prove you policy management-level controls on a defined cadence.

Why it matters

ISO 27001 certification depends on showing each Annex A control is either implemented or explicitly justified for exclusion in the Statement of Applicability (SoA). Certification bodies sample controls during surveillance audits, and a missing SoA entry — or implementation that doesn't match the SoA wording — is a finding.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

An ISO 27001 lead auditor looks for: (1) an SoA entry covering the control with justification, (2) a documented procedure or policy implementing it, (3) records that prove the procedure runs (logs, tickets, training records) and (4) management-review evidence that effectiveness is monitored.

Within Technological controls, the assessor will trace your implementation back to the catalogue reference (Annex A A.8.15) and look for objective evidence on the latest two assessment cycles.

How to implement

Logging Monitoring

AWS. Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation.

Azure. Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR.

GCP. Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM.

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

  • Policy. Document the trigger, the owner and the cadence.
  • Management. Document the trigger, the owner and the cadence.
  • Scope: management.

Evidence to collect

  • Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

SIEM ingestion dashboards (Splunk, Sentinel) confirm logging coverage and retention.

Common pitfalls

  • Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days.
  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in ISO/IEC 27001:2022

References

Topics: governance risklogging monitoringpolicy management