United States

DoD Cloud Computing Security Requirements Guide (CC SRG) v1r3

32 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

32 controls 0 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1-2Purpose, authority, scope and background0
3Information impact levels 2, 4, 5 and 60
4Risk assessment of cloud service offerings and the DoD provisional authorization0
5.1Apply the FedRAMP baseline plus the DoD FedRAMP+ controls and parameter values for the impact level0
5.10.1Connect to DoD networks only through an approved Cloud Access Point: NIPRNet BCAP for off-premises Level 4 and 5, ICAP for on-premises, SIPRNet rules for Level 60
5.10.2Network planes: separate management and user or data planes, encrypted management traffic, VPNs and audited management transactions0
5.10.3Service architecture: CSP-provided defence in depth for IaaS and PaaS, SaaS assessed as a whole, disaster recovery replication over private or IPsec-protected paths0
5.10.4IP addressing and DNS: DoD address space via the BCAP, no Internet reachability of NIPRNet-only services, .mil records in DoD DNS with DNSSEC0
5.10.5-6Mission owner duties using SaaS and IaaS or PaaS: defence in depth, STIGs, CSSP alignment, encryption at rest with DoD keys, one-way AD trusts0
5.11Encryption of data at rest with exclusive DoD control of keys0
5.12Backups: CSP backups under CP-9, mission owner responsibility and off-CSP copies for higher impact data0
5.13-14DoD contractors and mission partners using CSOs; test and development zones in the cloud0
5.15-17Ports, protocols and services registration, mobile code restrictions, and system registration and connection approval0
5.18Supply chain risk management plan and component authenticity0
5.19Electronic mail protections: DoD email hygiene and routing rules for cloud-hosted mail0
5.2.1Keep DoD data under exclusive US legal jurisdiction and list every storage location0
5.2.2Separation requirements by impact level: virtual separation at Level 4, dedicated government community infrastructure at Level 5, classified facilities at Level 60
5.2.3DoD owns all DoD data in the CSO, including logs; the CSP may not use it0
5.3.1Continuous monitoring after the PA: scans, annual assessment, reporting to DISA0
5.3.2Change control: security impact analysis and 30-day notice of significant changes to DISA0
5.4DoD PKI: CAC or alternate token for DoD users, DoD or NSS certificate revocation checking, PK-enabled portals, two-factor for CSP privileged users0
5.5Apply DoD SRGs and STIGs: mission owners for their systems at all levels, CSPs on dedicated DoD infrastructure0
5.6.1Facilities: FedRAMP Moderate physical security at Level 2, plus FedRAMP+ physical controls at Levels 4 and 5, cleared secure facilities at Level 60
5.6.2CSP personnel: US citizenship or nationality at Levels 4 and 5, position categorisation, background investigations, clearances at Level 6, training0
5.7Data spill handling: report, remediate across all copies, cryptographic erase or prescribed sanitisation0
5.8Off-boarding: return all mission data and audit logs in a usable format, then cryptographically erase and certify destruction0
5.9Media sanitisation before reuse or disposal: purge to NIST SP 800-88 at Levels 4 and 5, destroy where purge is uncertain0
6.1-4Cyberspace defence roles: boundary defence by DISA, mission defence by the mission owner's CSSP, CSP cooperation with DoD defenders0
6.5.1Incident response plan or DoD addendum covering all incidents and breaches with notice to the government0
6.5.2-3Incident reporting: categories, timelines, formats and the reporting mechanism to DoD0
6.5.4Digital forensics: capture, preserve and protect incident information with hashes, encryption, segregation and chain of custody for law enforcement0
6.6-6.10Act on DoD directives, meet POA&M remediation timelines, notify scheduled outages, use PKI for defence communications, share vulnerability and threat information0

Tell me when DoD Cloud Computing Security Requirements Guide (CC SRG) v1r3 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for DoD Cloud Computing Security Requirements Guide (CC SRG) v1r3, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition