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