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

DoD Cloud Computing SRG Impact Level 2 (IL2): A Practical Guide

What DoD CC SRG Impact Level 2 covers, who needs it, how it relates to FedRAMP Moderate, and a step-by-step path for cloud providers and DoD mission owners.

DoD Cloud Computing SRG Impact Level 2 (IL2): A Practical Guide

Impact Level 2 (IL2) is the lowest of the impact levels defined in the Department of Defense Cloud Computing Security Requirements Guide (CC SRG). It covers cloud use for DoD information that is not Controlled Unclassified Information (CUI), and in practice it rests on the FedRAMP Moderate baseline. This article covers what is specific to IL2 and leaves the wider DoD cloud program to the parent guide.

What it is

The Cloud Computing Security Requirements Guide is published by the Defense Information Systems Agency (DISA) under the authority of the DoD Chief Information Officer. It sets out how DoD assesses and authorizes commercial and non-DoD cloud services, and how DoD components may use them. It is a DoD policy and requirements document, not a statute. It becomes binding on cloud providers mainly through contract terms and DoD acquisition rules, and on DoD components through DoD policy.

The guide defines impact levels, which combine the sensitivity of the information with the potential effect of its compromise. The levels are IL2, IL4, IL5 and IL6. IL2 is the baseline for information approved for public release and other non-CUI. Anything that is CUI, or that supports national security systems, needs a higher level. IL2 therefore suits public-facing websites, general collaboration on non-sensitive material, and development and test workloads that hold no CUI.

The guide has been revised several times. A version 1, release 4 exists, but DoD cloud policy and the FedRAMP program have both been changing, so check the current DISA publication rather than relying on a cached copy.

Who it applies to

IL2 matters to three groups:

  • Cloud service providers (CSPs) that want DoD customers to use their offering for non-CUI workloads.
  • DoD mission owners, meaning the components and programs that buy and operate cloud services and remain responsible for authorizing their own use.
  • Contractors and integrators that build or run systems on a DoD component's behalf in a commercial cloud.

The data classification drives the level. If the information is CUI, including CUI that DoD contractors handle, IL2 is not enough and the workload needs IL4 or above. Misclassifying data is a frequent IL2 mistake: teams assume a workload is "just unclassified" without checking whether it contains CUI.

For acquisition, the DFARS cloud computing clause (252.239-7010) requires contractors providing cloud services to DoD to hold a DoD provisional authorization at the level appropriate to the data. That is the contractual route by which the CC SRG reaches providers. It is separate from DFARS 252.204-7012, which covers contractor systems that hold covered defense information and has its own requirements.

Key requirements and control areas

IL2 is unusual because it adds little of its own. Its main features are:

  • FedRAMP Moderate as the control baseline. For IL2, DoD accepts a FedRAMP Moderate authorization. The provider's control set is the NIST SP 800-53 Moderate baseline, assessed through the FedRAMP process. Higher levels add DoD-specific controls and parameters on top of FedRAMP, and IL2 does not.
  • Reciprocity. A provider with a valid FedRAMP authorization at Moderate or above can generally be used by DoD for IL2 workloads without a separate DISA assessment. The details of how DoD recognizes FedRAMP authorizations, including the move from FedRAMP Rev 4 to Rev 5 baselines, have been changing, so confirm the current position.
  • Simpler connectivity. IL2 workloads are not generally required to connect through the DoD boundary protections used for higher levels, because the data is not sensitive. Connection to DoD networks, where it exists, still needs mission-owner design and approval.
  • Lighter requirements on location and personnel. The stricter controls on data location, separation from non-DoD tenants and personnel screening arrive at higher levels. Check the current guide for exact IL2 wording rather than assuming none exist.
  • Mission-owner responsibilities. Under the shared responsibility model, the DoD component or its contractor still has to configure the service securely, manage identities and access, protect the data, and obtain its own authorization to operate for the system. A provider's authorization does not transfer to the customer's system.

The practical control areas are therefore the NIST SP 800-53 families that FedRAMP Moderate covers (access control, audit and accountability, configuration management, incident response, contingency planning, system and communications protection, and others), plus the customer-side configuration of the service.

Assessment, audit and enforcement

For the provider, IL2 assessment runs through FedRAMP. An accredited third-party assessment organization (3PAO) tests the offering, and the provider obtains an authorization through the FedRAMP process, followed by ongoing continuous monitoring overseen by the authorizing agency and FedRAMP. DISA's own provisional authorization process is generally associated with IL4 and above.

For the DoD customer, the mission owner uses the provider's authorization package as input to a system-level authorization under the DoD risk management framework. The authorizing official accepts or rejects the residual risk. Continuous monitoring continues after authorization.

Enforcement is mostly contractual and administrative. A provider without the required authorization can lose or fail to win DoD business. Non-compliance with DFARS clauses can carry contractual remedies, and a mission owner that runs workloads without proper authorization faces internal DoD consequences. IL2 has no standalone fine regime.

A practical path to meeting IL2

  1. Classify the data. Confirm with the contracting officer or data owner that the workload holds no CUI and no information requiring a higher level. Document the decision.
  2. Determine your role. Decide whether you are the provider seeking authorization, a mission owner, or a contractor operating on a component's behalf.
  3. Check existing authorizations. Providers should confirm their FedRAMP status and baseline level. Customers should check that the chosen service holds a current FedRAMP authorization at Moderate or higher and confirm how DoD currently recognizes it.
  4. Define the shared responsibility split. List which controls the provider inherits to you and which you must implement, using the provider's customer responsibility documentation.
  5. Implement customer-side controls. Configure identity and access, logging, encryption, backups, vulnerability management and incident response for your part of the stack.
  6. Assemble the authorization package. Build the system security plan, assessment results, and plan of action and milestones that your authorizing official needs.
  7. Obtain the authorization to operate from the appropriate DoD authorizing official, where the system requires one.
  8. Monitor continuously. Track control drift, provider authorization status and changes to the CC SRG, and re-assess when the data or the mission changes. Plan for an upgrade to IL4 if CUI enters the system.

How it maps to other frameworks

  • FedRAMP Moderate: the closest relationship. IL2 is built on FedRAMP Moderate, so a FedRAMP Moderate authorization is the main evidence for the provider side.
  • NIST SP 800-53: the underlying catalog for the FedRAMP baseline and for DoD's risk management framework.
  • NIST CSF: a partial overlap, useful for organizing the program, but CSF is not an authorization.
  • SOC 2 and ISO 27001: overlap in areas such as access control, logging, change management and incident response. Neither satisfies FedRAMP or DoD authorization on its own.
  • CMMC and DFARS 252.204-7012: related but different. They address contractor handling of federal contract information and CUI on contractor systems, not cloud authorization levels.

FAQs

Is IL2 the same as FedRAMP Moderate?

No, but it is closely tied to it. IL2 is a DoD impact level for non-CUI data, and DoD accepts a FedRAMP Moderate authorization as the control basis for it. IL2 itself is a DoD classification of use, not an additional certification.

Can I store CUI in an IL2 environment?

No. CUI generally requires IL4 or higher. If you cannot rule out CUI, treat the workload as needing a higher level.

Does a provider need a DISA provisional authorization for IL2?

Generally the FedRAMP authorization is what matters at IL2, with DISA provisional authorizations associated with higher levels. DoD's recognition processes have been evolving, so check current DoD guidance and your contract.

Does the provider's authorization cover my system?

No. It covers the provider's service. You remain responsible for your configuration, data and any system-level authorization your DoD authorizing official requires.

How often does it need reassessment?

Authorizations rely on continuous monitoring rather than a one-time check. Re-review whenever the data sensitivity, the service or the CC SRG changes significantly.

How Aristiun helps

Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. For IL2 work, where the control baseline is shared with FedRAMP Moderate and NIST SP 800-53, one evidence base can serve several requirements at once. See the compliance frameworks Aristiun covers.

  • Collect evidence automatically from connected systems such as AWS, Azure, GCP and GitHub, without manual screenshots or spreadsheets.
  • Map each piece of evidence to the relevant controls across all applicable frameworks at once.
  • Monitor control effectiveness and get alerts when controls drift, so you can remediate before auditors find issues.
  • Generate auditor-friendly reports with evidence pre-mapped to controls, and use AI-powered gap analysis to find missing evidence early.

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.