NIST 800-53 REV 5 • SYSTEM AND INFORMATION INTEGRITY
SI-13(1) — Transferring Component Responsibilities
Take system components out of service by transferring component responsibilities to substitute components no later than {{ insert: param, si-13.01_odp }} of mean time to failure.
CMMC Practice Mapping
No direct CMMC mapping
NIST 800-171 Mapping
No direct NIST 800-171 mapping
Related Controls
No related controls listed
Supplemental Guidance
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.
Practitioner Notes
When a component starts to fail, automatically transfer its responsibilities to a backup component before complete failure occurs.
Example 1: Configure high availability for your database servers (SQL Server Always On, PostgreSQL streaming replication). If the primary server shows signs of failure (missed heartbeats, high error rates), the cluster automatically promotes the secondary server.
Example 2: Set up load balancer health checks that automatically remove servers from the pool when they stop responding correctly. The remaining healthy servers absorb the traffic while the failed server is repaired or replaced.