6.9.5 Control of operational software
Control over the installation of software on operational systems applies as the base guidance requires, read as protecting systems that process personal data from unreviewed change.
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
- Records of approved installations · Document repository
governing documentDocuments that govern the control
- Installation control procedure for operational systems · Policy repository / GRC workspace
- Detection of unauthorised software · 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
- Control applied to servers while endpoints holding personal data are unmanaged
- Approval evidenced by a change ticket that carries no privacy consideration
- No detection, so unauthorised installation is discovered only by accident
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 sheet6.9.4 Logging and monitoring · 6.9.6 Technical vulnerability management