Impact Level 6 (IL6) is the highest level in the DoD Cloud Computing Security Requirements Guide (CC SRG). It covers cloud services that process classified information up to SECRET. Unlike the lower levels, it involves classified handling that FedRAMP does not cover, so the cleared facilities, cleared people, and classified networks involved change how you design, operate, and evidence the environment.
What it is
The Cloud Computing SRG is published by the Defense Information Systems Agency (DISA) on behalf of the DoD CIO. It defines how DoD components assess and authorize commercial and DoD-operated cloud services. It is DoD policy and guidance that binds through acquisition and authorization decisions. It is not a statute or a public certification scheme.
The SRG sorts cloud workloads into impact levels by the sensitivity of the data. In the current structure these are IL2, IL4, IL5 and IL6. IL2 covers non-controlled unclassified information, IL4 covers controlled unclassified information (CUI), and IL5 covers higher-sensitivity CUI and national security systems. IL6 is the only level for classified information, up to SECRET. The SRG has been revised several times, so check DISA's current release rather than relying on a version number quoted in a secondary source.
For IL2 through IL5, the SRG layers DoD-specific requirements on top of the FedRAMP baselines. IL6 is built differently. FedRAMP does not authorize cloud services for classified data, so IL6 adds the CNSSI 1253 Classified Information Overlay and requirements from the DoD's classified-systems policies on top of the SRG's NIST SP 800-53-based control baseline; check the current SRG release for the exact composition.
Who it applies to
IL6 applies when a DoD mission owner wants to place classified information, up to SECRET, in a cloud environment. In practice that means:
- Cloud service providers (CSPs) that offer a classified region or enclave and want DoD to use it for SECRET workloads.
- DoD components and mission owners that must authorize and operate systems in such an environment.
- Contractors and integrators building or running classified workloads, who must also meet industrial security requirements under the National Industrial Security Program (NISP), including facility clearances and contract security specifications.
If your data is CUI or unclassified, IL4 or IL5 is the relevant target, not IL6. Information classified above SECRET (for example TOP SECRET or compartmented programs) is handled under separate intelligence community and program-specific rules, not under IL6.
Key requirements and control areas
What distinguishes IL6 from IL5 is mostly about classification handling, not just a longer control list.
Classified-capable control baseline
The control set builds on the SRG's NIST SP 800-53-based baseline and adds the CNSSI 1253 Classified Information Overlay for national security systems. The overlay adds or tightens controls around handling, marking, access, auditing, and media protection for classified data.
Physical and personnel security
- Facilities that host and operate the environment must be approved for classified processing, with physical protections that match the classification level.
- Personnel with logical or physical access to the environment need appropriate clearances and a need to know. Expect U.S. citizenship requirements for operators and administrators.
- Contractor facilities and staff fall under NISP requirements, administered through the Defense Counterintelligence and Security Agency (DCSA).
Network isolation and connectivity
IL6 environments are connected to DoD classified networks (SIPRNet) rather than the internet. They are separated from unclassified and lower-impact-level environments. Connections to other classification domains involve controlled interfaces such as approved cross-domain solutions. Design reviews therefore focus on boundary definition, data flow, and strict separation of management planes.
Cryptography and key management
Classified data protection relies on NSA-approved cryptography. Depending on the architecture, that can mean approved classified-grade encryption or layered commercial solutions under NSA programs. Get the exact requirements from the SRG and the authorizing officials, because they drive architecture choices early.
Supply chain and operations
- Controls on hardware and software provenance, and on who can touch the infrastructure.
- Incident response and reporting that follows DoD classified-incident procedures, including spillage handling.
- Auditing, continuous monitoring and configuration management run within the classified boundary, so tooling must be able to operate there.
Assessment, audit and enforcement
There is no public certificate. Authorization follows the DoD Risk Management Framework (based on NIST SP 800-37) in two stages:
- Provisional Authorization (PA): DISA evaluates a CSP's offering against the SRG and issues a PA that records the assessed risk. Other DoD components can use it as a basis for their own decisions.
- Authority to Operate (ATO): The mission owner's authorizing official decides whether to accept the residual risk for a specific system and workload in that environment. A PA does not by itself authorize a mission system.
Assessments rely on documentation, testing and on-site review in cleared facilities, with continuous monitoring afterwards. Because of the classification, much of the evidence and assessment activity takes place within classified systems and cannot be exported or shared like commercial audit evidence. Enforcement is contractual and administrative: loss or non-grant of authorization, contract consequences, and, for mishandling classified information, security-violation processes under national security law and policy.
A practical path to readiness
- Confirm the need for IL6. Check the classification of the data with the program's security classification guide. Do not default to IL6 for sensitive but unclassified data.
- Establish industrial security standing. For contractors, confirm facility clearance status, personnel clearances and the contract security specification before any technical work touches classified data.
- Engage DISA and the authorizing official early. Agree on scope, whether you are pursuing a PA or an ATO, and the applicable SRG version and overlays.
- Define the authorization boundary. Document system components, network paths, administrative interfaces, data flows and external connections, including any cross-domain links.
- Select and tailor controls. Start from the baseline specified in the applicable SRG release plus the CNSSI 1253 classified overlay, then record tailoring decisions and inheritance from the underlying facilities and services.
- Design for the classified enclave. Plan cryptography, key management, identity, logging and monitoring so they run inside the boundary. Do not assume SaaS tooling is available.
- Prepare the security package. Produce the system security plan, assessment results, and plan of action and milestones in the formats the authorizing body expects.
- Support the assessment. Provide access, evidence and technical staff for testing and on-site review.
- Run continuous monitoring. Track control effectiveness, vulnerabilities, changes and incidents on the cadence the authorization sets, and report as required.
How it maps to other frameworks
- NIST SP 800-53 and CNSSI 1253: The strongest overlap. IL6 control content derives from 800-53 as tailored for national security systems. Work done on 800-53 transfers well, but the classified overlay adds requirements.
- DoD RMF (NIST SP 800-37): The process framework IL6 authorizations follow.
- FedRAMP and IL2/IL4/IL5: Related lineage, but FedRAMP does not cover classified data. A FedRAMP authorization is not a path to IL6.
- NIST CSF: Useful for organizing and communicating the program, but it is not a substitute for IL6 control requirements.
- ISO 27001 and SOC 2: Partial overlap in areas such as access control, change management and incident response. They do not address classified handling, cleared personnel or NSA-approved cryptography, so they give little credit toward IL6.
These are overlaps in control intent, not equivalence. Do not expect another framework's report to satisfy an IL6 assessor.
FAQs
Is IL6 the same as IL5 with more controls?
No. IL5 covers unclassified information, including higher-sensitivity CUI and national security systems. IL6 is for classified information up to SECRET, and adds classified-network connectivity, cleared facilities and personnel, and NSA-approved cryptography on top of a different baseline.
Can a FedRAMP High authorization get me to IL6?
No. FedRAMP does not authorize services for classified data. FedRAMP lineage helps at the lower impact levels, but IL6 needs its own DoD assessment against classified requirements.
Does IL6 allow TOP SECRET data?
No. IL6 is scoped to information up to SECRET. Higher classifications and compartmented programs are handled under separate rules and authorities.
Who grants the authorization?
DISA issues provisional authorizations for cloud offerings, and the mission owner's authorizing official grants the ATO for a specific system. The exact roles of other bodies, such as NSA and DCSA, depend on the program and arrangement, so confirm them with your authorizing officials.
Can we use commercial compliance tools in an IL6 environment?
Only if the tool can operate within the classified boundary and is approved for it. Evidence from classified systems generally cannot be moved to unclassified or commercial SaaS platforms. Teams often prepare the process, mappings and unclassified design work outside the enclave, and keep classified evidence inside it.
How Aristiun helps
IL6 work relies on a clear control picture, well-organized evidence and early risk analysis. Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. Teams can use it to organize and prepare the parts of an IL6 effort that are not themselves classified, and to keep related programs aligned with their compliance frameworks.
- Cross-framework mapping: map controls across 340+ frameworks with continuous evidence collection, so NIST 800-53 work supports related obligations from a single evidence base.
- Gap analysis: AI-powered validation checks that evidence meets auditor expectations and flags gaps early.
- Real-time control monitoring: alerts when controls drift out of compliance, so you can remediate before assessors find issues.
- Automated threat modeling: generate threat models from code, IaC and architecture diagrams to test boundary and data-flow designs.