AU-5(5)_alternate-audit-logging-capability
DevOps & SecurityAU-5(5)_alternate-audit-logging-capability 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.
Provide an alternate audit logging capability in the event of a failure in primary audit logging capability that implements [organization-defined].
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/AU_audit-and-accountability/AU-5(5)_alternate-audit-logging-capability/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/au-5-5-alternate-audit-logging-capability, 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-5(5) Alternate Audit Logging Capability
Enhancement of: AU-5
High-Level Description
Family: Audit and Accountability (AU) Framework: NIST SP 800-53 Rev 5
Since an alternate audit logging capability may be a short-term protection solution employed until the failure in the primary audit logging capability is corrected, organizations may determine that the alternate audit logging capability need only provide a subset of the primary audit logging functionality that is impacted by the failure.
What to Check
- Verify AU-5(5) Alternate Audit Logging Capability is documented in SSP
- Confirm control is operating effectively
- Review evidence of continuous monitoring for AU-5(5)
- Verify enhancement builds upon base control AU-5
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for AU-5(5) 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
| Tool | Purpose | Usage |
|---|---|---|
| cloud-audit-mcp | Check logging configuration | cloud_audit_logging |
| AWS CLI | Review CloudTrail/CloudWatch | aws cloudtrail describe-trails |
Remediation Guide
Control Statement
Provide an alternate audit logging capability in the event of a failure in primary audit logging capability that implements [organization-defined].
Implementation Guidance
Since an alternate audit logging capability may be a short-term protection solution employed until the failure in the primary audit logging capability is corrected, organizations may determine that the alternate audit logging capability need only provide a subset of the primary audit logging functionality that is impacted by the failure.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| AU-5(5) Alternate Audit Logging Capability not implemented | Medium | Audit and Accountability |
| AU-5(5) partially implemented | Low | Incomplete Audit and Accountability |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-778 | Insufficient Logging |
References
- NIST SP 800-53 Rev 5 - AU-5(5)
- NIST SP 800-53A Rev 5 (Assessment Procedures)
- NIST SP 800-53 Rev 5 Full Catalog
Checklist
- Control documented in SSP
- Implementation evidence collected
- Operating effectiveness validated
- Continuous monitoring in place
- Related controls (AU-9) reviewed