Independent technical practice

EAR and ITAR information gathering package

Gather products, technology, access and transaction facts for an EAR or ITAR export-control specialist. Keep classification decisions separate.

Bagged hard drive beside a forensic write blocker.

Global Digital Forensics · Information gathering library · October 18 2026

Edition GATHER-20261018-01 · Information-gathering edition

Read this guide freely. Request download access with your name and email.

GDF records the selected resource in its lead intake and private Stats.

Open your emailed link for seven days of preparation downloads in this browser.

No marketing subscription is created. Keep completed records in controlled systems.

Prepare business, item, technology, transaction and access facts for an export-control specialist to determine jurisdiction, classification and required authorizations.

Business owners, contract teams, engineering, IT, attorneys and export coordinators

EAR and ITAR preparation with cyber/data-handling questions. Sanctions, customs, nuclear exports, classified information and other regimes may require additional specialists.

Before you gather

  • EAR and ITAR are different export-control regimes. Neither is a general cybersecurity audit certificate. Start with the items, software, technical information, services and transactions. The specialist determines jurisdiction and classification, including whether another agency or regime applies.
  • A transaction can involve electronic access, remote support, source-code sharing, engineering collaboration or services as well as physical shipments. Gather who may access what, from where, with which permissions and authorization. Do not infer export eligibility from a US mailing address or citizenship label alone; route person-status questions to counsel through a restricted process.
  • DDTC registration, where required, does not itself grant export rights. A supplier label, an old ECCN, an ITAR clause or a cloud marketing statement is input for review, not the specialist determination. Keep the supporting classification, license, agreement, provisos and change history together.
  • EAR 734.18 and ITAR 120.54 contain different conditional provisions for certain encrypted transmission/storage. The current ITAR text reviewed has recent 2026 amendments. Ask the specialist to review the exact current text, encryption boundary, authorized recipients, key control, locations and provider access. Do not use a blanket statement that encryption or a domestic server resolves exports.
  • Recordkeeping periods have different starting events. EAR 762.6 uses five years from the latest specified event and restricts destruction after an agency request. ITAR 122.5 has its own license/approval/transaction rules and individual variation. Gather the actual dates and hold instructions; have the specialist set the schedule instead of using five years from file creation.

Give each request to the suggested owner. Record what is available and what is unknown in the editable CSV checklist. Use a secure evidence location agreed with the recipient; the checklist is an index, not a place for passwords, real patient data or controlled technical information.

Records to find

Download the editable gathering checklist. CSV files contain plain records, without saved column widths or workbook formatting. Import as UTF-8, keep IDs as text, wrap text and widen columns before use. Blank client fields are intentional.

EX-R01 Entity activities and responsible people

Ask
Business owner
Gather
Legal entities, sites/countries, products, manufacturing, software, research, services, brokering if relevant, customers and export responsibility contacts.
Where to ask
Corporate, engineering and sales records
Why it may be needed
Defines the proposed consultation and possible regimes.
If missing or uncertain
Describe the activity and ask for jurisdiction review; no guessed classification.

Reference: EA01; IT04

EA01 IT04

EX-R02 Item and technology descriptions

Ask
Engineering or product owner
Gather
Part/model/version list, function, performance specifications, materials, source/object code distinctions, drawings, manuals and technical data categories.
Where to ask
Engineering, PLM, repositories and product documentation
Why it may be needed
Provides the facts needed for a qualified jurisdiction/classification decision.
If missing or uncertain
Start with a sanitized description and arrange controlled specialist access before sharing technical data.

Reference: EA01; IT01

EA01 IT01

EX-R03 Existing jurisdiction and classifications

Ask
Export coordinator
Gather
ECCNs, USML categories, EAR99 determinations, commodity-jurisdiction/CCATS records if obtained, supplier classifications, rationale, dates and version history.
Where to ask
Export files, suppliers and counsel
Why it may be needed
Shows what was actually determined and which item/version it covers.
If missing or uncertain
Record Not yet determined. A supplier opinion may require confirmation and is not a government determination.

Reference: EA03; EA04; IT04

EA03 EA04 IT04

EX-R04 Transaction map

Ask
Sales and logistics
Gather
Proposed/prior transactions, destinations, parties, intermediaries, end users, end uses, routing, reexports/retransfers and ultimate consignees.
Where to ask
CRM, ERP, shipping and project records
Why it may be needed
Connects item facts to transaction-specific review.
If missing or uncertain
Unknown end use or destination is a question for the specialist before release.

Reference: EA05; EA04; IT04

EA05 EA04 IT04

EX-R05 Authorizations and restrictions

Ask
Export coordinator and counsel
Gather
Licenses, exceptions/exemptions basis, agreements, registrations where applicable, amendments, provisos, expiration dates and authorized parties/sites/data/services.
Where to ask
BIS/DDTC records and signed agreements
Why it may be needed
Allows specialist comparison of actual activity with authorized scope.
If missing or uncertain
Do not assume registration, a prior shipment or a different product license authorizes this activity.

Reference: IT03; IT05; EA04

IT03 IT05 EA04

EX-R06 Screening and escalation records

Ask
Compliance and sales
Gather
Screening procedure, dated results, party identifiers, red flags, end-use statements, escalation and release approvals, plus screening tool scope.
Where to ask
Screening provider, compliance and sales
Why it may be needed
Supports review of the actual decision at the time of transaction.
If missing or uncertain
Do not copy a static restricted-party list or conclude EAR99 always means no license required.

Reference: EA05; EA04

EA05 EA04

EX-R07 Technical information locations

Ask
Engineering and IT
Gather
Where technical information lives: design/source repositories, email, Teams/Slack, cloud drives, PLM, ticket systems, backups, removable devices and outside partners.
Where to ask
Data-source atlas, engineering and providers
Why it may be needed
Exposes copies and transfers beyond the product shipment.
If missing or uncertain
Treat candidate locations as unconfirmed until an owner responds.

Reference: EA01; IT01; IT02

EA01 IT01 IT02

EX-R08 Access and support facts

Ask
IT, HR and counsel
Gather
Actual access roles, contractor/provider organizations, work/support locations, foreign-person review process, access approvals and permitted remote administration.
Where to ask
Identity, HR, vendor and access records
Why it may be needed
Enables legal review of access/release risk without public disclosure of personal status.
If missing or uncertain
Do not place passports or immigration records in the general package. Counsel defines lawful, limited verification.

Reference: EA01; IT01; IT02

EA01 IT01 IT02

EX-R09 Cloud and cryptographic facts

Ask
IT architect and provider
Gather
Services/regions, replication, backups, disaster recovery, subcontractors, admin/support access, encryption boundary, module/strength details, key custody and decryption permissions.
Where to ask
Architecture, service contracts and provider security documents
Why it may be needed
Gives the specialist facts for the distinct EAR/ITAR encrypted-data provisions.
If missing or uncertain
If keys/provider access/regions are unknown, obtain written technical facts; do not represent the service as approved.

Reference: EA01 734.18; IT02

EA01 IT02

EX-R10 Technology access procedures

Ask
Export coordinator and IT
Gather
Existing technology control plans, permission reviews, visitor/collaboration rules, travel/device processes and exception records.
Where to ask
Export, facilities, IT and engineering
Why it may be needed
Supplies existing measures for specialist review; a template is not proof of implementation.
If missing or uncertain
Label a draft or proposed measure clearly; specialist determines what the activity requires.

Reference: EA03; EA04; IT04

EA03 EA04 IT04

EX-R11 Shipment and electronic release records

Ask
Logistics and system owners
Gather
Orders, invoices, shipment/export declarations where applicable, serial/item versions, authorizations referenced, transfer/access records and delivery acknowledgments.
Where to ask
ERP, freight forwarder, engineering and access logs
Why it may be needed
Links activity, authority and recipient over time.
If missing or uncertain
Identify records controlled by another party and arrange an authorized request rather than implying possession.

Reference: EA02; IT03

EA02 IT03

EX-R12 Retention and reproducibility

Ask
Records manager and IT
Gather
Schedules, license/transaction dates, record formats, change history, agency requests/holds, storage/access and ability to reproduce complete readable records.
Where to ask
Export archive, providers and legal holds
Why it may be needed
Enables separate EAR/ITAR schedule and reproduction review.
If missing or uncertain
Do not purge based on an assumed common five-year start date.

Reference: EA02 762.6; IT03 122.5

EA02 IT03

EX-R13 Training and business change

Ask
HR and export coordinator
Gather
Role-specific training, attendance, policies, changes to product/ownership/country/personnel/providers and prior advice about those changes.
Where to ask
HR, export program and project history
Why it may be needed
Helps the specialist assess whether old decisions still fit current facts.
If missing or uncertain
Record the change and date; do not assume an older determination transfers to a new version or end use.

Reference: EA03; IT04

EA03 IT04

EX-R14 Prior review and incident records

Ask
Counsel and export lead
Gather
Previous specialist reports, findings, corrective actions, suspected unauthorized access/shipments, regulator correspondence and disclosure records where authorized.
Where to ask
Restricted counsel/export files
Why it may be needed
Avoids repeating unresolved issues or making inconsistent representations.
If missing or uncertain
Potential violations should go to counsel/specialist promptly. This package neither determines reportability nor sends a disclosure.

Reference: EA04; IT04

EA04 IT04

EX-R15 Secure specialist access

Ask
Business sponsor and counsel
Gather
Identity/authorization of proposed recipients, secure repository, access restrictions, legal agreement and approved transfer method.
Where to ask
Engagement and information-security records
Why it may be needed
Sharing the preparation evidence can itself require export and privacy review.
If missing or uncertain
Supply a nonsensitive index until authority and secure delivery are agreed.

Reference: EA01; IT02; IT03

EA01 IT02 IT03

Questions for client IT and owners

Download the response template. A useful answer names the actual system, period, supporting record and limits. If you do not know, name the person or provider who can answer.

1. What precisely are you asking the specialist to review: hardware, software, technical data, services or a transaction?

Suggested responder
Client IT or system owner
Useful supporting record
Item/version list and a sanitized activity description.

2. Who made each existing classification and what version and facts did it cover?

Suggested responder
Client IT or system owner
Useful supporting record
Dated rationale and government/supplier correspondence, clearly distinguished.

3. Where can people outside the approved project view, download or administer the information?

Suggested responder
Client IT or system owner
Useful supporting record
Access map including support, backups, ticketing and collaboration.

4. Can any provider, administrator or subprocessor decrypt the information?

Suggested responder
Client IT or system owner
Useful supporting record
Architecture and key-custody statement; no secrets in the response.

5. Which countries, people and entities are involved in the planned activity?

Suggested responder
Client IT or system owner
Useful supporting record
Restricted transaction/person review file approved by counsel.

6. Which license, agreement, exception or exemption is proposed as the authorization?

Suggested responder
Client IT or system owner
Useful supporting record
Document, provisos, expiration, parties and specialist question.

7. What changed since the previous determination?

Suggested responder
Client IT or system owner
Useful supporting record
Change list covering technology, parties, destinations and services.

8. Are there agency requests, existing holds or uncertain prior transfers?

Suggested responder
Client IT or system owner
Useful supporting record
Counsel-controlled chronology and records index.

Missing facts and specialist decisions

These are explicit handoff questions. Marking records Received does not resolve them. Add client-specific questions and a responsible person.

EX-Q01 Which items/data/services are subject to EAR, ITAR, another regime or a documented exclusion?

Ask
Export-control specialist and counsel
Gather
Specifications, jurisdiction/classification history, technical descriptions and activities
Resolution needed
Written determination tied to the actual item/version; package completion cannot make it.

EX-Q02 Is the proposed storage/access/transfer authorized, including provider support and key access?

Ask
Export-control specialist with IT architect
Gather
Actual access paths, parties/locations, encryption facts and authorizations
Resolution needed
Transaction and system-specific instructions, including unresolved conditions before release.

EX-Q03 Which additional sanctions, nuclear, classified or contractual restrictions need separate review?

Ask
Counsel and appropriate specialist
Gather
Parties, countries, products/services and contract
Resolution needed
Explicit referral or documented exclusion; EAR/ITAR coverage is not assumed to cover every regime.

Download the open-question register

Preparing the handoff

  • Sanitized entity/activity and item/version descriptions are supplied first.
  • Classifications and authorizations are distinguished from proposed classifications and questions.
  • Access, cloud, technical-data and transaction maps identify unknowns and owners.
  • Specialist confirms authorization before receiving restricted technical information or advising release.

Download the record index. Use the shared walkthrough for custody, restricted records, missing information and receipt steps.

Sources for this package

Official laws/rules establish duties within their scope. Guidance explains programs; NIST supplies methods; vendor documentation describes possible product behavior. Actual contracts, facts, configuration and case orders still matter.

Privacy center

Choose your site settings

Optional technology stays off until you choose otherwise. You can change these browser settings at any time. Access to the core site does not depend on optional technologies.

Technology preferences
Sale or cross-context sharing: not used GDF does not sell or share website personal information for cross-context behavioral advertising.