EvidenceSheet
NIST SP 800-53 Rev 5 · SI - System and Information Integrity

SI-13(4) Predictable Failure Prevention | Standby Component Installation and Notification

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

Source: NIST SP 800-53 Rev 5, SI-13(4). The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

9
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • System audit records · Policy repository / GRC workspace
  • Test of Organizational processes for managing MTTF; automated mechanisms supporting and/or implementing the transparent installation of standby components; automated mechanisms supporting and/or implementing alarms or system shutdown if component failures are detected · Document repository

governing documentDocuments that govern the control

  • System and information integrity policy · Policy repository / GRC workspace
  • System and information integrity procedures · Policy repository / GRC workspace
  • Procedures addressing predictable failure prevention · Policy repository / GRC workspace
  • System design documentation · Document repository
  • System configuration settings and associated documentation · Policy repository / GRC workspace
  • List of actions to be taken once system component failure is detected · Document repository
  • System security plan · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

SI-13(3) Predictable Failure Prevention | Manual Transfer Between Components · SI-13(5) Predictable Failure Prevention | Failover Capability