ISO 27001:2022 Annex A 8.15 – Logging Explained

If you can’t see what’s happening, you can’t protect it.
Logging is how organisations gain visibility, evidence, and control.

‍
Annex A 8.15 exists to ensure organisations log, protect, and review relevant events, enabling detection of security incidents, supporting investigations, and providing accountability across systems and users.

This control is about observability, not just record keeping.

ISO 27001

Quick Guide: Annex A 8.15 at a Glance

Annex A 8.15 of ISO 27001:2022 focuses on logging of security-relevant events.

At a practical level, this means:

  • Recording key system, user, and application events
  • Ensuring logs are accurate, complete, and protected
  • Preventing unauthorised deletion or modification of logs
  • Reviewing and analysing logs for suspicious activity
  • Supporting investigations, audits, and incident response

The control does not require logging everything. It expects organisations to log what matters, protect it properly, and use it effectively.

In-Depth Guide to Annex A 8.15

What Is Annex A 8.15 and Why Does It Matter?

Logs provide:

  • Evidence of what happened
  • Insight into how systems are used
  • Early warning of security incidents
  • Support for forensic investigation
  • Accountability for user and system actions

Without effective logging:

  • Incidents go undetected
  • Investigations rely on guesswork
  • Accountability is weakened
  • Assurance becomes difficult to demonstrate

Annex A 8.15 ensures organisations treat logs as a security control, not just a technical by-product.

This control consolidates and replaces ISO 27001:2013 controls 12.4.1, 12.4.2, and 12.4.3.

How to Implement Annex A 8.15 Effectively

A pragmatic approach to Annex A 8.15 typically includes the following elements.

1. Define What Should Be Logged

Organisations should identify events that are relevant to information security risk.

ISO 27001:2022 highlights logging of events such as:

  • Successful and failed access attempts
  • Access to data and system resources
  • Use of privileged accounts
  • Configuration and system changes
  • Activation or deactivation of security controls
  • File access, deletion, or movement
  • Identity and access management activities

Logging every event is rarely practical.
Logging the right events is essential.

2. Ensure Logs Contain Meaningful Information

For logs to be useful, they should typically include:

  • User or system identity
  • Description of the event
  • Date and time of occurrence
  • System or asset involved
  • Network or location details where relevant

Incomplete logs limit investigation and assurance value.

3. Synchronise Time Sources

Annex A 8.15 relies on accurate timelines.

Organisations should ensure:

  • Systems use consistent time sources
  • Time discrepancies are minimised and understood
  • Logs from different systems can be correlated

Unsynchronised logs undermine incident reconstruction.

4. Protect Logs From Unauthorised Access and Change

Logs are high-value targets.

Organisations should ensure:

  • Users cannot alter or delete their own logs
  • Logs are protected against unauthorised modification
  • Storage capacity prevents overwriting or loss

Protection techniques may include:

  • Read-only or append-only logging
  • Cryptographic hashing
  • Secure centralised log storage

If logs can be changed, they cannot be trusted.

5. Prevent Log Loss or Overwriting

Failure to generate logs is itself a risk.

Organisations should:

  • Monitor log generation and storage
  • Prevent silent log failure
  • Ensure sufficient storage capacity

Missing logs often indicate deeper control failure.

6. Address Privacy and Data Protection

Logs may contain personal data.

Where logs are shared internally or externally, organisations should consider:

  • De-identification or masking of personal data
  • Alignment with privacy obligations and legislation
  • Limiting log access to authorised personnel only

Logging should support security without creating unnecessary privacy risk.

7. Analyse Logs for Security-Relevant Activity

Logging without review provides limited value.

Organisations should ensure:

  • Logs are reviewed in line with defined procedures
  • High-risk or critical systems receive greater scrutiny
  • Anomalous or suspicious patterns are investigated

Analysis may be manual or supported by tooling, depending on scale and risk.

8. Monitor Logs Actively Where Risk Justifies It

Annex A 8.15 supports active monitoring, particularly for:

  • Privileged access
  • Critical systems
  • External-facing services

Monitoring helps detect:

  • Unauthorised access attempts
  • Lateral movement
  • Malicious activity
  • Policy violations

Detection delayed is detection diminished.

9. Define Responsibility for Logging and Review

Clear ownership is essential.

Organisations should define:

  • Who is responsible for log configuration
  • Who reviews logs
  • Who responds to alerts or findings

Unowned logs are rarely reviewed effectively.

10. Use Centralised Logging Where Appropriate

In complex environments, organisations may consider:

  • Centralised log collection
  • Correlation across systems
  • Use of specialist log management or SIEM tools

Centralisation improves visibility, correlation, and response capability.

11. Include Cloud and Third-Party Logs

Where cloud or managed services are used:

  • Logging responsibility is shared
  • Contractual clarity is essential
  • Relevant logs should be accessible to the organisation

Cloud does not remove logging responsibility.

Practical Considerations

Annex A 8.15 does not require:

  • Logging every possible event
  • Continuous human review of all logs
  • Expensive tooling by default

It does require organisations to:

  • Decide what is important to log
  • Protect logs as security evidence
  • Use logs to support detection and investigation

Logs only add value when they are used.

Common Challenges and How to Overcome Them

  • Too many logs, no insight
  • Focus on security-relevant events
  • Logs stored but never reviewed
  • Define review and monitoring expectations
  • Logs that can be altered or deleted
  • Apply integrity and access controls
  • Inconsistent timestamps across systems
  • Synchronise time sources

Logging failures are often discovered during incidents, not before.

Final Recommendations

Annex A 8.15 is about knowing what is happening in your environment.

When logging is implemented effectively:

  • Security incidents are detected earlier
  • Investigations are faster and more accurate
  • Accountability is strengthened
  • Assurance becomes evidence-based

You cannot protect what you cannot see.
Annex A 8.15 ensures organisations turn activity into visibility, and visibility into control.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls