SA-17 Developer Security and Privacy Architecture and Design
Requires the developer to produce architecture and design evidence sufficient for the organization to judge the security of what it is buying.
Source: NIST SP 800-161 Rev 1 (supply chain), SA-17. 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-161 Rev 1 (supply chain) in the compliance library.
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
- Review records of those deliverables · Document repository
governing documentDocuments that govern the control
- Architecture and design deliverables required and received · Policy repository / GRC workspace
- Traceability from requirement to design · Document repository
First move
Common gaps auditors find
- design evidence withheld as proprietary and the risk unaccepted
- deliverables received but never reviewed
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 sheetSA-16 Developer-Provided Training · SA-20 Customized Development of Critical Components