@cyberstrikeus/cp-10-6-component-protection
BProtect system components used for recovery and reconstitution.
Install
agr install @cyberstrikeus/cp-10-6-component-protection --target claudeWrites 1 file into .claude/skills/, pinned to git-ea81230e.
- .claude/skills/cp-10-6-component-protection/SKILL.md
Document
name: "CP-10(6)_component-protection" description: "Protect system components used for recovery and reconstitution." category: "configuration" version: "5.2.0" author: "cyberstrike-official" tags:
- nist
- sp800-53
- rev5
- cp-10-6
- cp
- enhancement tech_stack:
- aws
- azure
- gcp cwe_ids: [] chains_with:
- AC-3
- AC-6
- MP-2
- MP-4
- PE-3
- PE-6 prerequisites:
- CP-10 severity_boost: AC-3: "Chain with AC-3 for comprehensive security coverage" AC-6: "Chain with AC-6 for comprehensive security coverage" MP-2: "Chain with MP-2 for comprehensive security coverage"
CP-10(6) Component Protection
Enhancement of: CP-10
High-Level Description
Family: Contingency Planning (CP) Framework: NIST SP 800-53 Rev 5
Protection of system recovery and reconstitution components (i.e., hardware, firmware, and software) includes physical and technical controls. Backup and restoration components used for recovery and reconstitution include router tables, compilers, and other system software.
What to Check
- Verify CP-10(6) Component Protection is documented in SSP
- Confirm control is operating effectively
- Review evidence of continuous monitoring for CP-10(6)
- 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(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 |
|---|---|---|
| Manual Review | Documentation and interview-based | N/A |
Remediation Guide
Control Statement
Protect system components used for recovery and reconstitution.
Implementation Guidance
Protection of system recovery and reconstitution components (i.e., hardware, firmware, and software) includes physical and technical controls. Backup and restoration components used for recovery and reconstitution include router tables, compilers, and other system software.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| CP-10(6) Component Protection not implemented | Medium | Contingency Planning |
| CP-10(6) partially implemented | Low | Incomplete Contingency Planning |
CWE Categories
| CWE ID | Title |
|---|---|
| N/A | No direct CWE mapping |
References
- NIST SP 800-53 Rev 5 - CP-10(6)
- NIST SP 800-53A Rev 5 (Assessment Procedures)
- NIST SP 800-53 Rev 5 Full Catalog
Checklist
- Control documented in SSP
- Implementation evidence collected
- Operating effectiveness validated
- Continuous monitoring in place
- Related controls (AC-3, AC-6, MP-2, MP-4, PE-3) reviewed
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicensecopyleft/unknown — index-and-link only
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-ea81230ea4b52026-07-31