EvidenceSheet

5.8 Information security in project management

Requires information security to be integrated into the way projects are managed, so security is handled inside the project method rather than bolted on after delivery.

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

  • Security risk assessments produced for projects in the period, including projects that are not IT projects · Document repository
  • Evidence of security requirements being set at initiation and verified before go live · Document repository
  • Records of security sign off at project stage gates, naming the approver · Document repository
  • Evidence that the same treatment applies to agile and to vendor led delivery, not only to waterfall projects · Vendor register / contract repository

governing documentDocuments that govern the control

  • The project methodology or gating documentation showing information security as a defined step, not an optional one · 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

5.7 Threat intelligence · 5.9 Inventory of information and other associated assets