Impact Level 4 (IL4) is the Department of Defense baseline for cloud services that handle Controlled Unclassified Information (CUI). It sits on top of FedRAMP Moderate and adds DoD-specific requirements, connectivity rules and a DISA-issued provisional authorization. This guide covers what is specific to IL4, not the wider Cloud Computing Security Requirements Guide (CC SRG) program.
What it is
The DoD Cloud Computing Security Requirements Guide is published by the Defense Information Systems Agency (DISA) on behalf of the DoD CIO. It defines how DoD assesses and authorizes commercial and non-commercial cloud service offerings, and how DoD components (mission owners) may use them. It is a DoD policy and requirements document, not a statute, and it is not a voluntary standard. DoD has revised the guide several times since its first release in 2015. Check the current version on DISA's cyber exchange before scoping work, because the guide has changed over time and may have changed again.
The SRG groups cloud workloads into Impact Levels by data sensitivity:
- IL2: non-CUI information cleared for public release or with low confidentiality impact.
- IL4: CUI, including information that requires protection under law, regulation or government-wide policy, in non-national-security systems.
- IL5: higher-sensitivity CUI and unclassified national security systems, with stronger separation requirements.
- IL6: classified information up to SECRET.
IL4 is the entry point for most CUI workloads. It is built on the FedRAMP Moderate baseline, with additional DoD-specified controls and enhancements layered on top, often called "FedRAMP+".
Who it applies to
Two groups are affected, and their obligations differ.
- Cloud service providers (CSPs) that want to host DoD CUI workloads. A DoD component generally cannot place that data in a cloud service offering unless DISA has issued a DoD Provisional Authorization (PA) at the appropriate level. DFARS clause 252.239-7010 reflects this for contractors providing cloud computing services to DoD.
- Mission owners: DoD components, and contractors operating systems on their behalf. They must select an authorized offering, configure it properly, connect it to DoD networks as required, and obtain their own system-level authorization under the DoD Risk Management Framework.
Contractors who only handle covered defense information in their own environment, rather than providing cloud services to DoD, are usually looking at DFARS 252.204-7012 and CMMC, not IL4. Under 7012, an external cloud provider storing covered defense information must meet FedRAMP Moderate or an equivalent. That is related to IL4 but is a different obligation. A contractor should confirm which clause and contract language actually applies before pursuing IL4.
Key requirements and control areas
Baseline plus DoD-specific controls
The starting point is the FedRAMP Moderate baseline, derived from NIST SP 800-53. The SRG then specifies additional controls, parameter values and enhancements. Many of these tighten requirements on areas such as auditing, incident response, cryptography, configuration management and personnel security. FedRAMP baselines have been moving to newer NIST 800-53 revisions, so confirm which revision and which DoD overlay the assessment will use.
Separation and tenancy
IL4 allows more shared infrastructure than IL5, but it still requires logical separation of DoD CUI workloads from other tenants. Describe in detail how tenant isolation works, because assessors examine it closely.
Connectivity and boundary protection
A defining feature of IL4 is how the workload connects to DoD networks. Mission owners generally reach IL4 cloud environments through DoD-controlled network paths (the Cloud Access Point architecture and its associated boundary and security stack components, for example), rather than only over the open internet. These components, and who operates them, have changed over time, so verify current DISA guidance. The mission owner is responsible for much of this boundary design, not the CSP alone.
Data location and personnel
The SRG places conditions on where data is stored and processed and on who may administer the environment. Restrictions on US data location and on personnel screening are tightest at higher levels. Confirm the exact IL4 requirements in the current SRG rather than assuming them.
Continuous monitoring and incident reporting
Authorized CSPs must keep producing monitoring evidence, such as vulnerability scans, plan-of-action items and change notifications. They must also follow DoD incident reporting procedures, which differ from commercial notification practice.
Shared responsibility documentation
Both CSP and mission owner must document who implements each control. Unclear responsibility is a common source of assessment findings.
Assessment, audit and enforcement
For CSPs, the path normally runs through a FedRAMP-recognized Third Party Assessment Organization (3PAO), which tests the offering against FedRAMP Moderate and the DoD additions. DISA then reviews the package and decides whether to issue a DoD Provisional Authorization. A FedRAMP Moderate authorization helps, because DoD can reuse much of that work, but it does not by itself confer IL4. The DoD-specific controls and connectivity must still be assessed.
A PA is not a system authorization. Each mission owner must still complete an assessment and obtain an Authorization to Operate (ATO) from its authorizing official under the DoD RMF, inheriting what it can from the CSP's PA. Enforcement is mostly contractual and procedural: DoD can decline to authorize, revoke or restrict a PA, and contracts can carry clauses that require compliance. Specific penalties are not stated here because they depend on the contract.
A practical path to IL4
- Confirm the need. Identify whether you are a CSP, a mission owner or a contractor handling CUI in your own environment, and which contract clauses apply.
- Classify the data. Establish that the workload is CUI and decide whether IL4 or IL5 is correct. Under-classifying is a common and costly mistake.
- Get the current SRG and overlays. Download the current guide, control baselines and DISA templates, and note the version your assessment will use.
- Achieve or confirm FedRAMP Moderate. Most IL4 efforts build on an existing FedRAMP authorization.
- Run a gap analysis on the DoD additions. Compare your implementation against the extra IL4 controls, parameters and connectivity requirements.
- Remediate and document. Update the system security plan, shared responsibility matrix, architecture diagrams and boundary definition.
- Engage a 3PAO and DISA. Agree on the assessment scope early and submit the package through the DoD process.
- Handle mission-owner authorization. Customers need their own ATO and network connectivity, so support them with inheritable evidence.
- Sustain continuous monitoring. Keep scans, POA&M updates and change notifications current so the PA is not put at risk.
How it maps to other frameworks
- FedRAMP: the strongest overlap. IL4 builds on FedRAMP Moderate, but the DoD additions and connectivity requirements mean FedRAMP alone is not sufficient.
- NIST SP 800-53: the underlying control catalog for both FedRAMP and the SRG.
- NIST SP 800-171 and CMMC: related protection of CUI, but aimed at contractor systems rather than cloud service authorization. Overlap exists in control topics, not in assessment process.
- ISO 27001 and SOC 2: partial overlap in areas such as access control, logging and change management. Neither substitutes for a DoD provisional authorization.
- NIST CSF: a useful way to organize and communicate the program, but not a compliance route to IL4.
FAQs
Is IL4 a certification?
No. It is an authorization level. DISA issues a DoD Provisional Authorization for a cloud service offering, and mission owners then authorize their own systems.
Does FedRAMP Moderate satisfy IL4?
Not on its own. IL4 uses FedRAMP Moderate as its base but adds DoD-specific controls and connectivity requirements that must be assessed.
What is the difference between IL4 and IL5?
Both cover CUI. IL5 covers higher-sensitivity CUI and unclassified national security systems, and demands stronger separation and tighter conditions than IL4.
Can a contractor simply use an IL4 cloud and be compliant?
Using an authorized offering is necessary but not sufficient. The mission owner still must configure it correctly, meet connectivity requirements and obtain its own ATO.
Does IL4 apply to every defense contractor?
No. It applies to cloud providers serving DoD and to mission owners hosting DoD CUI workloads. Other contractors are more likely to be subject to DFARS 252.204-7012, NIST SP 800-171 and CMMC.
How Aristiun helps
Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. IL4 work involves a large evidence base spanning NIST 800-53-derived controls, DoD additions and continuous monitoring, and the platform is built to reduce the manual effort in that. It maps controls across 340+ compliance frameworks with a single evidence base, so evidence gathered for related frameworks such as FedRAMP or NIST 800-53 can be reused where controls overlap.
- Map controls across 340+ frameworks, with each piece of evidence linked to the relevant controls at once.
- Collect evidence automatically from connected systems such as AWS, Azure, GCP and GitHub, instead of using screenshots and spreadsheets.
- Monitor control effectiveness and get alerts when controls drift, so you can remediate before an assessor finds the issue.
- Use AI-powered gap analysis and generate auditor-friendly reports organized by framework requirement, and generate threat models from code, IaC and architecture diagrams to support boundary and architecture documentation.