PL-10 Baseline selection
Requires a control baseline to be selected for the system, so that the starting set of controls is chosen deliberately against the system's categorization rather than assembled ad hoc.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Approval evidence for the selection · Document repository
governing documentDocuments that govern the control
- Documented baseline selection decision and the categorization it follows from · Policy repository / GRC workspace
- Security plan section recording the selected baseline · Policy repository / GRC workspace
- Traceability from the baseline to the controls implemented · 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
- Baseline never formally selected, so control scope is inferred after the fact
- Selection inconsistent with the recorded security categorization
- Selection made once and not revisited when the categorization changed
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. Centrally manage [organization-defined] · PL-11 Baseline tailoring