Free compliance framework explorer — browse controls, evidence, and implementation guidance.Subscribe for updates →
SOC 247
ITSP.10.17198
ISO 42001soon
ISO 27001soon

Browse

98 controls

03.03.04Response to audit logging process failuresITSP.10.171Audit and accountability

Official Requirement

A. Alert organizational personnel or roles within [Assignment: organization-defined time period] in the event of an audit logging process failure B. Take the following additional actions: [Assignment: organization-defined additional actions]

Source: Canadian Centre for Cyber Security ITSP.10.171 (2025), adapted from NIST SP 800-171 Rev. 3

In Plain English

When logging stops working -- whether due to a service outage, storage full, or configuration error -- your organization must detect it quickly, alert the right people, and take corrective action. A system running without logging is running blind, and that gap must be treated as a security event.

Help us build what matters.

Vote for the next framework, subscribe for updates, and let us know if you'd contribute.

The Trust Services Criteria referenced in this tool are published by the American Institute of Certified Public Accountants (AICPA) and incorporate principles from the Committee of Sponsoring Organizations of the Treadway Commission (COSO). Criteria descriptions are reproduced for reference purposes. All implementation guidance, evidence recommendations, and control language are original work by Truvo Cyber. ISO 27001 and ISO 42001 are standards published by the International Organization for Standardization (ISO). Framework and standard names are the property of their respective owners. This tool is not affiliated with, endorsed by, or certified by AICPA, COSO, or ISO.

© 2026 Truvo Cyber. All rights reserved.

On-premises implementation and evidence

Logging failure detection and response

Implementation steps

  1. Configure SIEM and log collector health monitoring to detect when log sources stop sending data or when storage thresholds are exceeded
  2. Set up automated alerts to security operations when logging failures are detected, with defined response time SLAs
  3. Document response procedures for logging failures including manual log collection, alternative logging mechanisms, and incident escalation
  4. Monitor disk space on syslog servers and SIEM storage; alert before capacity is exhausted

Tools / systems

Evidence artifacts

Evidence frequency: Continuous monitoring; annual alert testing; per-event incident documentation