EvidenceSheet
FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline) · SA - System and Services Acquisition

SA-15(3) Development Process, Standards, and Tools | Criticality Analysis (SA-15(3))

Development Process, Standards, and Tools | Criticality Analysis. Require the developer of the system, system component, or system service to perform a criticality analysis: (a) At the following decision points in the system development

Source: FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline), SA-15(3). 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 FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline) in the compliance library.

A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.

5
artefacts
0
held by a system
3
at each review
hard
to go live
Document repository
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

  • Evidence the analysis was performed at the defined decision points in the development life cycle · Document repository
  • Evidence the analysis was performed at the defined level of detail or decomposition · Document repository
  • Organisational review of the developer's analysis and the actions taken on its findings · Document repository

governing documentDocuments that govern the control

  • Contract or solicitation clause requiring the developer to perform criticality analysis · Vendor register / contract repository
  • The developer's criticality analysis output identifying critical components and functions · Document repository

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

SA-15 Development Process, Standards, and Tools (SA-15) · SA-22 Unsupported System Components (SA-22)