NIST · Shared reference library

NIST SP 800-53 Rev. 5 Common Control Library

Browse 1,193 controls and enhancements across 20 security and privacy families. Use the GovRAMP crosswalk to locate controls referenced by Security Snapshot, Core, and Moderate.

A shared catalog supports common-control planning; designation as a common, hybrid, or system-specific control depends on your organization’s implementation and inheritance decisions.

Sources and crosswalk scope

NIST OSCAL content 5.1.1+u4, retrieved 2026-09-18. GovRAMP Snapshot v1.4 and Core selection from Moderate v1.06 reference the December 2020 Rev. 5 text. Mappings establish exact identifier correspondence, not identical requirements, inherited implementation, or GovRAMP authorization. GovRAMP parameters and additional requirements remain authoritative for each program. Full Moderate, High, and other programs are not mapped here. Withdrawn controls are retained for reference.

Official pinned NIST source

SHA-256: 81cf2de45ede9aef3de7ce09d65ea9d32f662c483bbf916f6e346292b22f7763

Reset

6 matching controls · Page 1 of 1

System and Information Integrity · Base control

SI-13 · Predictable Failure Prevention

Control statement and discussion

NIST control statement

a. Determine mean time to failure (MTTF) for the following system components in specific environments of operation: [Assignment: system components] ; and b. Provide substitute system components and a means to exchange active and standby components in accordance with the following criteria: [Assignment: mean time to failure (MTTF) substitution criteria].

Discussion

While MTTF is primarily a reliability issue, predictable failure prevention is intended to address potential failures of system components that provide security capabilities. Failure rates reflect installation-specific consideration rather than the industry-average. Organizations define the criteria for the substitution of system components based on the MTTF value with consideration for the potential harm from component failures. The transfer of responsibilities between active and standby components does not compromise safety, operational readiness, or security capabilities. The preservation of system state variables is also critical to help ensure a successful transfer process. Standby components remain available at all times except for maintenance issues or recovery failures in progress.

GovRAMP crosswalk

Not selected in the imported Snapshot or Core sets. This does not establish exclusion from other GovRAMP baselines.

System and Information Integrity · Enhancement

SI-13(1) · Transferring Component Responsibilities

View parent control
Control statement and discussion

NIST control statement

Take system components out of service by transferring component responsibilities to substitute components no later than [Assignment: fraction or percentage] of mean time to failure.

Discussion

Transferring primary system component responsibilities to other substitute components prior to primary component failure is important to reduce the risk of degraded or debilitated mission or business functions. Making such transfers based on a percentage of mean time to failure allows organizations to be proactive based on their risk tolerance. However, the premature replacement of system components can result in the increased cost of system operations.

GovRAMP crosswalk

Not selected in the imported Snapshot or Core sets. This does not establish exclusion from other GovRAMP baselines.

System and Information Integrity · Enhancement · Withdrawn

SI-13(2) · Time Limit on Process Execution Without Supervision

View parent control
Control statement and discussion

NIST control statement

Withdrawn in this source release; review the official source for disposition.

GovRAMP crosswalk

Not selected in the imported Snapshot or Core sets. This does not establish exclusion from other GovRAMP baselines.

System and Information Integrity · Enhancement

SI-13(3) · Manual Transfer Between Components

View parent control
Control statement and discussion

NIST control statement

Manually initiate transfers between active and standby system components when the use of the active component reaches [Assignment: percentage] of the mean time to failure.

Discussion

For example, if the MTTF for a system component is 100 days and the MTTF percentage defined by the organization is 90 percent, the manual transfer would occur after 90 days.

GovRAMP crosswalk

Not selected in the imported Snapshot or Core sets. This does not establish exclusion from other GovRAMP baselines.

System and Information Integrity · Enhancement

SI-13(4) · Standby Component Installation and Notification

View parent control
Control statement and discussion

NIST control statement

If system component failures are detected: (a) Ensure that the standby components are successfully and transparently installed within [Assignment: time period] ; and (b) [Selection (one-or-more): activate [Assignment: alarm] ; automatically shut down the system; [Assignment: action] ].

Discussion

Automatic or manual transfer of components from standby to active mode can occur upon the detection of component failures.

GovRAMP crosswalk

Not selected in the imported Snapshot or Core sets. This does not establish exclusion from other GovRAMP baselines.

System and Information Integrity · Enhancement

SI-13(5) · Failover Capability

View parent control
Control statement and discussion

NIST control statement

Provide [Selection (one): real-time; near real-time] [Assignment: failover capability] for the system.

Discussion

Failover refers to the automatic switchover to an alternate system upon the failure of the primary system. Failover capability includes incorporating mirrored system operations at alternate processing sites or periodic data mirroring at regular intervals defined by the recovery time periods of organizations.

GovRAMP crosswalk

Not selected in the imported Snapshot or Core sets. This does not establish exclusion from other GovRAMP baselines.