03.03.02Audit record contentITSP.10.171Audit and accountability
Official Requirement
A. Include the following content in audit records: 1. what type of event occurred 2. when the event occurred 3. where the event occurred 4. source of the event 5. outcome of the event 6. identity of individuals, subjects, objects, or entities associated with the event B. Provide additional information for audit records, as needed
Source: Canadian Centre for Cyber Security ITSP.10.171 (2025), adapted from NIST SP 800-171 Rev. 3
In Plain English
Every audit log entry must answer: what happened, when, where in the system, what triggered it, whether it succeeded or failed, and who was involved. If your logs do not contain all of these fields, they will not support incident investigation. Ensure your logging format captures structured data, not just free-text messages.
These are typical controls and implementation steps. Your systems and environment may differ.
Typical Control Structured audit record content
Implementation Steps
Configure cloud audit services to capture all required fields: event type, timestamp, resource location, source IP, outcome (success/fail), and user/service identity
Standardize application log format (e.g., JSON structured logging) to include the six required content fields plus additional context (request ID, session ID)
Validate audit record completeness by sampling logs periodically and confirming all required fields are populated
Enrich logs in the SIEM with additional context (geolocation, user department, asset classification) to support investigations
Tools / Systems
Cloud audit logging (built-in structured format)Structured logging libraries (JSON logging frameworks)SIEM with field validation and enrichmentLog quality monitoring dashboard
Typical Control Structured audit record content
Evidence Artifacts
Sample audit records from cloud services and applications showing all six required content fields
SIEM parsing configuration demonstrating field extraction and validation
📅Continuous logging; quarterly log quality review
Cross-framework mappings coming in v1.1
When we add ISO 42001 and ISO 27001, you'll see which controls map to this criterion.
ISO
ISO 42001
AI Management Systems
ISO
ISO 27001
Information Security
Mapping data will appear here automatically when the frameworks are published.