Defence contractors often assume that a CMMC Level 2 environment also satisfies ITAR, but the two regimes ask different questions: CMMC asks whether controlled information is protected to a security baseline, while ITAR asks who, by nationality and authorisation, can reach technical data and where it goes. A system can pass every NIST SP 800-171 requirement and still cause an unauthorised export if a foreign national administrator or an offshore support engineer can read unencrypted drawings. This guide compares the two regimes as they apply to IT and security teams: scope, CUI versus ITAR technical data, cloud residency and access controls, and how to run one combined programme. It is for security leads, IT architects and export compliance officers at prime contractors and suppliers. For the whole defence industrial base picture see the Defence Industrial Base Cybersecurity Programme Guide; this page goes deeper on where CMMC and ITAR diverge.
Status checked 14 November 2026: the DoD CIO CMMC page states that Phase I began on 10 November 2025, that Phase II (scheduled for 10 November 2026) was suspended on 13 July 2026 with a reform task force established, that the programme is paused in Phase 1 with NIST SP 800-171 Rev 2 enforced through self-assessments and select government-led assessments, and that the pause does not remove DFARS 252.204-7012 obligations. ITAR (22 CFR Parts 120 to 130) is in force. Both can change: confirm against the official sources before relying on this page.
Key takeaways
- Different questions, overlapping data. CMMC protects CUI against a control baseline; ITAR controls the export and release of defence articles and technical data. Much ITAR technical data is also CUI, so both apply to the same files.
- CMMC compliance does not make a system ITAR-safe. NIST SP 800-171 is nationality-blind; ITAR makes nationality and authorisation part of access control.
- A FedRAMP Moderate equivalent cloud answers DFARS, not export control. For ITAR data the questions are where it is stored, who at the provider can see it unencrypted, and who holds the keys.
- Encryption can take storage out of export scope. 22 CFR 120.54(a)(5) treats properly end-to-end encrypted unclassified technical data as not exported, if strict conditions hold, including no third-party access to decryption means.
- Run one programme, two owners. One data map and one enclave, with security owning the 800-171 controls and export compliance owning jurisdiction, classification and person eligibility decisions.
The short answer
CMMC (32 CFR Part 170 and DFARS 252.204-7021) is a contractual assurance programme: it verifies that a contractor handling federal contract information or CUI has implemented FAR 52.204-21 or NIST SP 800-171 requirements, through self-assessment or third-party and government assessment depending on level. ITAR is an export control regulation administered by the State Department's Directorate of Defense Trade Controls: it applies to defence articles, services and technical data on the US Munitions List whether or not there is a DoD contract, and a breach can be a violation of law, not only of contract. If you hold ITAR technical data on a DoD programme, you need both: the 800-171 baseline for the CUI, and US person or authorised access, location and encryption controls for the export controlled subset.
Scope side by side
| Dimension | CMMC | ITAR |
|---|---|---|
| Legal basis | 32 CFR Part 170; DFARS 252.204-7021 in contracts | Arms Export Control Act; 22 CFR Parts 120 to 130 |
| Administered by | Department of Defense (DoD CIO) | Department of State, Directorate of Defense Trade Controls |
| Triggered by | A DoD contract or solicitation requiring a CMMC level | Handling defence articles, services or technical data, regardless of customer |
| Protected information | Federal contract information (Level 1) and CUI (Levels 2 and 3) | Technical data as defined in 22 CFR 120.33, plus defence articles and services |
| Core question | Are the required security controls implemented and assessed? | Has any export, reexport, retransfer or release occurred without authorisation? |
| Control set | FAR 52.204-21 (Level 1); NIST SP 800-171 Rev 2 (Level 2); selected NIST SP 800-172 requirements (Level 3) | No control catalogue: outcome-based prohibitions, licences and agreements |
| Who is the risk | Any unauthorised party, external or internal | Foreign persons and prohibited destinations, including foreign nationals inside the US |
| Evidence | System security plan, SPRS score, assessment results, affirmations | Registration, jurisdiction and classification records, licences, access logs, voluntary disclosures where needed |
| Consequence of failure | Ineligibility for award, contract remedies, False Claims Act exposure | Civil and criminal penalties and debarment under the Arms Export Control Act |
CMMC Level 1 covers the 15 basic safeguarding requirements of FAR 52.204-21; Level 2 covers the 110 requirements of NIST SP 800-171 Rev 2. The levels are compared in CMMC Level 1 vs Level 2 vs Level 3, and the controls in the NIST SP 800-171 and CMMC 2.0 Guide.
CUI versus ITAR technical data
The two data definitions overlap but are not the same set, and the difference drives design.
- Technical data (ITAR): 22 CFR 120.33 defines it as information, other than software as defined in 120.40(g), required for the design, development, production and related activities for defence articles, plus classified information relating to defence articles and services, information covered by an invention secrecy order, and software directly related to defence articles. It excludes general scientific, mathematical or engineering principles commonly taught in schools, public domain information, certain telemetry data, and basic marketing information on function or purpose.
- CUI (CMMC): information the government creates or possesses, or a contractor creates for it, that a law, regulation or policy requires to be safeguarded. DFARS 252.204-7012 calls the contractual subset covered defense information: unclassified controlled technical information or other CUI Registry information, marked or provided by or for DoD, or collected, developed or stored in support of contract performance.
- The overlap: the CUI Registry has a category called Export Controlled, which names ITAR and the Export Administration Regulations. Specified authorities in that category carry the banner
CUI//SP-EXPT; basic authorities carryCUI(orCUI//EXPT). ITAR technical data provided under a DoD contract is therefore usually both CUI and export controlled. - Outside the overlap: ITAR technical data developed on a company's own funds, or for a foreign government customer, is still ITAR controlled with no CUI marking and no CMMC obligation. Conversely, much CUI (privacy, procurement or general controlled technical information) is not export controlled.
| Data example | CUI? | ITAR? | Design consequence |
|---|---|---|---|
| DoD-furnished drawings of a USML Category XI component | Yes (Export Controlled) | Yes | 800-171 baseline plus US person or authorised access and location controls |
| Company-funded design for a USML item sold to an allied government | No | Yes | Export controls apply even though CMMC does not; keep it in the same enclave anyway |
| Contract deliverable schedule marked CUI | Yes | No | 800-171 baseline; nationality not a factor |
| Product brochure describing function and purpose | No | No (basic marketing exclusion) | Normal corporate controls |
Jurisdiction and classification (ITAR, EAR or not controlled) is a legal determination made by export compliance, not by IT. The security team's job is to make that determination visible: a register of programmes, repositories and data sets with their jurisdiction, used to drive labels, DLP rules and repository permissions. See the CUI Guide for marking and dissemination.
Threat models compared
CMMC: confidentiality against a baseline
The CMMC threat model is the familiar one: external intrusion, credential theft, malware and insider misuse leading to CUI exfiltration. The 110 Level 2 requirements answer it with account management, multifactor authentication, boundary protection, encryption, logging and incident response. The DFARS 252.204-7012 clause adds the reporting side: rapid reporting within 72 hours at dibnet.dod.mil using a DoD-approved medium assurance certificate, and preservation of images and monitoring data for at least 90 days after the report. Nothing in this model distinguishes a US citizen administrator from a foreign national with the same role.
ITAR: unauthorised export and release
The ITAR threat model is about authorised people in the wrong category and data in the wrong place. Release to a foreign person inside the United States can be an export, so a perfectly legitimate employee, contractor or managed service engineer can be the failure. So can a cloud provider's support staff in another country with access to unencrypted data, a backup replicated to a region outside the US, or a collaboration tool that lets an external guest from a foreign partner open a file before an agreement is in place. Many of these events produce no security alert at all, because no control was bypassed.
Failure modes that only one regime catches
| Event | CMMC view | ITAR view |
|---|---|---|
| Foreign national IT administrator with legitimate privileged access to the engineering file server | Compliant if least privilege, MFA and logging are in place | Potential unauthorised release unless authorised by licence or other approval |
| Cloud tenant meets FedRAMP Moderate equivalent but provider support is global | Meets the 7012 cloud requirement | Risk if support staff can access unencrypted technical data |
| Phishing compromise leads to theft of drawings by a foreign actor | Cyber incident: 72-hour report under 7012 | Unauthorised export: a matter for export compliance and counsel |
| Engineers email ITAR drawings to a personal account | CUI spill and policy breach | Possible export depending on recipient and location |
| Missing audit log retention on a file share | Requirement not met | Weakens the ability to show who accessed what |
Cloud residency and access controls
Cloud is where the regimes most often get conflated. DFARS 252.204-7012 requires an external cloud service provider that stores, processes or transmits covered defense information to meet security requirements equivalent to the FedRAMP Moderate baseline, and to support the clause's incident reporting, malware, preservation and forensic access requirements. That is a security baseline. It does not, on its own, establish where data is stored or the nationality of the people who can reach it, which is what ITAR is concerned with.
The encryption route
22 CFR 120.54(a)(5) provides that sending, taking or storing technical data is not an export if the data is unclassified, secured with end-to-end encryption, protected by cryptographic modules compliant with FIPS 140-2 or its successors (or other means giving at least the security of AES-128), and not intentionally sent to or stored in, or sent from, a country proscribed in 22 CFR 126.1. A note states that data in transit over the internet is not treated as stored in the countries it passes through. Section 120.54(b) defines end-to-end encryption as protection from the originator, or the originator's in-country security boundary, to the intended recipient, with no third party given the means to decrypt; and 120.54(c) says that accessing technical data in encrypted form meeting (a)(5) is not a release or export.
For architects the operative words are "no third party given the means to decrypt". A design that relies on this route needs:
- Customer-controlled keys: keys generated and held in a FIPS validated module under the contractor's control, with the provider unable to use them on its own authority. See Cloud Customer-Managed Keys and BYOK/HYOK Decision Guide.
- Decryption only at authorised endpoints: data decrypted inside the contractor's boundary or by eligible users, never in provider-managed services that need plaintext (search indexing, previews, AI features) unless those services are themselves within an authorised boundary.
- Validated modules: check the module certificate, not the vendor's marketing claim. See FIPS 140-2 vs FIPS 140-3.
- Location rules: region and backup configuration that keeps data out of 126.1 countries, documented.
The personnel route
Where data must be processed in plaintext, organisations instead use cloud environments whose support and operations staff are contractually limited to US persons, and whose data stays in US regions. This is a contractual and operational property of the service, so verify it in the service terms and the provider's own compliance documentation, and record the evidence in the export compliance file. Combine both routes where possible: US person operated environments with customer-held keys.
Identity and access attributes
ITAR makes person eligibility an access control input, which 800-171 role models do not carry. Practical patterns:
- Eligibility attribute: a directory attribute such as "export authorised for programme X", set by export compliance from HR and licence records, never self-asserted. Use it in attribute-based policies on repositories, PLM and file shares. See the Authorisation Models Guide.
- Privileged and service accounts: administrators, backup operators and service accounts with read access to plaintext data are in scope for eligibility too, including managed service provider staff. See the Defence Industrial Base Identity Security Guide.
- External collaboration: guest access to ITAR repositories blocked by default and enabled only against a recorded licence or agreement, with expiry matched to it.
- Location signals: conditional access that blocks or challenges sessions from 126.1 countries and flags travel, as supporting evidence rather than the sole control.
Combined programmes
Running CMMC and ITAR as separate projects duplicates the data map, the enclave and the evidence. A combined programme builds one model and derives both.
- Map data once. Inventory federal contract information, CUI, ITAR technical data, EAR technology and proprietary data, with flows from receipt to supplier. Mark the ITAR subset with its jurisdiction decision.
- Choose one boundary. Put CUI and ITAR technical data in the same enclave where possible, and apply the stricter ITAR personnel and location rules to the whole enclave. Splitting them into two enclaves adds cost and creates transfer paths. See the CMMC Scoping Guide for the asset categories.
- Write one system security plan that describes the 800-171 controls and, in a separate section, the export control overlay: eligibility attributes, key custody, cloud locations and the export compliance owner.
- Split ownership clearly. Security owns control implementation and SPRS scoring; export compliance owns registration, jurisdiction and classification, licences and eligibility decisions; legal owns voluntary disclosure decisions.
- Join incident handling. Any 7012 incident involving ITAR data triggers an export compliance review in parallel with the 72-hour report, because the two processes have different owners and different questions.
- Test before cut-over. Pilot the eligibility attribute in audit mode, logging which accesses would have been denied, before enforcing; keep the old permissions export to restore if engineering work stops.
Worked scenario
A 300-person machining supplier receives DoD drawings for a USML component under a contract with the 7012 clause and a Level 2 requirement, and also does company-funded design work for an allied customer. It has two engineers who are foreign nationals working on commercial programmes, and an outsourced IT provider with a support desk abroad.
- The supplier builds one engineering enclave in a US region cloud tenant whose operations staff are contractually US persons, with customer-managed keys in a FIPS validated module.
- Both the DoD drawings and the allied customer design files live in the enclave; the allied work is ITAR only, but one boundary is simpler than two.
- Export compliance sets the eligibility attribute; the two foreign national engineers do not receive it, and their commercial work stays outside the enclave.
- The outsourced IT provider's offshore desk manages the corporate network only; enclave administration moves to a US person team with separate privileged accounts.
- The SSP documents all 110 requirements for the enclave and the export overlay. The SPRS score covers the enclave; export compliance keeps the eligibility and key custody evidence.
Decision criteria
- CMMC only: you handle CUI with no export controlled content. Focus on 800-171 implementation and assessment readiness.
- ITAR only: commercial or foreign military sales work with no DoD contract clauses. No CMMC level applies, but you still need person eligibility, location and encryption controls, and many organisations adopt the 800-171 baseline anyway as a recognised standard.
- Both: DoD contracts involving USML items. Build the combined programme above.
- Small suppliers: a single cloud enclave with US person operations and customer-held keys is usually cheaper than securing the whole company. Large primes: expect multiple enclaves by programme and classification, with eligibility attributes integrated with HR and licence systems and regular reconciliation.
Detection and measurement
Log and review access to export controlled repositories by user, eligibility attribute value, location and device; administrative actions in the enclave; key usage events from the key management service; sharing and guest invitations; and region or replication changes. Feed denied access attempts by ineligible users to export compliance as well as the SOC.
- Eligibility coverage: percentage of accounts with access to ITAR data that carry a current eligibility decision (target 100%).
- Attribute drift: accounts whose eligibility changed in HR or licence records but not in the directory within the agreed number of days.
- Key custody: percentage of ITAR data stores encrypted with customer-controlled keys in validated modules.
- Location exceptions: sessions or storage events in proscribed countries (target zero), and time to review each one.
- Joint incident review: percentage of 7012 incidents involving ITAR data with a documented export compliance review.
Framework mapping
| Control area | NIST SP 800-171 Rev 3 reference | NIST SP 800-53 Rev 5 | ITAR overlay |
|---|---|---|---|
| Accounts and access enforcement | 03.01.01 Account Management; 03.01.02 Access Enforcement | AC-2, AC-3 | Eligibility attribute in access policy |
| Flow of controlled data | 03.01.03 Information Flow Enforcement | AC-4 | Block transfer to ineligible users and proscribed locations |
| External systems and collaboration | 03.01.20 Use of External Systems | AC-20, AC-21 | Guest access only against a licence or agreement |
| Boundary | 03.13.01 Boundary Protection | SC-7 | Enclave boundary as export control boundary |
| Cryptography | 03.13.11 Cryptographic Protection | SC-13 | FIPS validated modules and customer-held keys for 120.54(a)(5) |
| Logging | 03.03.01 Event Logging | AU-2 | Evidence of who accessed which technical data |
CMMC Level 2 assessments currently use NIST SP 800-171 Rev 2, whose requirement numbering differs; the Rev 3 identifiers are shown because they align with SP 800-53 and are the current NIST revision.
Common failure patterns
- "We passed CMMC, so we are ITAR compliant": the SSP never mentions nationality, offshore support or key custody.
- FedRAMP equated with ITAR: a FedRAMP Moderate equivalent tenant is chosen, but provider support or backups sit outside the US with access to plaintext.
- Provider-held keys relied on for the encryption carve-out: the provider can decrypt, so the third-party condition in 120.54(b) fails.
- Privileged access forgotten: engineers are checked for eligibility, but domain administrators, backup operators and MSP staff are not.
- Separate incident tracks: the SOC files the 72-hour report and closes the case, and export compliance never hears that technical data left.
- Self-asserted citizenship: the eligibility attribute is editable from a profile page or populated from an unverified field.
Practitioner checklist
- Record the CMMC programme status and the eCFR check date in the SSP and re-check quarterly.
- Keep a jurisdiction register for every programme and repository, owned by export compliance.
- Put CUI and ITAR technical data in one enclave with the stricter ITAR rules applied throughout.
- Confirm in writing where the cloud provider stores data, backups and logs, and the nationality terms for its support staff.
- Hold keys for ITAR data in FIPS validated modules under your control if you rely on 120.54(a)(5).
- Drive access from an eligibility attribute set by export compliance, including for administrators and service providers.
- Block guest sharing to ITAR repositories except against a recorded licence or agreement.
- Link the 7012 incident process to an export compliance review.
- Measure eligibility coverage, key custody and location exceptions monthly.
Standards and references
- eCFR: 22 CFR 120.54 Activities that are not exports, reexports, retransfers, or temporary imports
- eCFR: 22 CFR 120.33 Technical data
- DoD CIO: About CMMC
- Acquisition.gov: DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting
- National Archives: CUI Category Export Controlled
- NIST: SP 800-171 Rev. 3 Protecting Controlled Unclassified Information
- NIST: SP 800-53 Rev. 5 Security and Privacy Controls
This guide summarises CMMC and the ITAR as they apply to information security and is not legal advice; export jurisdiction, classification and licensing decisions belong to your export compliance function and counsel. Related NHI Mgmt Group resources: Defence Industrial Base Cybersecurity Programme Guide, CMMC Scoping Guide, NIST SP 800-171 and CMMC 2.0 Guide, Encryption Export Controls Guide.