Alternative Security Mechanisms
LOW MODERATE HIGHRequirements NIST SOURCE
Employ [alternative or supplemental security mechanisms] for satisfying [security functions] when the primary means of implementing the security function is unavailable or compromised.
Discussion (NIST Supplemental Guidance)
Use of alternative security mechanisms supports system resiliency, contingency planning, and continuity of operations. To ensure mission and business continuity, organizations can implement alternative or supplemental security mechanisms. The mechanisms may be less effective than the primary mechanisms. However, having the capability to readily employ alternative or supplemental mechanisms enhances mission and business continuity that might otherwise be adversely impacted if operations had to be curtailed until the primary means of implementing the functions was restored. Given the cost and level of effort required to provide such alternative capabilities, the alternative or supplemental mechanisms are only applied to critical security capabilities provided by systems, system components, or system services. For example, an organization may issue one-time pads to senior executives, officials, and system administrators if multi-factor tokens—the standard means for achieving secure authentication— are compromised.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for CP-13 yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- alternative or supplemental security mechanisms are defined;
- security functions are defined;
- <CP-13_ODP[01] alternative or supplemental security mechanisms> are employed for satisfying <CP-13_ODP[02] security functions> when the primary means of implementing the security function is unavailable or compromised.
Examine
[SELECT FROM: Contingency planning policy; procedures addressing alternate security mechanisms; contingency plan; continuity of operations plan; system design documentation; system configuration settings and associated documentation; contingency plan test records; contingency plan test results; system security plan; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with system operation responsibilities; organizational personnel with information security responsibilities].
Test
[SELECT FROM: system capability implementing alternative security mechanisms].
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for CP-13. This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- Contingency planning policy
- contingency plan
- continuity of operations plan
- contingency plan test records
- contingency plan test results
- system security plan
Configuration
- system design documentation
- system configuration settings and associated documentation
Testing
- system capability implementing alternative security mechanisms
Other Records
- procedures addressing alternate security mechanisms
- other relevant documents or records