PL-10 Baseline Selection
Selects the control baseline with supply chain risk taken into account, so C-SCRM controls are chosen rather than assumed.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Baseline selection record including C-SCRM control choices · Cloud console / configuration management
governing documentDocuments that govern the control
- Rationale for inclusion or exclusion · Document repository
- Approval of the selected baseline · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- C-SCRM controls dropped in tailoring with no rationale
- baseline selected before criticality is understood
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 sheetPL-9 Central Management · PM-2 Information Security Program Leadership Role