US Export Controls: ITAR (defense) + EAR (dual-use commercial) compliance

version
0.1.0
GitHub stars
436

Install

/plugin install us-export@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

US Export Controls Expert

Engineering guidance only. Not legal advice. Export-control determinations come from DDTC (ITAR) and BIS (EAR), not from this toolkit. The claims below are starting points for security engineers working with export-control counsel, not compliance positions to adopt as-is. Citations to read alongside this material: 22 CFR 120.54 (the ITAR encrypted-technical-data carve-out: access to properly-keyed, end-to-end-encrypted technical data is not automatically a release), 22 CFR 122.5 (ITAR recordkeeping, scoped to specific record categories), 15 CFR 734.6 (BIS is the licensing authority on EAR), 15 CFR 746.8 (Russia and Belarus sanctions). The BIS country guidance is the live sanctions list; it moves and this file will lag.

Deep expertise in both ITAR (International Traffic in Arms Regulations) and EAR (Export Administration Regulations) for US export control compliance.

Expertise Areas

Dual Framework Overview

ITAR (International Traffic in Arms Regulations):

  • Authority: US Department of State, Directorate of Defense Trade Controls (DDTC)
  • Scope: Defense articles, services, and technical data on the US Munitions List (USML)
  • Registration: Required ($3,000/year)
  • Key posture (simplified): access restricted to US persons; technical data stored in US-located systems by default. The 22 CFR 120.54 encrypted-technical-data carve-out means "US-only storage" isn't an absolute rule for properly-encrypted data, so deployment patterns vary. Validate with counsel for your USML category.

EAR (Export Administration Regulations):

  • Authority: US Department of Commerce, Bureau of Industry and Security (BIS)
  • Scope: Dual-use commercial items on the Commerce Control List (CCL)
  • Registration: Not required (except encryption items)
  • Key posture (simplified): denied-party screening and sanctions-driven access controls. Under 15 CFR 734.6, BIS (not this toolkit) determines what licensing applies to any given item; specific-country rules live in 15 CFR 746 and shift regularly (Russia and Belarus under 746.8, Crimea/DNR/LNR under 746.6, etc.).

ITAR Framework (7 Controls)

ITAR-1: US Person Verification

Requirement: Only "US persons" may access ITAR-controlled technical data. 22 CFR 120.62 defines that term broader than "citizens or green-card holders." It covers:

  • US citizens (by birth or naturalization)
  • Lawful permanent residents (green-card holders)
  • "Protected individuals" under 8 USC 1324b(a)(3) (certain refugees, asylees, and specific visa holders)
  • US-incorporated entities and US governmental agencies (for entity-level access)

Access policies that say "citizens or LPRs only" over-restrict and can create avoidable HR and employment-law exposure. Use the full 120.62 definition; work with HR and counsel on how you verify each category.

Implementation:

  • Verify US-person status using documentation appropriate to the 120.62 category (I-9 covers employment eligibility, not ITAR 120.62 scope by itself)
  • Tag IAM users with US-person status
  • Implement RBAC limiting access to US persons
  • Re-verify periodically; document the method for each 120.62 category

Cloud Verification:

# AWS: Tag users with citizenship
aws iam tag-user --user-name john.smith --tags Key=Citizenship,Value=US

# List all users for verification
aws iam list-users --query 'Users[*].UserName'

Common Gaps:

  • Foreign nationals with admin access
  • Contractors without citizenship verification
  • Shared accounts without individual attribution
ITAR-2: Data-Residency Posture (US-Located by Default)

Posture summary: ITAR technical data is stored in US-located systems by default. 22 CFR 120.54 carves out end-to-end-encrypted technical data from the release definition, so there are deployment patterns where non-US storage of encrypted data is defensible. Defaulting to US-located regions is the simplest posture; confirm with counsel before relying on the encryption carve-out or any cloud-provider attestation.

Approved Regions:

  • AWS GovCloud: us-gov-west-1, us-gov-east-1 (highly recommended)
  • AWS Commercial: us-east-1, us-east-2, us-west-1, us-west-2 (with controls)
  • Azure Government: usgovvirginia, usgovtexas, usgovarizona (highly recommended)
  • GCP Assured Workloads: us-central1, us-east4, us-west1 (with ITAR configuration)

Prohibited:

  • Any non-US region (eu-west-1, ap-southeast-1, etc.)
  • Cross-border replication or backup
  • Edge caching outside US (CloudFront with EU edge)

Verification:

# AWS: Check S3 bucket locations
for bucket in $(aws s3api list-buckets --query 'Buckets[*].Name' --output text); do
  location=$(aws s3api get-bucket-location --bucket "$bucket" --query 'LocationConstraint' --output text)
  echo "$bucket: $location"
done
ITAR-3: Encryption Requirements

Requirement: FIPS 140-2 validated encryption for all ITAR data

Standards:

  • FIPS 140-2 Level 2+ (Level 3 for TOP SECRET)
  • Customer-managed encryption keys (CMEK) recommended
  • Hardware Security Modules (HSMs) required

Cloud Solutions:

  • AWS KMS: FIPS 140-2 Level 2 validated (Certificate #3139, #3195, #3520)
  • Azure Key Vault HSM: FIPS 140-2 Level 2 (Certificate #3347, #3653)
  • GCP Cloud KMS: FIPS 140-2 Level 3 (Certificate #3666, #4124)

Encryption Coverage:

  • Data at rest: EBS, S3, RDS, databases
  • Data in transit: TLS 1.2+ with FIPS cipher suites
  • Backups and snapshots
ITAR-4: Access Logging and Audit

Requirement summary: 22 CFR 122.5 requires ITAR-registered exporters to retain specific record categories (manufacturing, export transactions, broker records, and similar) for 5 years. This is not a blanket "retain every cloud log for 5 years" mandate. Identify which of your cloud logs carry those record categories and retain those for 5 years; treat general CloudTrail or admin-audit logs that aren't within 122.5 scope as a separate retention decision (operational, security-monitoring, etc.) and set that retention based on your own policy and any other applicable framework.

Logging scope that's usually worth capturing (operational + security, not all strictly under 122.5):

  • Management events (IAM changes, resource creation)
  • Data-access events (S3 object access, database queries)
  • Authentication and authorization events
  • Failed access attempts

Implementation:

  • AWS: CloudTrail with S3 logging. Retain 122.5-scope records for 5 years; set separate retention for general audit logs.
  • Azure: Activity Log, Monitor. Same scoping principle.
  • GCP: Cloud Logging with log exports. Same scoping principle.

Log Protection:

  • Log file validation enabled
  • Logs stored in separate security account
  • MFA delete protection on log buckets
ITAR-5: Network Isolation

Requirement: ITAR systems should be isolated from non-ITAR systems

Implementation:

  • Dedicated VPCs/VNets for ITAR workloads
  • No VPC peering to non-ITAR environments
  • Separate accounts/subscriptions/projects
  • Network segmentation with security groups/NSGs

Best Practice:

  • Use AWS Organizations or Azure Management Groups
  • ITAR workloads in separate organizational unit
  • Service Control Policies (SCPs) to enforce isolation
ITAR-6: Export Control Marking

Requirement: Mark all ITAR data with appropriate export control notices

Tagging Strategy:

AWS Resource Tags:
  ExportControl: "ITAR"
  Classification: "CUI" | "SECRET"
  Handling: "NOFORN" (No Foreign Nationals)
  Owner: "john.smith@company.com"

Document Marking:

WARNING: This document contains technical data whose export is
restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751,
et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C.,
App 2401 et seq.), as amended. Violations of these export laws are
subject to severe criminal penalties. Disseminate in accordance with
provisions of DoD Directive 5230.25.
ITAR-7: Third-Party Access Control

Requirement: Control access by cloud service providers and third parties

Implementation:

  • Use GovCloud/Government regions (US persons-only CSP staff)
  • Enable Customer Lockbox (Azure) for support approval
  • Service Control Policies to prevent external role assumption
  • Audit all cross-account access

Commercial Cloud:

  • AWS: US persons for GovCloud support
  • Azure: Screened personnel for Government cloud
  • GCP: Assured Workloads personnel controls

EAR Framework (7 Controls)

EAR-1: Export Control Classification (ECCN)

Requirement: Classify all items with proper ECCN or EAR99

Classification Process:

  1. Is item on USML? → Use ITAR (not EAR)
  2. Is item on CCL? → Assign ECCN
  3. Not on CCL? → Likely EAR99

Common ECCNs:

ECCNDescriptionLicense Required
5D002Encryption softwareOften License Exception ENC
5A002Encryption hardwareVaries by specification
5E002Encryption technologyVaries by specification
3A001Electronic equipmentVaries by destination
4A003Digital computersVaries by performance
EAR99Items not on CCLNo license for most destinations, but licenses can still be required based on destination (15 CFR 746), end-user (Entity List / DPL / SDN), or end-use (15 CFR 744 proliferation and military end-use rules)

Self-Classification:

  • Review CCL (15 CFR 774 Supplement No. 1)
  • Determine applicable category (0-9)
  • Assign ECCN based on specifications
  • Document classification rationale
EAR-2: End-User and End-Use Screening

Requirement: Screen all customers against BIS denied parties lists

Screening Lists:

ListAuthorityPurposeEntries
Entity ListBISNational security/foreign policy restrictions1,400+
Denied Persons List (DPL)BISExport privileges denied200+
Unverified List (UVL)BISEnd-use verification failed100+
Specially Designated Nationals (SDN)Treasury OFACSanctions program10,000+
Military End User (MEU)BISChina/Russia military restrictionsN/A
Foreign Sanctions Evaders (FSE)TreasurySanctions evasion70+

Screening Process:

  1. Collect customer information (name, address, country)
  2. Screen against all lists (consolidated screening)
  3. Document screening results and date
  4. Block access if match found
  5. Report matches to BIS/OFAC

Frequency:

  • Before provisioning new accounts
  • Quarterly for existing customers
  • After any BIS list update

Implementation:

# Pseudocode for screening
def screen_customer(customer_name, country):
    if customer_name in ENTITY_LIST:
        return "DENIED - Entity List match"
    if customer_name in DPL:
        return "DENIED - Denied Persons List"
    if customer_name in SDN:
        return "DENIED - OFAC SDN List"
    if country in EMBARGOED_COUNTRIES:
        return "DENIED - Embargoed country"
    return "APPROVED"
EAR-3: Encryption Compliance (FIPS 140)

Requirement: Encryption items (Category 5 Part 2) must use FIPS 140-2/140-3 validated modules

FIPS Validation:

  • AWS KMS: FIPS 140-2 Level 2 (Certificates #3139, #3195, #3520, etc.)
  • Azure Key Vault: FIPS 140-2 Level 2 (Certificates #3347, #3653)
  • GCP Cloud KMS: FIPS 140-2 Level 3 (Certificates #3666, #4124)

License Exception ENC:

  • Available for certain encryption items
  • Self-classification required
  • Semi-annual reporting to BIS
  • Not available for embargoed countries

Encryption Registration:

  • One-time registration with BIS
  • Submit product details and specifications
  • Required for ECCN 5A002, 5D002, 5E002
  • Update registration for product changes
EAR-4: Geographic Access Controls

Requirement: Block access from comprehensively embargoed countries

Embargoed Countries (no exports):

  • Cuba (CU)
  • Iran (IR)
  • North Korea (KP)
  • Syria (SY)
  • Crimea region of Ukraine

Partially Sanctioned (check specific restrictions):

  • Russia (RU) - electronics, semiconductors, certain technology
  • Belarus (BY) - similar to Russia restrictions
  • Venezuela (VE) - certain restrictions

Implementation:

AWS WAF Geo-Blocking:

{
  "Name": "EAR-Embargo-Block",
  "Rules": [{
    "GeoMatchStatement": {
      "CountryCodes": ["CU", "IR", "KP", "SY"]
    },
    "Action": "Block"
  }]
}

CloudFront Geo-Restrictions:

{
  "GeoRestriction": {
    "RestrictionType": "blacklist",
    "Items": ["CU", "IR", "KP", "SY", "UA"]
  }
}
EAR-5: Technology Transfer Controls

Requirement: Control export of technical data and source code

Technical Data Definition (EAR 734.2):

  • Information required for design, development, production, or use
  • Blueprints, plans, diagrams, models, formulae, tables
  • Engineering designs and specifications
  • Manuals and instructions written or recorded
  • Source code (depending on ECCN)

Deemed Exports (EAR 734.13):

  • Release of controlled technology to foreign nationals in the US
  • Considered an "export" to the person's country
  • May require license depending on technology and country
  • Visual inspection or oral exchange may constitute deemed export

Source Code Controls:

  • Classify source code (often ECCN 5D002 for encryption)
  • Restrict access by geography and screening
  • Control access to code repositories (GitHub, GitLab)
  • Watermark or mark source files
EAR-6: Cloud Service Provider Attestations

Requirement: Verify CSP provides EAR-compliant features

CSP Compliance Features:

ProviderFIPS 140-2CMEKData ResidencyGeo-Blocking
AWS✅ Level 2+✅ KMS✅ Regional✅ WAF, CloudFront
Azure✅ Level 2✅ Key Vault✅ Regional✅ Front Door, WAF
GCP✅ Level 3✅ Cloud KMS✅ Regional✅ Cloud Armor

Required Attestations:

  • FIPS 140-2 validation certificates
  • Customer-managed encryption keys available
  • No CSP access to customer data without permission
  • Data residency controls and documentation

BIS Cloud Computing FAQ:

  • Cloud services are generally "tools" not "items"
  • Customer responsible for export compliance
  • CSP should provide compliant features
EAR-7: License Exception Applicability

Requirement: Determine if License Exception applies (avoiding license requirement)

License Exception ENC (Encryption):

Eligibility:

  • Encryption items ECCN 5A002, 5D002, 5E002
  • Self-classification or BIS review
  • Not available for embargoed countries or denied parties

Requirements:

  • One-time encryption registration with BIS
  • Semi-annual self-classification reports
  • Maintain classification documentation

License Exception TSU (Technology and Software - Unrestricted):

Categories:

  • Publicly available technology/software
  • Educational information
  • Published materials (books, journals, conferences)
  • Not subject to proprietary/confidential restrictions

Note: Open source software may qualify for TSU

License Exception BAG (Baggage):

Eligibility:

  • Personal baggage exports
  • Tools of trade for business travelers
  • Laptops, phones with encryption

Limits: Reasonable quantities for personal/professional use

License Exception TMP (Temporary):

Eligibility:

  • Temporary exports/re-exports for:
    • Testing and evaluation
    • Demonstrations
    • Exhibitions and trade shows

Duration: Typically 1 year, renewable

Jurisdiction Determination

Decision Tree:

Step 1: Is the item on the US Munitions List (USML)?
├─ YES → ITAR applies (State Department DDTC jurisdiction)
│   └─ End analysis - use ITAR framework
└─ NO → Continue to Step 2

Step 2: Is the item on the Commerce Control List (CCL)?
├─ YES → EAR applies with specific ECCN
│   ├─ High-level ECCN (e.g., 5D002) → May require license
│   ├─ Check License Exceptions (ENC, TSU, BAG, TMP)
│   └─ Prohibited: embargoed countries, denied parties
└─ NO → Continue to Step 3

Step 3: Item not on USML or CCL
└─ Likely EAR99
    ├─ No license required for most destinations to most end-users
    ├─ License still required for exports to comprehensively embargoed destinations (15 CFR 746)
    ├─ License still required when end-user is on the Entity List, DPL, or SDN
    ├─ License still required for prohibited end-uses under 15 CFR 744 (proliferation, military end-use, military-intelligence end-use)
    └─ The "knowledge" standard applies: if you know or have reason to know the item is destined for a prohibited use or user, a license is required even for EAR99

Commodity Jurisdiction (CJ) Request:

  • Submit to DDTC if uncertain USML vs CCL
  • Form DS-4076
  • 60-day response time (can extend)
  • Binding determination

Framework Crosswalk

Overlapping Controls (implement once, satisfies both):

✅ FIPS 140-2 Encryption

  • ITAR-3 and EAR-3 both require FIPS 140-2
  • Same HSM standards (Level 2+)
  • Implementation: AWS KMS, Azure Key Vault HSM, GCP Cloud KMS

✅ Access Logging

  • ITAR-4 requires 5-year retention for the record categories named in 22 CFR 122.5 (not every log)
  • EAR benefits from logging as operational and audit evidence
  • Implementation: CloudTrail or equivalent, with retention scoped per 122.5 record categories

Framework-Specific Controls:

ITAR-Only:

  • ITAR-1: US Person Verification (not required for EAR)
  • ITAR-2: US-located residency by default, with the 22 CFR 120.54 encryption carve-out available (EAR geography is driven by sanctions and licensing, not a uniform rule)
  • ITAR-5: Network Isolation (not required for EAR)

EAR-Only:

  • EAR-1: ECCN Classification (ITAR uses USML categories)
  • EAR-2: Denied Party Screening (not ITAR requirement, but recommended)
  • EAR-7: License Exceptions (not available for ITAR)

Compliance Strategy:

  • If ITAR applies: Default to strictest controls (US-person access, US-located regions). The 22 CFR 120.54 encryption carve-out gives you some deployment flexibility if counsel blesses it.
  • If EAR applies: Apply ECCN-specific controls, denied-party screening, and the current 15 CFR 746 sanctions rules.
  • If both apply: Segregate systems OR apply ITAR defaults plus EAR additions.

Cloud Platform Recommendations

ITAR Workloads:

  1. AWS GovCloud (highly recommended)

    • FedRAMP High authorized
    • US persons-only personnel
    • Physical isolation from commercial
  2. Azure Government (highly recommended)

    • FedRAMP High authorized
    • Screened US personnel
  3. GCP Assured Workloads (recommended)

    • ITAR compliance configuration
    • Data residency enforcement

EAR Workloads:

  1. AWS Commercial (with controls)

    • FIPS 140-2 encryption via KMS
    • WAF for geo-blocking
    • Denied party screening in provisioning
  2. Azure Commercial (with controls)

    • FIPS 140-2 Key Vault
    • Front Door for geo-filtering
  3. GCP Commercial (with controls)

    • FIPS 140-2 Cloud KMS
    • Cloud Armor for geo-blocking

Common Implementation Challenges

  1. US Person Verification (ITAR)

    • Challenge: Citizenship documentation collection
    • Solution: Integrate with HR onboarding, maintain verification database
  2. Denied Party Screening (EAR)

    • Challenge: Real-time screening at scale
    • Solution: Automated screening APIs (Dow Jones, LexisNexis, OpenSanctions)
  3. Data Residency Compliance (ITAR)

    • Challenge: Accidental non-US region deployment
    • Solution: Service Control Policies, resource tagging policies
  4. ECCN Classification (EAR)

    • Challenge: Understanding CCL and determining ECCN
    • Solution: Consult trade compliance counsel, BIS ECCN search tool
  5. License Exception Determination (EAR)

    • Challenge: Knowing when exceptions apply
    • Solution: Document exception applicability, consult BIS guidance

Enforcement and Penalties

ITAR Violations:

  • Civil Penalties: Up to $1,162,989 per violation
  • Criminal Penalties: Up to $1,000,000 fine and 20 years imprisonment
  • Debarment: Loss of export privileges

EAR Violations:

  • Civil Penalties: Up to $364,992 per violation or 2x transaction value
  • Criminal Penalties: Up to $1,000,000 fine and 20 years imprisonment
  • Denial of Export Privileges: Loss of ability to export

Voluntary Self-Disclosure:

  • Mitigating factor in enforcement
  • Reduced penalties for self-reported violations
  • DDTC and BIS encourage self-disclosure

Resources

ITAR Resources:

EAR Resources:

Capabilities

  • ITAR vs EAR jurisdiction determination (USML vs CCL decision tree)
  • DDTC registration guidance and annual renewal process
  • US person verification strategies for cloud environments
  • FIPS 140-2 encryption implementation across AWS, Azure, and GCP
  • Denied party screening automation and API integration
  • ECCN classification for encryption software and technology
  • License Exception applicability (ENC, TSU, BAG, TMP)
  • Data residency verification: ITAR defaults to US-located storage (with the 22 CFR 120.54 encryption carve-out where counsel approves); EAR residency depends on ECCN, licensing posture, and current 15 CFR 746 sanctions
  • Cloud platform selection (GovCloud vs commercial) based on framework
  • Deemed export analysis for foreign national access to technical data
  • Crosswalk between ITAR and EAR overlapping and unique controls
  • Compliance cost estimation and resource planning
  • Export control marking and resource tagging strategies
  • Audit trail configuration and 5-year retention for records within 22 CFR 122.5 scope
  • Voluntary self-disclosure guidance for potential violations

Commands 6

US Export Controls Assessment

Engineering guidance only. Not legal advice. DDTC (ITAR) and BIS (EAR) are the authorities; the toolkit is not. Read alongside this: 22 CFR 120.54, 22 CFR 122.5, 15 CFR 734.6, 15 CFR 746.8, and the BIS country guidance. Work with counsel before adopting any posture.

Evaluates readiness for US export controls compliance across both ITAR (defense articles) and EAR (dual-use commercial) frameworks.

Arguments

  • $1 - Scope (optional: itar, ear, both) - defaults to "both"
  • $2 - Assessment depth (optional: quick, detailed) - defaults to "detailed"

Framework Selection

ScopeFrameworkWhen to Use
itarITAR onlyDefense articles on USML, technical data for defense
earEAR onlyDual-use commercial items on CCL, encryption products
bothITAR + EARUncertain jurisdiction, mixed product portfolio

Assessment Output

ITAR Assessment (7 controls):

  1. US Person Verification - Access limited to US citizens / permanent residents
  2. Data-Residency Posture - US-located storage by default; 22 CFR 120.54 encryption carve-out available with counsel sign-off
  3. Encryption Requirements - FIPS 140-2 validated encryption
  4. Access Logging - 5-year retention for records within 22 CFR 122.5 scope (not every log)
  5. Network Isolation - Dedicated VPCs / VNets for ITAR workloads
  6. Export Control Marking - Resources tagged with ITAR classification
  7. Third-Party Access Control - CSP access restrictions

EAR Assessment (7 controls):

  1. Export Control Classification - ECCN or EAR99 determination
  2. End-User Screening - Denied parties list checking (Entity List, DPL, SDN)
  3. Encryption Compliance - FIPS 140 for Category 5 Part 2 items
  4. Geographic Access Controls - Embargo country blocking (Cuba, Iran, NK, Syria)
  5. Technology Transfer Controls - Source code and technical data access controls
  6. CSP Attestations - Cloud provider FIPS encryption and CMEK verification
  7. License Exceptions - ENC, TSU, BAG applicability determination

Jurisdiction Determination:

  • Is the item on the USML (US Munitions List)? → ITAR
  • Is the item on the CCL (Commerce Control List)? → EAR with ECCN
  • Neither list? → Likely EAR99. No license for most destinations / end-users, but destination (15 CFR 746), end-user (Entity List / DPL / SDN), and end-use (15 CFR 744) rules still apply. The "knowledge" standard means a license can be required even for EAR99 if you know or have reason to know the item is destined for a prohibited use or user.

Compliance Status:

  • Compliant, Non-Compliant, Partially Compliant
  • Gap analysis with prioritized remediation steps
  • Registration/licensing requirements (DDTC for ITAR, BIS for EAR)

Examples

# Assess both frameworks (default)
/us-export:assess

# ITAR-only assessment for defense contractor
/us-export:assess itar detailed

# EAR-only quick assessment for commercial exporter
/us-export:assess ear quick

# Full assessment for mixed portfolio
/us-export:assess both detailed

Common Scenarios

Defense Contractor: ITAR applies - US person verification, GovCloud recommended Encryption Software: EAR applies - ECCN 5D002, License Exception ENC may apply Cloud Service Provider: Both may apply - implement geographic controls, screening Semiconductor Manufacturer: EAR applies - ECCN classification, Entity List screening

ITAR vs EAR Compliance Matrix

Engineering guidance only. Not legal advice. The matrix below is a simplified planning aid; DDTC and BIS make the actual determinations. The country lists, retention requirements, and residency postures shown here are starting points to discuss with export-control counsel. Sanctions rules in particular shift fast; verify against the BIS country guidance before acting on the country-list rows.

Side-by-side comparison of ITAR and EAR requirements to understand overlaps, differences, and compliance strategies.

Arguments

  • $1 - Focus area (optional: overview, controls, cloud, licensing) - defaults to "overview"

Framework Overview

AspectITAREAR
AuthorityState Department (DDTC)Commerce Department (BIS)
ScopeDefense articles, services, technical data (USML)Dual-use commercial items (CCL)
Item ListUS Munitions List (USML) - 21 categoriesCommerce Control List (CCL) - 10 categories
PersonnelUS persons per 22 CFR 120.62 (citizens, LPRs, "protected individuals" under 8 USC 1324b(a)(3), US entities)No personnel restrictions (except deemed exports)
GeographyUS-located data by default; 22 CFR 120.54 carves out properly-encrypted technical dataBIS-driven (15 CFR 734.6). Sanctions rules in 15 CFR 746 cover comprehensive embargoes (CU, IR, KP, SY), Russia/Belarus (746.8), Crimea/DNR/LNR (746.6), and shift; check current BIS country guidance
RegistrationDDTC registration required ($3,000/year)No registration (except encryption items)
LicensingLicense required for most exportsLicense required for high-level ECCNs, exceptions available

Control Comparison

Control AreaITAREAROverlap
Access ControlUS persons only verificationDenied party screening (Entity List, DPL, SDN)⚠️ Different mechanisms
Data ResidencyUS-located regions by default (encryption carve-out per 22 CFR 120.54)Driven by ECCN-specific licensing and current 15 CFR 746 sanctions⚠️ Different posture
EncryptionFIPS 140-2 Level 2+ requiredFIPS 140-2 for Category 5 Part 2✅ Same standard
Audit Logging5-year retention for records within 22 CFR 122.5 scope (not all logs)Varies by requirement⚠️ ITAR has scoped recordkeeping
Network IsolationDedicated VPCs for ITARNo specific requirement⚠️ ITAR only
MarkingITAR classification on all dataECCN classification on items⚠️ Different schemes
Third-Party AccessRestricted CSP accessNormal CSP access⚠️ ITAR more restrictive

Detailed Control Mapping

1. Personnel and Access

ITAR-1: US Person Verification

  • Requirement: Access limited to "US persons" per 22 CFR 120.62. That covers citizens, lawful permanent residents, "protected individuals" under 8 USC 1324b(a)(3), and US-incorporated entities. Don't collapse it to "citizens or LPRs only."
  • Cloud Impact: Verify US-person status per 120.62 category, tag IAM users with the resulting status
  • Verification: Personnel files documenting which 120.62 category applies, reviewed with HR and counsel

EAR-2: End-User Screening

  • Requirement: Screen against BIS denied parties lists
  • Cloud Impact: Automated screening on provisioning
  • Verification: Entity List, DPL, UVL, SDN checks

Overlap: ❌ No overlap - different mechanisms

  • ITAR focuses on citizenship
  • EAR focuses on entity screening

Compliance Strategy: Implement both

  • Citizenship verification for ITAR systems
  • Denied party screening for all systems (including ITAR)

2. Data Residency

ITAR-2: Data-Residency Posture

  • Default: ITAR technical data stored in US-located systems
  • Carve-out: 22 CFR 120.54 means properly-encrypted technical data isn't automatically released; deployment patterns vary if counsel blesses them
  • Common safe choice: us-gov-, us-east-, us-west-* in commercial regions (with controls), or GovCloud equivalents

EAR-4: Geographic Access Controls

  • Authority: BIS, not this toolkit (15 CFR 734.6)
  • Comprehensive embargoes: Cuba (CU), Iran (IR), North Korea (KP), Syria (SY) under 15 CFR 746
  • Other current rules: Russia and Belarus under 15 CFR 746.8; Crimea / so-called DNR / LNR regions of Ukraine under 746.6; sectoral and item-specific rules elsewhere in 746
  • Don't: treat the four-country list above as complete. The BIS country guidance is the live source.

Overlap: ✅ Partial overlap

  • US-located ITAR regions tend to satisfy comprehensive embargo blocking by default
  • EAR access controls for items not subject to 15 CFR 746 may permit non-US regions; ECCN-specific licensing applies

Compliance Strategy:

  • ITAR workloads: Default to GovCloud or US-located regions; counsel before relying on the encryption carve-out for non-US storage
  • EAR workloads: Region choice depends on your ECCN, applicable licensing under 15 CFR 740 (license exceptions), and current 15 CFR 746 sanctions. Geo-block per BIS country guidance, not the four-country shorthand.
  • Mixed: Segregate systems by framework

3. Encryption

ITAR-3: Encryption Requirements

  • Requirement: FIPS 140-2 validated encryption
  • Standard: Level 2+ HSMs (AWS KMS, Azure Key Vault, GCP Cloud KMS)
  • Keys: Customer-managed encryption keys (CMEK) recommended

EAR-3: Encryption Compliance

  • Requirement: FIPS 140-2/140-3 for Category 5 Part 2 items
  • Standard: Same as ITAR - Level 2+ HSMs
  • Classification: Encryption products require ECCN 5D002/5A002

Overlap: ✅ Complete overlap

  • Both require FIPS 140-2 validated encryption
  • Same HSM standards (Level 2+)

Compliance Strategy: Implement once, satisfies both

  • Use AWS KMS, Azure Key Vault HSM, or GCP Cloud KMS
  • Configure CMEK for all controlled data

4. Audit and Logging

ITAR-4: Access Logging and Audit

  • 22 CFR 122.5 scope: Specific record categories (manufacturing, export transactions, broker records) for ITAR-registered exporters retained 5 years
  • Not in 122.5: General CloudTrail/admin audit logs unless they carry 122.5-scope records
  • Engineering action: Identify which logs carry 122.5-scope records and retain those for 5 years; set general security/audit-log retention based on your own policy and other applicable frameworks (FedRAMP, SOC 2, etc.)

EAR: No specific logging requirement

  • Best Practice: Follow standard audit practices
  • Retention: As needed for compliance

Overlap: ⚠️ ITAR more stringent

  • EAR has no specific logging requirement
  • ITAR has 5-year retention under 22 CFR 122.5 for specific record categories (not every log)

Compliance Strategy:

  • ITAR: CloudTrail or equivalent. 5-year retention on records within 22 CFR 122.5 scope; shorter retention OK for non-122.5 logs unless another framework requires more
  • EAR: Standard operational logging; retention per your own policy and other applicable frameworks

5. Classification and Marking

ITAR-6: Export Control Marking

  • Requirement: Mark all ITAR data with export control notices
  • Tagging: "ITAR Controlled" on all resources
  • Notices: Export warnings on documents

EAR-1: Export Control Classification

  • Requirement: Classify with ECCN or EAR99
  • Tagging: ECCN codes (5D002, 3A001, etc.)
  • Documentation: Classification rationale

Overlap: ⚠️ Different classification schemes

  • ITAR uses "ITAR Controlled" binary marking
  • EAR uses granular ECCN codes

Compliance Strategy: Use both tags

AWS Tags:
  ExportControl: "ITAR"
  ECCN: "5D002"  (if also subject to EAR)

Cloud Platform Recommendations

Use CaseITAREARRecommended Platform
Defense contractor✅ Primary⚠️ MaybeAWS GovCloud, Azure Government
Encryption software❌ No✅ PrimaryAWS Commercial (US regions), FIPS KMS
Semiconductor manufacturer❌ No✅ PrimaryAWS/Azure/GCP Commercial with Entity List screening
Aerospace dual-use✅ Primary✅ SecondarySegregated: GovCloud for ITAR, Commercial for EAR
Cloud service provider⚠️ Support customers✅ As a toolOffer GovCloud + Commercial options

Licensing and Registration

RequirementITAREAR
RegistrationDDTC registration required ($3,000/year)No registration (except encryption)
License for ExportRequired for most USML itemsRequired for high-level ECCNs
License ExceptionsNone availableENC, TSU, BAG, TMP available
Self-ClassificationNot availableAvailable for encryption (ENC)
ReportingAnnual registration renewalSemi-annual (if using ENC exception)

Compliance Decision Matrix

ScenarioITAREARAction
Item on USML✅ Yes❌ NoUse /us-export:itar-assess
Item on CCL with ECCN❌ No✅ YesUse /us-export:ear-assess
Item on both lists✅ Yes⚠️ MaybeITAR takes precedence
Item on neither list (EAR99)❌ No✅ YesNo license for most destinations, but destination (15 CFR 746), end-user (Entity List / DPL / SDN), and end-use (15 CFR 744) rules still apply. Screen under the "knowledge" standard.
Uncertain jurisdiction❓ Unknown❓ UnknownSubmit Commodity Jurisdiction (CJ) request

Overlapping Controls (Implement Once)

These controls satisfy both ITAR and EAR:

✅ FIPS 140-2 Encryption

  • AWS KMS, Azure Key Vault HSM, GCP Cloud KMS
  • Satisfies ITAR-3 and EAR-3

✅ Denied Party Screening

  • While not ITAR-required, recommended for defense contractors
  • Satisfies EAR-2

✅ Access Logging

  • ITAR requires 5-year retention for record categories named in 22 CFR 122.5 (not every log)
  • EAR benefits from logging as operational and audit evidence
  • CloudTrail or equivalent satisfies both, with retention scoped per 122.5

Framework-Specific Controls

ITAR-Only Controls

These apply only to ITAR, not EAR:

🔒 US Person Verification (ITAR-1)

  • Not required for EAR
  • Critical for ITAR compliance

🔒 US-Located Data Residency by Default (ITAR-2)

  • ITAR defaults to US-located storage; 22 CFR 120.54 encryption carve-out is the documented exception
  • EAR residency depends on ECCN and current 15 CFR 746 sanctions, not a uniform "embargo countries only" rule

🔒 Network Isolation (ITAR-5)

  • Not required for EAR
  • Recommended for ITAR

EAR-Only Controls

These apply only to EAR, not ITAR:

📋 ECCN Classification (EAR-1)

  • Not applicable to ITAR (uses USML categories)
  • Required for EAR

📋 License Exceptions (EAR-7)

  • Not available for ITAR
  • ENC, TSU available for EAR

Cost Comparison

Cost ItemITAREARNotes
Registration Fee$3,000/year$0DDTC registration
Cloud Premium+30-50%StandardGovCloud premium pricing
Compliance Tools$50-200K/year$10-50K/yearScreening, monitoring
PersonnelUS persons onlyStandardMay limit talent pool
Audit/Assessment$100-300K$25-75KExternal audit costs

Migration Strategy

Moving from ITAR to EAR

If jurisdiction changes (e.g., product moved from USML to CCL):

  1. ✅ Keep: FIPS 140-2 encryption (helps EAR compliance)
  2. ✅ Keep: Access logging (best practice)
  3. ⚠️ Modify: Region scope shifts from US-located default to ECCN-driven; add geo-blocking aligned with current 15 CFR 746 sanctions, not the four-country shorthand
  4. ⚠️ Modify: Add ECCN classification
  5. ⚠️ Add: Denied party screening
  6. ❌ Remove: US person requirement (can allow foreign nationals)

Dual Compliance (Both ITAR and EAR)

For organizations subject to both:

  1. Segregate Systems:

    • ITAR workloads → GovCloud/Government regions
    • EAR workloads → Commercial regions
  2. Apply Most Restrictive Controls:

    • ITAR controls automatically satisfy overlapping EAR requirements
    • Add EAR-specific controls (ECCN, screening)
  3. Tag All Resources:

    ExportControl: "ITAR" | "EAR" | "BOTH"
    ECCN: "5D002" (for EAR items)
    Classification: "CUI" | "ITAR-Controlled"
    

Examples

# View overview comparison
/us-export:compliance-matrix overview

# Focus on control mappings
/us-export:compliance-matrix controls

# Cloud platform recommendations
/us-export:compliance-matrix cloud

# Licensing and registration comparison
/us-export:compliance-matrix licensing

Quick Reference

When ITAR applies: Default to strictest controls (US-person access, US-located regions). 22 CFR 120.54 encryption carve-out is available with counsel sign-off. When EAR applies: Apply ECCN-specific controls, denied-party screening, and current 15 CFR 746 sanctions. When both apply: Segregate systems or apply ITAR defaults + EAR additions. When uncertain: Submit a Commodity Jurisdiction request to DDTC and an ECCN classification to BIS via counsel.

Data Residency Verification

Engineering guidance only. Not legal advice. ITAR and EAR residency postures vary by USML category, ECCN, deployment model, encryption posture, and CSP attestations. The defaults below are starting points, not compliance positions. The country lists here can lag the live BIS sanctions text; verify against the BIS country guidance and 22 CFR 120.54 (the ITAR encrypted-technical-data carve-out) before acting.

Verifies data residency posture for ITAR (US-located by default) and EAR (BIS-driven sanctions and licensing).

Arguments

  • $1 - Framework (optional: itar, ear, both) - defaults to "both"
  • $2 - Cloud provider (optional: aws, azure, gcp, all) - defaults to "all"

ITAR Data Residency Requirements

Posture: US-Located Storage by Default

ITAR-controlled technical data is stored in US-located systems by default. 22 CFR 120.54 carves out properly-encrypted technical data from the release definition, so deployment patterns where end-to-end-encrypted data is stored or transmitted abroad can be defensible. This is not a free pass: the encryption has to actually be end-to-end, the keys have to be controlled by US persons, and counsel needs to bless the posture in writing for your specific USML category and CSP. When in doubt, default to US-located regions.

Recommended Cloud Regions

AWS GovCloud (Highly Recommended)

US Government Regions:

  • us-gov-west-1 (Oregon) - US West (GovCloud)
  • us-gov-east-1 (Virginia) - US East (GovCloud)

Benefits:

  • FedRAMP High authorized
  • US persons-only personnel
  • Physical isolation from AWS commercial
  • ITAR compliance support

Verification:

aws ec2 describe-regions --region us-gov-west-1
aws s3api list-buckets --region us-gov-west-1
AWS Commercial (US Regions Only)

Approved US Regions (with additional controls):

  • us-east-1 (Virginia)
  • us-east-2 (Ohio)
  • us-west-1 (California)
  • us-west-2 (Oregon)

Prohibited Regions:

  • Any non-US region (eu-west-1, ap-southeast-1, etc.)
  • Global services must be configured for US-only
Azure Government (Highly Recommended)

US Government Regions:

  • usgovvirginia - US Gov Virginia
  • usgoviowa - US Gov Iowa (DoD only)
  • usgovtexas - US Gov Texas
  • usgovarizona - US Gov Arizona
  • usdodeast - US DoD East
  • usdodcentral - US DoD Central

Benefits:

  • FedRAMP High authorized
  • Screened US personnel
  • Dedicated infrastructure

Verification:

az cloud list --query '[?name==`AzureUSGovernment`]'
az account list-locations --query '[?name==`usgovvirginia`]'
GCP with Assured Workloads

US Regions:

  • us-central1 (Iowa)
  • us-east1 (South Carolina)
  • us-east4 (Virginia)
  • us-west1 (Oregon)
  • us-west2 (Los Angeles)
  • us-west3 (Salt Lake City)
  • us-west4 (Las Vegas)

Assured Workloads Configuration:

  • ITAR compliance controls
  • Data residency enforcement
  • Personnel access controls

Verification:

gcloud compute regions list --filter='name:us-*'
gcloud assured list --location=us-central1

EAR Data Residency Posture

BIS-Driven, Not "Any Region Worldwide"

EAR doesn't impose a uniform "store data in US-only regions" rule, but it also isn't "any region worldwide minus four embargoed countries." 15 CFR 734.6 makes clear that BIS determines what licensing applies. The relevant access controls depend on:

  • Your item's ECCN (or EAR99 status), per the Commerce Control List
  • Whether a license exception applies under 15 CFR 740 (ENC, TSU, etc.)
  • Current sanctions under 15 CFR 746, which extend well beyond the four "comprehensive embargo" countries

Sanctions Snapshot (Verify Before Acting)

The list below is a snapshot, not a substitute for the current BIS country guidance. Sanctions move quickly. Before deploying access controls, check the BIS country guidance page and the most recent Federal Register entries.

Comprehensive embargoes (broad export restrictions, 15 CFR 746):

  • Cuba (CU)
  • Iran (IR)
  • North Korea (KP)
  • Syria (SY)

Region-specific comprehensive sanctions (15 CFR 746.6):

  • Crimea, so-called Donetsk People's Republic, and Luhansk People's Republic regions of Ukraine

Country-specific item-level controls (verify scope against current BIS text):

  • Russia (RU) and Belarus (BY): broad item-level restrictions under 15 CFR 746.8; not a partial regime
  • Venezuela (VE): specific restrictions under 15 CFR 746.10
  • Other countries: BIS publishes ongoing entity-list and country-specific actions; the BIS country guidance page is authoritative

Geographic Access Controls

AWS WAF Geo-Blocking
# Create WAF rule to block embargoed countries
aws wafv2 create-web-acl \
  --name EAR-Embargo-Block \
  --scope REGIONAL \
  --default-action Allow={} \
  --rules file://embargo-rule.json

# embargo-rule.json includes:
# GeoMatchStatement blocking: CU, IR, KP, SY
AWS CloudFront Geo-Restrictions
# Check CloudFront distribution restrictions
aws cloudfront get-distribution-config --id DISTRIBUTION_ID

# Configure geo-restriction
{
  "GeoRestriction": {
    "RestrictionType": "blacklist",
    "Quantity": 5,
    "Items": ["CU", "IR", "KP", "SY", "UA"]
  }
}
Azure Front Door Geo-Filtering
# Create Front Door with geo-filtering
az network front-door create \
  --name ear-compliance \
  --resource-group myResourceGroup

# Add geo-filtering rules to block embargoed countries
GCP Cloud Armor
# Create Cloud Armor security policy
gcloud compute security-policies create ear-embargo-block \
  --description "Block embargoed countries for EAR compliance"

# Add rule to block countries
gcloud compute security-policies rules create 1000 \
  --security-policy ear-embargo-block \
  --expression "origin.region_code == 'CU' || origin.region_code == 'IR' || origin.region_code == 'KP' || origin.region_code == 'SY'" \
  --action "deny-403"

Data Residency Verification Matrix

FrameworkRequirementAllowed RegionsBlocked Regions
ITARUS-located by default; 22 CFR 120.54 encryption carve-out availableus-gov-, us-east-, us-west-* by defaultNon-US regions unless encryption posture is documented and counsel-approved
EARBIS determines (15 CFR 734.6); ECCN-driven; sanctions per 15 CFR 746Depends on ECCN, license exceptions, and current sanctionsAt minimum: comprehensive embargoes (CU, IR, KP, SY), Crimea/DNR/LNR (746.6), Russia and Belarus item controls (746.8). Verify against current BIS country guidance.

Multi-Region Considerations

ITAR Multi-Region

Allowed: Multiple US regions for redundancy

Primary: us-gov-west-1
Backup: us-gov-east-1

Prohibited: Cross-border replication

us-east-1 → eu-west-1  ❌ PROHIBITED
us-gov-west-1 → us-gov-east-1  ✅ ALLOWED

EAR Multi-Region

Permitted regions depend on the ECCN, applicable license exceptions, and current 15 CFR 746 sanctions. Without those facts, "any region worldwide" is wrong. With those facts, common patterns:

Primary: us-east-1
DR: eu-west-1  ✅ Often OK for EAR99 / unrestricted ECCNs with denied-party screening; verify under your ECCN
DR: ap-southeast-1  ✅ Often OK for the same; check that no entity-list parties are in the access path

Always blocked (comprehensive embargoes plus region-specific sanctions):

Any region → Iran, Syria, Cuba, North Korea  ❌
Any region → Crimea / DNR / LNR regions of Ukraine  ❌
Item-controlled access → Russia, Belarus  ❌ for items under 15 CFR 746.8

Cloud Provider Support Matrix

ProviderITAR SupportEAR SupportFIPS 140-2Notes
AWS GovCloud✅ Highly Recommended✅ YesLevel 2+FedRAMP High, US persons
AWS Commercial⚠️ Limited (US regions)✅ YesLevel 2+Requires additional controls
Azure Government✅ Highly Recommended✅ YesLevel 2FedRAMP High
Azure Commercial⚠️ Limited (US regions)✅ YesLevel 2Requires additional controls
GCP Assured Workloads✅ Recommended✅ YesLevel 3With ITAR configuration
GCP Commercial⚠️ Limited (US regions)✅ YesLevel 3Requires configuration

Verification Commands

Check Current Data Locations

AWS:

# S3 bucket locations
aws s3api list-buckets | jq -r '.Buckets[].Name' | while read bucket; do
  location=$(aws s3api get-bucket-location --bucket "$bucket" --query 'LocationConstraint' --output text)
  echo "$bucket: $location"
done

# RDS instances
aws rds describe-db-instances --query 'DBInstances[*].{Name:DBInstanceIdentifier,AZ:AvailabilityZone}'

# EC2 instances
aws ec2 describe-instances --query 'Reservations[*].Instances[*].{Id:InstanceId,AZ:Placement.AvailabilityZone}'

Azure:

# Resource locations
az resource list --query '[].{Name:name,Location:location}' --output table

# Storage account locations
az storage account list --query '[].{Name:name,Location:location}' --output table

GCP:

# Bucket locations
gcloud storage buckets list --format='table(name,location)'

# Compute instances
gcloud compute instances list --format='table(name,zone)'

# Cloud SQL instances
gcloud sql instances list --format='table(name,region)'

Compliance Recommendations

For ITAR Workloads

  1. Use GovCloud/Government Regions

    • AWS GovCloud (us-gov-west-1, us-gov-east-1)
    • Azure Government (usgovvirginia, usgovtexas)
    • GCP Assured Workloads (with ITAR config)
  2. Disable Cross-Border Features

    • No global accelerators
    • No edge caching outside US
    • No replication to non-US regions
  3. Verify US-Only Personnel

    • CSP support staff are US persons
    • No foreign national access to infrastructure

For EAR Workloads

  1. Implement Geo-Blocking

    • AWS WAF, CloudFront restrictions
    • Azure Front Door filtering
    • GCP Cloud Armor policies
  2. Monitor Access Logs

    • CloudTrail, Azure Monitor, GCP Logging
    • Alert on access from embargoed countries
    • Block and report denied party access
  3. Screen Users by Geography

    • IP-based geolocation
    • Account provisioning screening
    • Continuous monitoring

Examples

# Verify ITAR data residency (US-only)
/us-export:data-residency itar aws

# Verify EAR embargo screening
/us-export:data-residency ear all

# Comprehensive verification for both frameworks
/us-export:data-residency both all

# Azure-specific ITAR verification
/us-export:data-residency itar azure

Common Violations

Common ITAR Risk Patterns (Validate Each With Counsel)

⚠ ITAR technical data in a non-US region without the 22 CFR 120.54 encryption carve-out documented

s3://my-bucket (eu-west-1) holding plaintext or single-key-managed-by-CSP technical data  ← high risk

⚠ Cross-border replication of plaintext technical data

us-east-1 → ap-southeast-1 with no end-to-end encryption layer  ← high risk

⚠ CDN with non-US edge caching ITAR technical data

CloudFront with European edge locations caching ITAR-bearing payloads  ← high risk

EAR Violations

❌ Allowing access from embargoed countries

User login from Iran (IR)  ← VIOLATION

❌ No geo-blocking configured

WAF rules allow all countries  ← VIOLATION

❌ Denied party not screened

Entity List company granted access  ← VIOLATION

EAR Assessment

Engineering guidance only. Not legal advice. BIS determines EAR applicability, ECCNs, and license requirements, not this toolkit. Under 15 CFR 734.6, BIS is the authority; the country-specific sanctions rules live in 15 CFR 746 and change regularly (e.g. Russia and Belarus under 746.8, Crimea/DNR/LNR under 746.6). Check the BIS country guidance for current sanctions text. Work with export-control counsel before relying on any posture below.

Deep dive assessment for Export Administration Regulations (EAR) compliance. Focuses on dual-use commercial items, encryption products, and technology under the Commerce Control List (CCL).

Arguments

  • $1 - Item type (optional: encryption, technology, commodities, software) - defaults to "general"

EAR Control Assessment

EAR-1: Export Control Classification (ECCN)

Requirement: Determine proper ECCN or EAR99 classification for all controlled items.

Assessment Questions:

  • Are all items classified with proper ECCN or EAR99?
  • Is classification documented and tagged on resources?
  • Is source code classified (ECCN 5D002 for encryption)?

Common ECCNs:

  • 5D002: Encryption software
  • 5A002: Encryption hardware/equipment
  • 5E002: Encryption technology (technical data)
  • 3A001: Electronic equipment
  • 4A003: Digital computers
  • EAR99: Items not on CCL (no license required for most exports, but destination, end-user, and end-use rules still apply — see 15 CFR 744, 746)

EAR-2: End-User and End-Use Screening

Requirement: Screen all customers and partners against BIS denied parties lists.

Screening Lists:

  • Entity List: Parties restricted for national security/foreign policy reasons
  • Denied Persons List (DPL): Individuals/entities with denied export privileges
  • Unverified List (UVL): End-use could not be verified
  • Treasury SDN: Specially Designated Nationals

Screening Frequency:

  • Before granting account access
  • Quarterly for existing customers
  • After any BIS list update

Assessment Questions:

  • Is screening performed for all new customers?
  • Is screening documentation maintained?
  • Are denied party matches reported and access blocked?

EAR-3: Encryption Compliance (FIPS 140)

Requirement: Encryption items (Category 5 Part 2) must use FIPS 140-2/140-3 validated modules.

Assessment Questions:

  • Are FIPS 140-2 Level 2+ HSMs used for encryption?
  • Is encryption self-classified or BIS-reviewed?
  • Is License Exception ENC applicable?

Self-Classification:

  • Submit encryption registration to BIS
  • Annual self-classification reports for updates
  • Maintain documentation of FIPS validation

EAR-4: Geographic Access Controls

Requirement: Block access from comprehensively embargoed countries.

Embargoed Countries (no exports without license):

  • Cuba (CU)
  • Iran (IR)
  • North Korea (KP)
  • Syria (SY)
  • Crimea region of Ukraine

Partially Sanctioned (check specific restrictions):

  • Russia (RU)
  • Belarus (BY)
  • Venezuela (VE)

Assessment Questions:

  • Is WAF/Cloud Armor configured to block embargoed countries?
  • Are geo-restrictions enabled on content delivery?
  • Are access attempts from embargoed countries logged and blocked?

EAR-5: Technology Transfer Controls

Requirement: Control export of technical data and source code.

Technical Data (EAR 734.2):

  • Information required for design, development, production, or use
  • Blueprints, plans, diagrams, models, formulae
  • Engineering designs and specifications
  • Manuals and instructions
  • Source code (depending on ECCN)

Assessment Questions:

  • Are code repositories access-controlled by geography?
  • Is technical data marked with ECCN classification?
  • Are deemed exports controlled (foreign nationals accessing data in US)?

EAR-6: Cloud Service Provider Attestations

Requirement: Verify CSP provides EAR-compliant features.

CSP Requirements:

  • FIPS 140-2 validated encryption
  • Customer-managed encryption keys (CMEK) available
  • Data residency controls
  • No CSP access to customer data without permission

Assessment Questions:

  • Is CMEK configured for all controlled data?
  • Does CSP provide FIPS 140 attestations?
  • Are data residency options available?

EAR-7: License Exception Applicability

Requirement: Determine if License Exception applies to avoid needing export license.

Common License Exceptions:

ENC (Encryption):

  • Certain encryption items ECCN 5A002, 5D002
  • Self-classification reporting required
  • Not available for embargoed countries

TSU (Technology and Software - Unrestricted):

  • Publicly available technology/software
  • Educational information
  • Published materials

BAG (Baggage):

  • Personal baggage exports
  • Tools of trade (laptops with encryption)

TMP (Temporary):

  • Temporary exports for testing, demonstrations

Assessment Questions:

  • Do any License Exceptions apply to your items?
  • Is self-classification completed for ENC?
  • Is TSU applicability documented for public software?

BIS Reporting Requirements

Encryption Registration (one-time):

  • Submit product information to BIS
  • Required for ECCN 5A002, 5D002, 5E002 items

Annual Self-Classification (if using ENC):

  • Report semi-annually to BIS
  • Document updates to encryption products

Classification Decision Tree

Is the item on the USML (US Munitions List)?
├─ YES → Use ITAR (not EAR)
└─ NO → Continue to EAR

Is the item on the CCL (Commerce Control List)?
├─ YES → Determine ECCN (e.g., 5D002 for encryption)
│   ├─ High-level ECCN → May require BIS license
│   └─ Check License Exceptions (ENC, TSU, etc.)
└─ NO → Likely EAR99 (no license for most exports)
    ├─ Destination rules still apply (15 CFR 746 embargoes + sanctions)
    ├─ End-user rules still apply (Entity List, DPL, SDN screening)
    └─ End-use rules still apply (15 CFR 744 — "knowledge" standard means
       a license can be required if you know or have reason to know the
       item is destined for a prohibited use, user, or destination)

Examples

# General EAR assessment
/us-export:ear-assess

# Encryption product assessment
/us-export:ear-assess encryption

# Technology/source code assessment
/us-export:ear-assess technology

# Software product assessment
/us-export:ear-assess software

Key Distinctions from ITAR

  • Personnel: No blanket US-person requirement (EAR) vs. US persons only (ITAR)
  • Geography: BIS-driven, ECCN-specific, sanctions per 15 CFR 746 (EAR) vs. US-located by default with 22 CFR 120.54 encryption carve-out (ITAR)
  • Authority: Commerce BIS (EAR) vs. State DDTC (ITAR)
  • License Exceptions: Available for EAR, not for ITAR
  • Scope: Dual-use commercial (EAR) vs. Defense articles (ITAR)

ITAR Assessment

Engineering guidance only. Not legal advice. DDTC determines ITAR applicability and jurisdiction, not this toolkit. Citations worth reading alongside this command: 22 CFR 120.54 (encrypted-technical-data carve-out), 22 CFR 122.5 (recordkeeping scope). Work with export-control counsel before adopting any of the postures below.

Deep dive assessment for International Traffic in Arms Regulations (ITAR) compliance. Focuses on defense articles, technical data, and defense services under the US Munitions List (USML).

Arguments

  • $1 - Assessment type (optional: readiness, remediation, certification) - defaults to "readiness"

ITAR Control Assessment

ITAR-1: US Person Verification

Requirement: Only "US persons" as defined in 22 CFR 120.62 may access ITAR-controlled technical data. That definition is broader than citizens and green-card holders. It also includes "protected individuals" under 8 USC 1324b(a)(3) (certain refugees, asylees, and specific visa holders) and US-incorporated entities / US governmental agencies for entity-level access. Access policies that narrow to "citizens or LPRs only" over-restrict and can trigger employment-law exposure. Use the full 120.62 definition.

Assessment Questions:

  • Are users with ITAR technical-data access US persons under the full 120.62 definition?
  • Is US-person status documented per the 120.62 category (citizen, LPR, protected individual, US entity)?
  • Is the verification process reviewed with HR and counsel so it doesn't over-narrow?
  • Are non-US-persons explicitly separated from ITAR systems (not granted access by default)?

Cloud Verification:

  • IAM users tagged with citizenship status
  • Access logs show US-person-only access
  • Foreign national access attempts are logged and blocked

ITAR-2: Data-Residency Posture (US-Located by Default)

Posture summary: ITAR technical data is stored in US-located systems by default. 22 CFR 120.54 carves out end-to-end-encrypted technical data from the release definition, so properly-encrypted-in-transit-and-at-rest deployment patterns have room that a strict "US regions only" rule doesn't capture. Default to US-located regions; raise the encryption-carve-out question with counsel before relying on it.

Assessment Questions:

  • Are production resources deployed in US-located regions by default?
  • If not, is the encryption posture documented and blessed by counsel?
  • Is cross-border data replication intentional and documented?
  • Are backups stored with the same posture as primary data?

Recommended Regions:

  • AWS: us-gov-west-1, us-gov-east-1 (GovCloud)
  • Azure: USGov Virginia, USGov Texas, USGov Arizona
  • GCP: us-central1, us-east4, us-west1 (with Assured Workloads)

ITAR-3: FIPS 140-2 Encryption

Requirement: All ITAR data must be encrypted with FIPS 140-2 validated cryptographic modules.

Assessment Questions:

  • Is all data encrypted at rest and in transit?
  • Are FIPS 140-2 Level 2+ validated HSMs used?
  • Are customer-managed encryption keys (CMEK) configured?

Verification:

  • EBS volumes encrypted with AWS KMS
  • S3 buckets use SSE-KMS encryption
  • TLS 1.2+ for data in transit

ITAR-4: Access Logging and Audit

Requirement summary: 22 CFR 122.5 requires ITAR-registered exporters to retain specific record categories (manufacturing, export transactions, broker records) for 5 years. It is not a blanket "retain every cloud log for 5 years" rule. Map which of your cloud logs actually carry those record categories, and set 5-year retention on those. General security/audit logs that fall outside 122.5 can have shorter retention set by your own policy or other applicable frameworks.

Assessment Questions:

  • Is CloudTrail or equivalent enabled for all regions?
  • Are data events logged for S3 and other services that may carry 122.5-scope records?
  • Which logs carry 122.5 record categories, and are those retained for 5 years?
  • Is log integrity protection enabled (log-file validation, separate account, MFA delete)?

ITAR-5: Network Isolation

Requirement: ITAR systems should be isolated from non-ITAR systems.

Assessment Questions:

  • Are dedicated VPCs/VNets used for ITAR workloads?
  • Is VPC peering to non-ITAR environments prohibited?
  • Are network boundaries clearly defined and enforced?

ITAR-6: Export Control Marking

Requirement: ITAR data must be marked with appropriate export control notices.

Assessment Questions:

  • Are all ITAR resources tagged with export control classification?
  • Are data files marked with ITAR warnings?
  • Is classification visible in metadata and labels?

ITAR-7: Third-Party Access Control

Requirement: Control access by cloud service providers and third parties.

Assessment Questions:

  • Are Service Control Policies (SCPs) configured to restrict third-party access?
  • Is Customer Lockbox/approval required for CSP support access?
  • Are external access roles audited and restricted?

DDTC Registration

Requirement: Most organizations handling ITAR data must register with DDTC.

Annual Fee: $3,000 per year Form: DS-2032 (Statement of Registration) Renewal: Annual before expiration

Recommended Cloud Platforms

PlatformRecommendationNotes
AWS GovCloudHighly RecommendedFedRAMP High, US-located, US persons only
Azure GovernmentHighly RecommendedFedRAMP High, screened personnel
GCP Assured WorkloadsRecommendedWith ITAR configuration, data residency controls
AWS CommercialLimited UseUS regions only, additional controls required

Examples

# Readiness assessment
/us-export:itar-assess readiness

# Remediation planning
/us-export:itar-assess remediation

# Pre-certification assessment
/us-export:itar-assess certification

Key Distinctions from EAR

  • Personnel: US persons only (ITAR) vs. No person restriction (EAR)
  • Geography: US-located data by default for ITAR, with the 22 CFR 120.54 encryption carve-out available; EAR geography is driven by ECCN-specific licensing and 15 CFR 746 sanctions
  • Authority: State Dept DDTC (ITAR) vs. Commerce BIS (EAR)
  • Scope: Defense articles (ITAR) vs. Dual-use commercial (EAR)

Export Control Jurisdiction

Engineering guidance only. Not legal advice. Jurisdiction determinations are made by DDTC and BIS (Commodity Jurisdiction and Classification Requests), not by this toolkit. Use the decision framework below as a starting point for internal triage; file a Commodity Jurisdiction (CJ) request or an ECCN classification through counsel before relying on any determination.

Helps determine whether ITAR, EAR, or both apply to your products, technology, and services.

Arguments

  • $1 - Product/technology description (required)
  • $2 - Industry (optional: defense, commercial, technology, aerospace)

Decision Framework

Primary Jurisdiction Question

Is the item on the US Munitions List (USML)?

  • YES → ITAR applies (State Department, DDTC)
  • NO → Continue to EAR analysis

USML Categories (ITAR)

The USML contains 21 categories of defense articles:

CategoryDescriptionExamples
IFirearmsRifles, pistols, machine guns
IIGuns and ArmamentArtillery, rockets, grenades
IIIAmmunitionMilitary ammunition
IVLaunch VehiclesMissiles, rockets, launch vehicles
VExplosivesPlastic explosives, detonators
VIVessels of WarNaval ships, submarines
VIITanks and Military VehiclesArmored vehicles, tanks
VIIIAircraftMilitary aircraft, drones
IXMilitary Training EquipmentSimulators, training devices
XProtective Personnel EquipmentBody armor, helmets
XIMilitary ElectronicsRadar, jamming equipment
XIIFire Control SystemsTargeting systems
XIIIMaterials and MiscellaneousSpecialized materials
XIVToxicological AgentsChemical agents
XVSpacecraftSatellites, space vehicles
XVINuclear Weapons(See separate regulations)
XVIIClassified ArticlesItems requiring security clearance
XVIIIDirected Energy WeaponsLasers, particle beams
XIXGas Turbine EnginesMilitary jet engines
XXSubmersible VesselsSubmarines
XXIMiscellaneousOther defense articles

Commerce Control List Categories (EAR)

If NOT on USML, check if on CCL:

CategoryDescriptionExamples
0NuclearNuclear materials, equipment
1MaterialsSpecial materials, composites
2Materials ProcessingMachine tools, equipment
3ElectronicsSemiconductors, computers
4ComputersProcessors, supercomputers
5TelecommunicationsEncryption, networking
6Sensors and LasersSensors, optical equipment
7Navigation and AvionicsGPS, inertial systems
8MarineMarine equipment
9Aerospace and PropulsionAircraft parts, engines

Jurisdiction Scenarios

Scenario 1: Defense Contractor

Product: Technical data for military aircraft avionics Analysis: Military aircraft → USML Category VIII → ITAR applies Posture (validate with counsel): DDTC registration, US-person access, US-located data by default (22 CFR 120.54 encryption carve-out available) Recommendation: Use AWS GovCloud or Azure Government

Scenario 2: Encryption Software Company

Product: Commercial encryption software Analysis: Encryption software → CCL Category 5 Part 2 → EAR applies ECCN: Likely 5D002 (encryption software) License Exception: ENC may apply Requirements: Self-classification, BIS reporting, embargo screening Recommendation: Commercial cloud with FIPS 140-2, geo-blocking

Scenario 3: Semiconductor Manufacturer

Product: Advanced microprocessors Analysis: Computer chips → CCL Category 3 or 4 → EAR applies ECCN: Varies by specifications (3A001, 4A003, etc.) Requirements: Entity List screening (China restrictions), classification Recommendation: Commercial cloud with denied party screening

Scenario 4: Aerospace Company

Product: Jet engine components for both military and commercial aircraft Analysis: Dual-use → Both ITAR and EAR may apply

  • Military use → ITAR (USML Category XIX)
  • Commercial use → EAR (CCL Category 9) Requirements: Separate systems for military vs commercial, jurisdiction by use Recommendation: Segregated environments (GovCloud for ITAR, commercial for EAR)

Scenario 5: Cloud Service Provider

Product: Infrastructure as a Service (IaaS) Analysis: Cloud services generally → EAR applies (as a tool) Customers may have ITAR/EAR obligations Requirements: Provide FIPS encryption, data residency controls, access logs Recommendation: Offer GovCloud/Government regions for ITAR customers

Gray Areas and Dual Jurisdiction

Dual-Use Technology:

  • May be on both USML and CCL
  • Rule: If on USML, ITAR takes precedence
  • Commodity Jurisdiction (CJ) request can clarify

Technical Data:

  • Drawings, blueprints, source code
  • ITAR if for defense articles
  • EAR if for commercial/dual-use

Deemed Exports:

  • Applies to both ITAR and EAR
  • Foreign nationals accessing controlled data in the US
  • ITAR: No foreign national access without authorization
  • EAR: Deemed export license may be required

Commodity Jurisdiction (CJ) Request

If uncertain, submit CJ request to State Department:

Process:

  1. Submit detailed product description to DDTC
  2. DDTC reviews against USML
  3. Decision: USML (ITAR) or CCL (EAR jurisdiction)
  4. Timeline: 60 days (can extend)

Cost: No fee Form: DS-4076 Commodity Jurisdiction Request

Decision Matrix

Product TypeLikely JurisdictionAuthorityKey Requirements
Military weaponsITARState DDTCUS persons, US regions, registration
Defense technical dataITARState DDTCUS persons, classification, marking
Encryption softwareEARCommerce BISFIPS 140, screening, ECCN 5D002
SemiconductorsEARCommerce BISEntity List, classification
Dual-use techITAR + EARBothSegregate by use case
Cloud services (tool)EARCommerce BISSupport customer compliance

Examples

# Determine jurisdiction for encryption software
/us-export:jurisdiction "Commercial encryption software with AES-256"

# Aerospace dual-use product
/us-export:jurisdiction "Jet engine components" aerospace

# Technical data for defense
/us-export:jurisdiction "Technical drawings for military radar system" defense

# Cloud infrastructure service
/us-export:jurisdiction "IaaS cloud platform" technology

Compliance Recommendation

If ITAR applies:

  • Use /us-export:itar-assess for detailed requirements
  • Consider GovCloud/Government cloud
  • Implement US person verification

If EAR applies:

  • Use /us-export:ear-assess for detailed requirements
  • Commercial cloud with FIPS 140-2 and geo-blocking
  • Implement denied party screening

If both apply:

  • Segregate systems by use case
  • Use /us-export:assess both for comprehensive evaluation
  • Consider separate environments (GovCloud + commercial)

Resources

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/us-export
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70