AU-9(6)_read-only-access
DevOps & SecurityAU-9(6)_read-only-access 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.
Authorize read-only access to audit information to [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-9(6)_read-only-access/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/au-9-6-read-only-access, 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(6) Read-only Access
Enhancement of: AU-9
High-Level Description
Family: Audit and Accountability (AU) Framework: NIST SP 800-53 Rev 5
Restricting privileged user or role authorizations to read-only helps to limit the potential damage to organizations that could be initiated by such users or roles, such as deleting audit records to cover up malicious activity.
What to Check
- Verify AU-9(6) Read-only Access is documented in SSP
- Confirm control is operating effectively
- Review evidence of continuous monitoring for AU-9(6)
- Verify enhancement builds upon base control AU-9
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for AU-9(6) 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
Authorize read-only access to audit information to [organization-defined].
Implementation Guidance
Restricting privileged user or role authorizations to read-only helps to limit the potential damage to organizations that could be initiated by such users or roles, such as deleting audit records to cover up malicious activity.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| AU-9(6) Read-only Access not implemented | Medium | Audit and Accountability |
| AU-9(6) partially implemented | Low | Incomplete Audit and Accountability |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-778 | Insufficient Logging |
References
- NIST SP 800-53 Rev 5 - AU-9(6)
- 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 (none) reviewed