Authorize read-only access to audit information to [organization-defined].
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill AU-9(6)_read-only-access --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of AU 9(6) Read Only Access?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-au-9-6-read-only-access)More formats (shields.io, HTML) on the badges page.
---
name: "AU-9(6)_read-only-access"
description: "Authorize read-only access to audit information to [organization-defined]."
category: "information-gathering"
version: "5.2.0"
author: "cyberstrike-official"
tags:
- nist
- sp800-53
- rev5
- au-9-6
- au
- enhancement
tech_stack:
- aws
- azure
- gcp
- linux
- windows
cwe_ids:
- CWE-778
chains_with: []
prerequisites:
- AU-9
severity_boost: {}
---
# 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)](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=au-9.6)
- [NIST SP 800-53A Rev 5 (Assessment Procedures)](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final)
- [NIST SP 800-53 Rev 5 Full Catalog](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)
## Checklist
- [ ] Control documented in SSP
- [ ] Implementation evidence collected
- [ ] Operating effectiveness validated
- [ ] Continuous monitoring in place
- [ ] Related controls (none) reviewed
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!