EvidenceSheet
NIST SP 800-53 Rev 5 · SA - System and Services Acquisition

SA-17(2) Developer Security and Privacy Architecture and Design | Security-relevant Components

Require the developer of the system, system component, or system service to: (a) Define security-relevant hardware, software, and firmware; and (b) Provide a rationale that the definition for security-relevant hardware, software, and firmware is complete.

Source: NIST SP 800-53 Rev 5, SA-17(2). 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
0
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

none for this control

governing documentDocuments that govern the control

  • System and services acquisition policy · Policy repository / GRC workspace
  • Enterprise architecture policy · Policy repository / GRC workspace
  • Procedures addressing developer security architecture and design specifications for the system · Policy repository / GRC workspace
  • Solicitation documentation · Document repository
  • Acquisition documentation · Document repository
  • Service level agreements · Vendor register / contract repository
  • Acquisition contracts for the system, system component, or system service · Vendor register / contract repository
  • List of security-relevant hardware, software, and firmware components · Document repository
  • Documented rationale of completeness regarding definitions provided for security-relevant hardware, software, and firmware · 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-17(1) Developer Security and Privacy Architecture and Design | Formal Policy Model · SA-17(3) Developer Security and Privacy Architecture and Design | Formal Correspondence