SC-44 Detonation Chambers. Employ a detonation chamber capability within [organization-defined]
Detonation Chambers. Employ a detonation chamber capability within [organization-defined].
5
artefacts
1
held by a system
3
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
- Configuration showing which content types are detonated and the verdict handling · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Design evidence showing the chamber is isolated from production networks and identity systems · Document repository
- Records of detonations performed and malicious verdicts acted on · Document repository
- Evidence of anti evasion measures, since malware that detects analysis will behave benignly · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Identification of where the detonation chamber capability is employed, such as at mail or web ingress or in an isolated analysis environment · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management 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
- Chamber network connected in a way that lets detonated code call out to production or to the identity provider
- Only executable attachments detonated while archives, links and document macros bypass
- Verdicts produced after the content has already been delivered, with no retraction step
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-43 Usage Restrictions. Establish usage restrictions and implementation guidelines for the following system components: [organization-defined] ; and Authorize, monitor, and control the use of such components within the system · SC-45 System Time Synchronization. Synchronize system clocks within and between systems and system components