| name | CP-10(2)_transaction-recovery |
| description | Implement transaction recovery for systems that are transaction-based. |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","cp-10-2","cp","enhancement"] |
| tech_stack | ["aws","azure","gcp"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | ["CP-10"] |
| severity_boost | {} |
CP-10(2) Transaction Recovery
Enhancement of: CP-10
High-Level Description
Family: Contingency Planning (CP)
Framework: NIST SP 800-53 Rev 5
Transaction-based systems include database management systems and transaction processing systems. Mechanisms supporting transaction recovery include transaction rollback and transaction journaling.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CP-10(2) 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 |
|---|
| Manual Review | Documentation and interview-based | N/A |
Remediation Guide
Control Statement
Implement transaction recovery for systems that are transaction-based.
Implementation Guidance
Transaction-based systems include database management systems and transaction processing systems. Mechanisms supporting transaction recovery include transaction rollback and transaction journaling.
Risk Assessment
| Finding | Severity | Impact |
|---|
| CP-10(2) Transaction Recovery not implemented | Medium | Contingency Planning |
| CP-10(2) partially implemented |
