ITAR
ITAR Technical Data and NIST SP 800-171
If you hold ITAR technical data, you likely have to meet two rule sets at once. One controls who may see the data, and one controls how your systems guard it.
Cybersecurity Consulting, a Capital Cyber practice in Leesburg, Virginia, provides CISO level leadership for CMMC, NIST SP 800-171 and federal authorization, with a program for ITAR technical data.
How does ITAR technical data relate to NIST SP 800-171?
ITAR controls who may receive defense technical data, to keep it from unauthorized foreign persons. NIST SP 800-171, required through DFARS 252.204-7012, sets security rules for systems holding Controlled Unclassified Information. That includes export controlled data.
A maker holding ITAR drawings usually must satisfy both.
What counts as ITAR technical data?
It is information needed to design, develop, make, assemble, run, repair, test, maintain or modify a defense article. The article is on the United States Munitions List.
It covers blueprints, drawings, photos, plans, instructions and documents, in any form. Software directly tied to defense articles is treated in a similar way.
Public domain information is excluded. So are general science, math and engineering principles taught in schools.
Whether a file is technical data is a classification call. It belongs to your export compliance team, not IT. IT needs to know which data was classified that way and where it lives.
How is ITAR different from NIST SP 800-171?
ITAR asks who may access the data. Could a foreign person receive it without an authorization? NIST SP 800-171 asks how the system is secured: access control, logging, encryption, incident response and the rest.
Meeting one does not meet the other. A system can meet all 110 requirements and still let a foreign person read an ITAR drawing if nobody checked the users.
A system can limit access by citizenship and still fail CMMC because nobody reviews its logs. Design for both from the start.
Is ITAR technical data also CUI?
Usually yes, when created or received under a DoD contract. Export controlled information is a category in the federal CUI program. So DFARS 252.204-7012 applies to the systems that hold it.
That overlap helps. One enclave, built for both rule sets, can hold both.
Access rules are tighter, since export control asks who is a U.S. person. But systems, documents and evidence can be shared.
What does DFARS 252.204-7012 add?
It adds security, reporting and cloud rules on top of export rules. Covered defense information, which includes controlled technical information and other CUI, must be protected by NIST SP 800-171.
Cyber incidents affecting it must be reported to DoD within 72 hours of discovery. Images and relevant data must be kept for DoD to review.
A cloud service holding this data must meet security equal to the FedRAMP Moderate baseline. It must also follow the clause's rules on incident reports, malicious software and forensics. The clause flows down to subcontractors who handle the data, so a prime's duties become its suppliers' duties.
What is the 22 CFR 120.54 encryption carve out?
It lists acts that are not exports. One is sending, taking or storing unclassified technical data protected by end to end encryption that meets the rule. Then it is not an export, even if the encrypted data passes through or rests on servers abroad.
The rule sets conditions. Data is encrypted before it leaves the sender's security boundary and stays encrypted until the intended recipient decrypts it.
The crypto is validated under FIPS 140 or at least as effective as the rule describes. The data is not sent to a person in, or stored in, a country the ITAR proscribes. Read the rule text before relying on it.
Why does the carve out matter?
Cloud services rarely show every place data rests or every person who runs the systems. Without the carve out, you would need certainty that no unauthorized foreign person could reach the clear data. Properly applied encryption can change that analysis.
It is not a shortcut. The data is still CUI, DFARS 7012 still applies, and whoever decrypts it must be authorized.
Key control is central. If the provider holds the keys, the conditions may not be met. Show who controls the keys and where decryption happens.
How should a manufacturer set up for both rules?
Start with classification and data flow. Which customers send ITAR technical data, in what form, and who needs it?
Then build an enclave only authorized users can reach. Record U.S. person status where it matters, and apply all 110 NIST SP 800-171 requirements.
Pick platforms that support the duties in contract and in practice. Document encryption and key custody if you rely on 120.54.
Train people who handle drawings, shop floor included. A drawing handed to the wrong visitor is an export problem no firewall will catch.
Where do contractors get this wrong?
First, they assume a compliant cloud settles the export question. Access decisions, foreign national staff, offshore IT vendor support and visiting engineers are your calls, not the platform's.
Second, they treat ITAR as paperwork for contracts staff. Technical data lives in CAD systems, file shares, email and machine controllers.
If security does not know which files are controlled, it cannot protect them. Keep export compliance and security talking. Each holds half the answer.
Next step: book a 30 minute call with the practice to map your ITAR data and enclave.