OpenParable
Skip to content
← Back to skills

CP-10(2)_transaction-recovery

Development

CP-10(2)_transaction-recovery is an Agent Skill for development published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Implement transaction recovery for systems that are transaction-based.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/CP_contingency-planning/CP-10(2)_transaction-recovery/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cp-10-2-transaction-recovery, 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.

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

  • Verify CP-10(2) Transaction Recovery is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for CP-10(2)
  • Verify enhancement builds upon base control CP-10

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

ToolPurposeUsage
Manual ReviewDocumentation and interview-basedN/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

FindingSeverityImpact
CP-10(2) Transaction Recovery not implementedMediumContingency Planning
CP-10(2) partially implementedLowIncomplete Contingency Planning

CWE Categories

CWE IDTitle
N/ANo direct CWE mapping

References

Checklist

  • Control documented in SSP
  • Implementation evidence collected
  • Operating effectiveness validated
  • Continuous monitoring in place
  • Related controls (none) reviewed