Skip to main content
Intelligent Security Governance — 340+ Frameworks Powered by Ayurak AI
Blog/Compliance Guides

DoD Cloud Computing SRG Impact Level 5 (IL5): A Practical Guide

What DoD Cloud Computing SRG Impact Level 5 requires, who needs it, how DISA provisional authorization works, and how to prepare. A practical guide for cloud providers and mission owners.

DoD Cloud Computing SRG Impact Level 5 (IL5): A Practical Guide

Impact Level 5 (IL5) is the level of the Department of Defense Cloud Computing Security Requirements Guide (CC SRG) for cloud services that hold higher-sensitivity Controlled Unclassified Information (CUI) and certain unclassified national security systems. It builds on FedRAMP Moderate, then adds DoD-specific controls, stronger separation and tighter connectivity rules. This article covers what is specific to IL5; the parent program is covered in a sibling post.

What it is

The Cloud Computing SRG is published by the Defense Information Systems Agency (DISA) on behalf of the DoD. It is not a statute. It is DoD security guidance that becomes binding through DoD policy and contract clauses. It defines how DoD components may use commercial and non-DoD cloud services, and what a cloud service provider (CSP) must show before DoD missions can host data there.

The SRG sorts information into impact levels by the sensitivity of the data and the criticality of the mission. In broad terms:

  • IL2: non-controlled, publicly releasable or low-sensitivity information.
  • IL4: CUI and other non-critical mission information.
  • IL5: higher-sensitivity CUI, mission-critical information, and unclassified national security systems.
  • IL6: classified information up to Secret.

The SRG has been revised several times, and the DoD has recently been adjusting how it treats FedRAMP alignment and equivalency. Check DISA's current published release before scoping work rather than relying on a version cited in older material.

Who it applies to

Two groups are in scope, with different obligations:

  • Cloud service providers that want to offer a service to DoD mission owners at IL5. They need a DoD Provisional Authorization (PA) from DISA for the specific cloud service offering.
  • DoD mission owners (components, programs, and contractors operating systems on their behalf) that deploy workloads in an authorized cloud. They remain responsible for their own system authorization (an ATO) and for the security of what they build on top of the CSP's service.

Contractors are affected directly when a contract includes DFARS clause 252.239-7010 (Cloud Computing Services), which requires cloud services provided to DoD to meet the SRG and the relevant PA requirements. Separately, DFARS 252.204-7012 governs covered defense information held by contractors and has its own FedRAMP Moderate-equivalence expectations for external cloud providers. That clause is not the same as IL5, so treat the two as distinct obligations.

Which level applies is decided by the data and mission, not by the CSP's preference. Determination is made by the mission owner, and it is common for a service to be authorized at more than one level.

Key requirements and control areas

IL5 is not a standalone control catalog. It starts from the FedRAMP Moderate baseline, which derives from NIST SP 800-53, and layers on SRG-specific requirements. The areas that distinguish IL5 from lower levels are these.

Baseline plus additional controls

The CSP must meet the FedRAMP Moderate baseline and an additional set of DoD-specific controls and parameter values (often called "FedRAMP+"). A FedRAMP authorization is a practical prerequisite, but it does not by itself satisfy IL5.

Separation from non-federal tenants

This is the biggest architectural difference from IL4. IL5 data must be separated from the data of non-federal tenants, either through dedicated infrastructure or through strong logical separation in an environment limited to federal government tenants. Multi-tenant public cloud regions open to any customer generally do not meet this on their own, which is why providers stand up dedicated or government-only regions for IL5.

Connectivity and boundary protection

IL4 and IL5 workloads are expected to connect to DoD networks through DoD-approved boundary and cloud access point arrangements, so that traffic is inspected and defended under DoD network-defense rules. Mission owners must design network architecture to fit those patterns instead of exposing workloads directly.

Personnel and data location

The SRG places stricter requirements on who may administer the environment, including personnel screening and citizenship or residency conditions for those with logical access to IL5 data, and it constrains where data may be stored and processed, generally within the United States or its outlying areas. Confirm the exact current wording in the SRG, since these clauses drive staffing and support models.

Cyber defense and incident reporting

Mission owners must have cybersecurity service provider (CSSP) coverage for their systems, and CSPs must support DoD incident reporting and response expectations.

Shared responsibility

The PA covers the CSP's service. The mission owner must still document inherited and customer-owned controls, and secure configuration, identity, logging, and data protection in their own tenancy.

Assessment, audit and enforcement

There is no self-attestation path. A CSP is assessed by an independent assessor and submits its package to DISA, which reviews it and, if satisfied, issues a Provisional Authorization at the requested level. FedRAMP packages can be reused as the starting point, with DoD-specific controls assessed in addition. Authorized services are listed in the DoD cloud service catalog.

A PA is not a system ATO. Each mission owner's authorizing official still decides whether to accept the risk for a specific system, using the PA as inherited evidence. After authorization, CSPs are expected to run continuous monitoring, report on a regular cadence, handle significant changes through DoD's change processes, and remediate findings tracked in a plan of action and milestones (POA&M).

Enforcement is mainly contractual and administrative. A CSP without the needed PA cannot be used for the relevant DoD workloads, and a contractor that breaches a DFARS cloud clause faces ordinary contract remedies. There is no separate statutory fine schedule for the SRG itself.

A practical path to IL5

  1. Confirm the required level. As a CSP, confirm demand and the data types your DoD customers will place in the service. As a mission owner, categorize the information and mission criticality formally.
  2. Define the authorization boundary. Scope the specific service offering, its dependencies, and the regions or environments that will host IL5 workloads.
  3. Design the separation model. Decide on dedicated or government-only infrastructure, and confirm that tenancy, management plane and support tooling meet the separation requirements.
  4. Close the FedRAMP Moderate baseline. Complete or maintain a FedRAMP authorization, since it is the foundation of the package.
  5. Add the DoD-specific controls. Gap-assess against the SRG's additional requirements, including personnel, data location and boundary connectivity, and fix architecture and staffing issues early because they are the slowest to change.
  6. Document responsibilities. Produce a customer responsibility matrix showing what the CSP provides and what mission owners must implement.
  7. Engage an independent assessor and DISA. Complete the assessment, address findings, and submit the package for provisional authorization.
  8. Operate continuous monitoring. Maintain scanning, evidence, POA&M tracking, and change management to a cadence that keeps the authorization valid.
  9. For mission owners: build and authorize your system. Inherit the PA, implement customer-side controls, connect through approved paths, and obtain your ATO.

How it maps to other frameworks

  • FedRAMP: the strongest overlap. IL5 builds on the FedRAMP Moderate baseline, but it adds DoD-specific controls and separation requirements. FedRAMP authorization is not IL5 authorization.
  • NIST SP 800-53: the underlying control catalog for both. IL5 control selection and parameters come from it.
  • NIST SP 800-171 and CMMC: these protect CUI on contractor systems. They overlap in subject matter with IL5 controls, but they apply to a different problem and are assessed differently.
  • ISO 27001 and SOC 2: partial overlap in areas like access control, logging and change management. Neither substitutes for a DISA PA, though existing evidence can support parts of the package.

These are overlaps in control intent, not equivalence.

FAQs

What is the difference between IL4 and IL5?

Both cover CUI, but IL5 is for higher-sensitivity CUI and mission-critical or national security system data. The main practical difference is stronger separation from non-federal tenants and tighter requirements around the environment.

Does FedRAMP High satisfy IL5?

Not automatically. IL5 is defined by the SRG, with its own additional controls and separation rules, and it requires a DoD Provisional Authorization. A FedRAMP High package can be useful evidence, but it does not replace DISA's review.

Is a Provisional Authorization the same as an ATO?

No. The PA authorizes the cloud service offering for use at a given level. Each mission owner still needs an ATO for its own system hosted on that service.

Can a contractor self-certify IL5?

No. IL5 requires independent assessment and DISA's authorization decision. Contractors can, however, use services that already hold an IL5 PA and then authorize their own systems.

How long does it take?

It varies widely with the maturity of the existing FedRAMP package, the architecture, and the findings. Separation and personnel requirements are the usual sources of delay, so plan for a multi-month effort at minimum.

How Aristiun helps

Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. For IL5 work, the value is in keeping a large control set, and the evidence behind it, current across both the CSP and mission-owner sides. You can browse compliance frameworks to see how this fits with the rest of your program.

  • Cross-framework mapping across 340+ frameworks, so evidence collected for FedRAMP, NIST 800-53 or ISO 27001 maps to relevant controls simultaneously and a single evidence base serves multiple requirements.
  • Automated evidence collection from connected systems such as AWS, Azure, GCP and GitHub, without manual screenshots or spreadsheets.
  • Real-time control monitoring with alerts when controls drift out of compliance, so you can remediate before an assessor finds the issue.
  • Automated threat modeling from code, IaC and architecture diagrams, plus gap analysis and audit-ready reports organized by framework requirement.

Found this insightful?

Share it with your security team or save it for later.

Get Started

Ready to secure your organization?

See how Aristiun automates compliance and strengthens your security posture across 340+ frameworks.