CM-2 Baseline Configuration
Establishes the baseline for delivered components so that later supplier changes can be detected against a known starting point.
Source: NIST SP 800-161 Rev 1 (supply chain), CM-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-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
- Comparison evidence against the supplier-shipped state · Vendor register / contract repository
- Baseline update records after supplier change · Vendor register / contract repository
governing documentDocuments that govern the control
- Baseline captured at acceptance for delivered components · Policy repository / GRC workspace
First move
Common gaps auditors find
- baseline taken after months of operation
- no baseline for appliances and firmware
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 sheetCM-1 Policy and Procedures · CM-3 Configuration Change Control