PL-11 Baseline tailoring
Requires the selected control baseline to be tailored by applying documented tailoring actions such as scoping, compensating control selection and parameter assignment, so the baseline reflects the actual system and risk
4
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Record of organization-defined parameter values assigned during tailoring · Document repository
governing documentDocuments that govern the control
- Documented tailoring actions with the rationale for each · Document repository
- Approval of the tailored baseline by the responsible authority · Policy repository / GRC workspace
- Traceability from tailoring decisions into the security plan · 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
- Controls removed during tailoring with no documented rationale or approval
- Parameter values left unset, so several controls have no measurable target
- Tailoring performed once and never reconciled with later system changes
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-10 Baseline selection · PM-1 Information Security Program Plan. Develop and disseminate an organization-wide information security program plan that: Provides an overview of the requirements for the security program and a description of the security program management controls and