| name | SI-10(1)_manual-override-capability |
| description | Provide a manual override capability for input validation of the following information inputs: [organization-defined]; |
| category | input-validation |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","si-10-1","si","enhancement"] |
| tech_stack | ["aws","azure","gcp","linux","windows"] |
| cwe_ids | ["CWE-20"] |
| chains_with | ["AC-3","AU-2","AU-12"] |
| prerequisites | ["SI-10"] |
| severity_boost | {"AC-3":"Chain with AC-3 for comprehensive security coverage","AU-2":"Chain with AU-2 for comprehensive security coverage","AU-12":"Chain with AU-12 for comprehensive security coverage"} |
SI-10(1) Manual Override Capability
Enhancement of: SI-10
High-Level Description
Family: System and Information Integrity (SI)
Framework: NIST SP 800-53 Rev 5
In certain situations, such as during events that are defined in contingency plans, a manual override capability for input validation may be needed. Manual overrides are used only in limited circumstances and with the inputs defined by the organization.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for SI-10(1) 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
Provide a manual override capability for input validation of the following information inputs: [organization-defined];
Restrict the use of the manual override capability to only [organization-defined] ; and
Audit the use of the manual override capability.
Implementation Guidance
In certain situations, such as during events that are defined in contingency plans, a manual override capability for input validation may be needed. Manual overrides are used only in limited circumstances and with the inputs defined by the organization.
