800-53 · SI System and Information Integrity
SI-13
Predictable Failure Prevention
frameworkNIST SP 800-53 Rev 5.2
sectionSI System and Information Integrity
csf 2.0PR.IR-03
topics—
frameworks0 0 2
Official texta. Determine mean time to failure (MTTF) for the following system components in specific environments of operation: [Assignment: organization-defined system components]; and
b. Provide substitute system components and a means to exchange active and standby components in accordance with the following criteria: [Assignment: organization-defined mean time to failure (MTTF) substitution criteria].NIST SP 800-53 Rev 5.2 control statement (public domain)
b. Provide substitute system components and a means to exchange active and standby components in accordance with the following criteria: [Assignment: organization-defined mean time to failure (MTTF) substitution criteria].NIST SP 800-53 Rev 5.2 control statement (public domain)
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | PR.IR-03 | Mechanisms are implemented to achieve resilience requirements in normal and adverse situations | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| ISO 27001 | A.5.29A.8.14A.8.17A.8.27 | Information security during disruption; Redundancy of information processing facilities… | No mapping. Only shares CSF PR.IR-03: related, not a mapping+2 more loosely related (not mappings)Clause 4.2 Understanding the needs and expectations of interested parties Only shares CSF PR.IR-03: related, not a mapping | |
| CIS v8.1 | CIS 11.1 | Establish and Maintain a Data Recovery Process | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| SOC 2 | A1.1A1.2A1.3CC9.1 | Capacity management to meet availability commitments; Environmental protections, backups and recovery infrastructure… | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| PCI DSS | 12.10.112.10.212.10.6 | Incident response plan ready to activate; Incident response plan reviewed and tested annually… | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| CMMC | SC.L2-3.13.2 | Security Engineering | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| HIPAA | §164.308(a)(7)(ii)(D) | Testing and Revision Procedure | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| GDPR | Art.32(1)(b)Art.32(1)(c) | Security of processing; Security of processing | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| NIS2 | 4.3 | Crisis management | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| Essential Eight | ISM-1515 | Restoration of data, applications and settings from backups to a common point in time… | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| DORA | Art.11(1)Art.11(4)Art.11(6)Art.12(4) | Response and recovery; Response and recovery… | No mapping. Only shares CSF PR.IR-03: related, not a mapping | |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.