SC-29 Heterogeneity
Uses diversity of components and suppliers so a single compromised source cannot affect everything at once.
Source: NIST SP 800-161 Rev 1 (supply chain), SC-29. 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 component and supplier concentration · Vendor register / contract repository
- Diversity decisions and their rationale · Document repository
governing documentDocuments that govern the control
- Identification of common-mode dependencies · Document repository
First move
Common gaps auditors find
- standardization pursued to the point of a single point of failure
- diversity claimed while all products share one upstream component
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 sheetSC-28 Protection of Information at Rest · SC-30 Concealment and Misdirection