SA-24 Design For Cyber Resiliency
a. Design organizational systems, system components, or system services to achieve cyber resiliency by: 1. Defining the following cyber resiliency goals: organization-defined cyber resiliency goals. 2. Defining the following cyber resiliency objectives: organization-defined cyber resiliency objectives. 3. Defining the following cyber resiliency techniques: organization-defined cyber resiliency techniques. 4. Defining the following cyber resiliency implementation approaches: organization-defined cyber resiliency implementation approaches. 5. Defining the following cyber resiliency design principles: organization-defined cyber resiliency design principles. b. Implement and review the selected cyber resiliency goals, objectives, techniques, implementation approaches, and design principles as part of an organizational risk management process or systems security engineering process.
Source: NIST SP 800-53 Rev 5, SA-24. 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.
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
- Privacy impact assessment · Data governance / DLP tooling
- Test of Organizational processes for applying cyber resiliency principles in system specification, design, development, implementation, and modification; mechanisms supporting the application of cyber resiliency principles in system specification, design, development, implementation, and modification. · Document repository
governing documentDocuments that govern the control
- System and services acquisition policy · Policy repository / GRC workspace
- System and services acquisition procedures · Policy repository / GRC workspace
- Assessment and authorization procedures · Policy repository / GRC workspace
- Procedures addressing cyber resiliency goals, objectives, techniques, implementation approaches, and design principles used in the specification, design, development, implementation, and modification of the system · Policy repository / GRC workspace
- System design documentation · Document repository
- Security and privacy requirements and specifications for the system · Policy repository / GRC workspace
- System security plan · Policy repository / GRC workspace
- Privacy plan · Policy repository / GRC workspace
First move
Common gaps auditors find
- Cyber resiliency goals, objectives, techniques, approaches and design principles were never defined
- Selected cyber resiliency elements are not implemented as part of the risk management strategy
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