OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening
Harden production system components to generally accepted industry standards, document the hardening requirements for each component, verify immutable images against those requirements when the images are created, and re
4
artefacts
2
held by a system
1
at each review
easy
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Build pipeline output showing the compliance check applied to a golden image · Source control / CI pipeline
- Configuration drift report against the baseline for a sample of running hosts · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Record of approved baseline exceptions with technical justification · Cloud console / configuration management
governing documentDocuments that govern the control
- Hardening baseline document per operating system, database and hypervisor type · Policy repository / GRC workspace
First move
Automate the pull from your Source control / CI pipeline. Pull-request approvals, pipeline test results and deployment records from source control, per release.
Common gaps auditors find
- A public benchmark cited without stating which settings were adopted or waived
- Baseline applied at build time only while running systems drift unchecked
- No baseline defined for newer component types such as orchestration platforms
- Exceptions granted informally, leaving the effective baseline unknown
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 sheetOPS-22 Testing and Documentation of known Vulnerabilities · OPS-24 Separation of Datasets in the Cloud Infrastructure