PL-7 Concept of Operations
Describes how the system will actually be operated, including which parts suppliers and providers operate and the boundaries between them.
3
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
- Review on change · Document repository
governing documentDocuments that govern the control
- Concept of operations naming operational responsibilities · Policy repository / GRC workspace
- Split of duties between organization and providers · 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
- operating model undocumented so responsibility gaps appear during incidents
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-4 Rules of Behavior · PL-8 Security and Privacy Architectures