| name | SI-7(8)_auditing-capability-for-significant-events |
| description | Upon detection of a potential integrity violation, provide the capability to audit the event and initiate the following actions: [organization-defined |
| category | input-validation |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","si-7-8","si","enhancement"] |
| tech_stack | ["aws","azure","gcp","linux","windows"] |
| cwe_ids | ["CWE-20"] |
| chains_with | ["AU-2","AU-6","AU-12"] |
| prerequisites | ["SI-7"] |
| severity_boost | {"AU-2":"Chain with AU-2 for comprehensive security coverage","AU-6":"Chain with AU-6 for comprehensive security coverage","AU-12":"Chain with AU-12 for comprehensive security coverage"} |
SI-7(8) Auditing Capability for Significant Events
Enhancement of: SI-7
High-Level Description
Family: System and Information Integrity (SI)
Framework: NIST SP 800-53 Rev 5
Organizations select response actions based on types of software, specific software, or information for which there are potential integrity violations.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for SI-7(8) 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 integrity monitoring | cloud_audit_monitoring |
| AWS CLI | Review GuardDuty/Inspector | aws guardduty list-detectors |
Remediation Guide
Control Statement
Upon detection of a potential integrity violation, provide the capability to audit the event and initiate the following actions: [organization-defined].
Implementation Guidance
Organizations select response actions based on types of software, specific software, or information for which there are potential integrity violations.
Risk Assessment
