PL-8 Security and Privacy Architectures
Builds supply chain considerations into architecture, including diversity, provenance and the ability to replace a supplier.
Source: NIST SP 800-161 Rev 1 (supply chain), PL-8. 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
- Analysis of substitutability for critical components · Cloud console / configuration management
- Architecture decision records · Cloud console / configuration management
governing documentDocuments that govern the control
- Architecture artefacts addressing supplier dependency and diversity · Vendor register / contract repository
First move
Common gaps auditors find
- architecture locks the organization to a single supplier with no analysis
- diversity considered for hardware but not software dependencies
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