SC-39 Process Isolation
Maintain separate execution domain for each executing system process.
6
artefacts
1
held by a system
1
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
- TLS configuration scan results across in scope endpoints · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Denial of service protection configuration and capacity test results · Source control / CI pipeline
governing documentDocuments that govern the control
- Control implementation statement for SC-39 citing the system mission and inheritance from common controls · Document repository
- Network segmentation diagrams with VLAN and zone mapping · Policy repository / GRC workspace
- Boundary protection architecture with firewall and proxy rule documentation · Policy repository / GRC workspace
- Cryptographic standards specifying approved algorithms and key lengths · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Vulnerability scanner / patch tooling on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Flat networks expose sensitive workloads without segmentation
- Cryptographic keys stored alongside the data they protect
- Firewall rule base contains stale allow any entries
- Internal traffic between services unencrypted within trusted zones
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 sheetSC-28(1) Cryptographic Protection · SC-45 System Time Synchronization. Synchronize system clocks within and between systems and system components