PM-3 Information Security and Privacy Resources
Funds C-SCRM as a line of work rather than expecting it from existing capacity.
3
artefacts
0
held by a system
2
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
- Staffing allocated to supplier assessment and monitoring · SIEM / log platform
- Evidence resource requests are considered in planning · Document repository
governing documentDocuments that govern the control
- Budget lines covering C-SCRM activity · Document repository
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 assigned with no resource so it happens only after an incident
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 sheetPM-2 Information Security Program Leadership Role · PM-4 Plan of Action and Milestones Process