OpenParable
Skip to content
← Back to skills

AU-3_content-of-audit-records

DevOps & Security

AU-3_content-of-audit-records is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure that audit records contain information that establishes the following: What type of event occurred; When the event occurred; Where the event oc

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/AU_audit-and-accountability/AU-3_content-of-audit-records/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/au-3-content-of-audit-records, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

AU-3 Content of Audit Records

High-Level Description

Family: Audit and Accountability (AU) Framework: NIST SP 800-53 Rev 5

Audit record content that may be necessary to support the auditing function includes event descriptions (item a), time stamps (item b), source and destination addresses (item c), user or process identifiers (items d and f), success or fail indications (item e), and filenames involved (items a, c, e, and f) . Event outcomes include indicators of event success or failure and event-specific results, such as the system security and privacy posture after the event occurred. Organizations consider how audit records can reveal information about individuals that may give rise to privacy risks and how best to mitigate such risks. For example, there is the potential to reveal personally identifiable information in the audit trail, especially if the trail records inputs or is based on patterns or time of usage.

What to Check

  • Verify AU-3 Content of Audit Records is documented in SSP
  • Validate all 6 control requirements are implemented
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for AU-3

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AU-3 implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

ToolPurposeUsage
cloud-audit-mcpCheck logging configurationcloud_audit_logging
AWS CLIReview CloudTrail/CloudWatchaws cloudtrail describe-trails

Remediation Guide

Control Statement

Ensure that audit records contain information that establishes the following: What type of event occurred; When the event occurred; Where the event occurred; Source of the event; Outcome of the event; and Identity of any individuals, subjects, or objects/entities associated with the event.

Implementation Guidance

Audit record content that may be necessary to support the auditing function includes event descriptions (item a), time stamps (item b), source and destination addresses (item c), user or process identifiers (items d and f), success or fail indications (item e), and filenames involved (items a, c, e, and f) . Event outcomes include indicators of event success or failure and event-specific results, such as the system security and privacy posture after the event occurred. Organizations consider how audit records can reveal information about individuals that may give rise to privacy risks and how best to mitigate such risks. For example, there is the potential to reveal personally identifiable information in the audit trail, especially if the trail records inputs or is based on patterns or time of usage.

Risk Assessment

FindingSeverityImpact
AU-3 Content of Audit Records not implementedMediumAudit and Accountability
AU-3 partially implementedLowIncomplete Audit and Accountability

CWE Categories

CWE IDTitle
CWE-778Insufficient Logging

References

Checklist

  • Control documented in SSP
  • Implementation evidence collected
  • Operating effectiveness validated
  • Continuous monitoring in place
  • Related controls (AU-2, AU-8, AU-12, AU-14, MA-4) reviewed