EvidenceSheet

PL-7 Concept of Operations. Develop a Concept of Operations (CONOPS) for the system describing how the organization intends to operate the system from the perspective of information security and privacy; and Review and update the

Concept of Operations. Develop a Concept of Operations (CONOPS) for the system describing how the organization intends to operate the system from the perspective of information security and privacy; and Review and update.

5
artefacts
0
held by a system
2
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

  • Evidence the CONOPS covers operating modes, operator roles and the security assumptions behind them · Identity provider / directory
  • Review and update records against the defined frequency · Document repository

governing documentDocuments that govern the control

  • The Concept of Operations document describing how the system is intended to be operated from a security and privacy perspective · Policy repository / GRC workspace
  • Traceability from the CONOPS to the system security plan and privacy plan, showing they agree · Policy repository / GRC workspace
  • Approval of the CONOPS by the accountable system owner · 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

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 sheet

PL-4 Rules of behavior · PL-8 Security and privacy architectures