OpenParable
Skip to content
← Back to skills

AU-9_protection-of-audit-information

DevOps & Security

AU-9_protection-of-audit-information 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.

Protect audit information and audit logging tools from unauthorized access, modification, and deletion;

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-9_protection-of-audit-information/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/au-9-protection-of-audit-information, 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-9 Protection of Audit Information

High-Level Description

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

Audit information includes all information needed to successfully audit system activity, such as audit records, audit log settings, audit reports, and personally identifiable information. Audit logging tools are those programs and devices used to conduct system audit and logging activities. Protection of audit information focuses on technical protection and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by both media protection controls and physical and environmental protection controls.

What to Check

  • Verify AU-9 Protection of Audit Information is documented in SSP
  • Validate all 2 control requirements are implemented
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for AU-9

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AU-9 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

Protect audit information and audit logging tools from unauthorized access, modification, and deletion; and Alert [organization-defined] upon detection of unauthorized access, modification, or deletion of audit information.

Implementation Guidance

Audit information includes all information needed to successfully audit system activity, such as audit records, audit log settings, audit reports, and personally identifiable information. Audit logging tools are those programs and devices used to conduct system audit and logging activities. Protection of audit information focuses on technical protection and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by both media protection controls and physical and environmental protection controls.

Risk Assessment

FindingSeverityImpact
AU-9 Protection of Audit Information not implementedMediumAudit and Accountability
AU-9 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 (AC-3, AC-6, AU-6, AU-11, AU-14) reviewed