SC-36 Distributed Processing and Storage. Distribute the following processing and storage components across multiple [organization-defined]: [organization-defined]
Distributed Processing and Storage. Distribute the following processing and storage components across multiple [organization-defined]: [organization-defined].
5
artefacts
1
held by a system
2
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
- Monitoring of the distributed components for compromise, since distribution alone does not detect it · SIEM / log platform
periodic reviewEvidence produced at each review
- Evidence the locations are genuinely independent, covering power, network and provider dependencies · Cloud console / configuration management
- Test evidence that loss of one location leaves the function operating · Document repository
governing documentDocuments that govern the control
- The defined processing and storage components required to be distributed, and the defined locations they are distributed across · Document repository
- Architecture documentation showing the actual distribution achieved · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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
- Distribution across availability zones sharing one region, one provider and one control plane
- Storage distributed while the processing that depends on it sits in a single location
- Distribution never failure tested, so the surviving location's capacity is 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 sheetSC-35 External Malicious Code Identification. Include system components that proactively seek to identify network-based malicious code or malicious websites · SC-37 Out-of-band Channels. Employ the following out-of-band channels for the physical delivery or electronic transmission of [organization-defined] to [organization-defined]: [organization-defined]