Before you export, know what you are shipping.
Encryption controls depend on what each algorithm is used for and how long its keys are. Earnie reads your source code and dependencies, tags every cryptographic asset with its export-control signals, and gives your team the evidence it needs to self-classify.
Request a demoThe thresholds behind encryption controls
Bits of symmetric key length
Above this, cryptography for data confidentiality falls in Category 5, Part 2.
Bits for integer factorisation
The asymmetric equivalent, for algorithms such as RSA.
Bits for elliptic curves
The equivalent for discrete logarithms over an elliptic curve.
Annual self-classification report
Due to BIS each year for encryption items self-classified under License Exception ENC.
Source: BIS encryption controls guidance on key length and on the annual self-classification report.
From detected cryptography to classification evidence
Export classification depends on facts about each cryptographic asset. Earnie gathers them in five connected steps.
Find the cryptography in code and dependencies
Earnie scans your source and its dependencies, and records the primitive, mode, key size and the library that provides each asset.
Illustrative example
Separate confidentiality from everything else
Encryption controls focus on cryptography for data confidentiality. Earnie records each finding’s purpose, so signatures, hashes and MACs stay out of the key-length test.
Confidentiality
Authentication
Hash and MAC
Not established
Illustrative example
Read each asset against the threshold
For confidentiality assets, Earnie compares the resolved key length with the cited threshold. A size it couldn’t resolve is recorded as unknown, never as small.
Illustrative example
Flag new export exposure before it merges
Two cryptography templates watch export evidence in developer self-checks and pull request scans. Both start as Warn.
Signatures, hashes and MACs never raise these, because they fall outside the threshold by design.
Export the evidence for your classification
A crypto export freezes a CBOM together with an export-control evidence report. The report cites what was scanned and which ruleset Earnie used, and states no ECCN.
export-control properties per assetself-contained HTMLchecksums and citationsTry the key-length test on common algorithms
Pick an algorithm and what it’s used for.
Illustrative. Thresholds from BIS guidance on key length. This shows how the test reads, not a classification and not Earnie output. Earnie records the result for each detected asset as signals: met, not met, unknown or not evaluated.
Where encryption export rules come from
Wassenaar Arrangement
The multilateral list of dual-use goods and technologies that the US and EU encryption categories are drawn from.
Basis of Category 5, Part 2US Export Administration Regulations
Encryption items sit in Category 5, Part 2. License Exception ENC is in 15 CFR 740.17, and the self-classification report in Supplement No. 8 to Part 742.
Cited by Earnie’s export packageEU Dual-Use Regulation
Controls dual-use exports from the EU, with information security in Category 5, Part 2 of Annex I.
Regulation (EU) 2021/821Regulations map
Software supply chain rules by jurisdiction, with the evidence Earnie produces for each.
Open the mapAn evidence layer for your export compliance team
Detect
Inventory cryptography in source code and dependencies.
Signal
Record purpose, key length and export-control signals on each asset.
Govern
Warn on export-relevant cryptography before it merges.
Evidence
Freeze a CBOM and an export-control evidence report for each release.
Classification and authorisation are the exporter’s legal conclusion. Earnie states no ECCN and files nothing with BIS. It gives your export compliance team and counsel the inventory and the evidence to reach that conclusion.
Questions about export control and Earnie
Does Earnie classify our product or assign an ECCN?
No. Earnie gives you evidence for your own self-classification. The export-control evidence report states no classification and doesn’t imply one, and it isn’t legal advice. The classification and any authorisation are the exporter’s legal conclusion.
What are export-control signals?
Each cryptographic finding records its purpose and three export-control signals. Each signal is met, not met, unknown or not evaluated. They are evidence only, and policies can read them.
What is in the export-control evidence report?
The detected cryptographic assets, their export-control signals, the detection surface, meaning what was scanned, and the identity of the ruleset Earnie used. The header names the export dataset and when it was last reviewed, and tells you to check the evidence against the current 15 CFR 740.17 and Category 5, Part 2 before relying on it.
Does the report prove all our cryptography is standard?
No. Signature-based detection can’t prove that no non-standard cryptography is present, so the report marks that statement as not established from the frozen evidence.
Which export rules does Earnie’s package cite?
The Export control (US EAR) package cites 15 CFR 740.17, License Exception ENC, and the self-classification report in Supplement No. 8 to Part 742. It contains a CycloneDX CBOM and the export-control evidence report. It classifies nothing and files nothing.
Can policies catch export-relevant cryptography before it merges?
Yes. Warn on confidentiality crypto over export threshold and Warn on unresolved export evidence run in developer self-checks and pull request scans, like any other policy. Both start as Warn.
Does my code leave my environment?
No. Cryptography detection runs inside your own Earnie deployment. On SaaS, only fingerprints, one-way hashes of your code, go to the knowledge base we host. On-prem, nothing leaves your network.
Classify from evidence, not from memory.
See Earnie inventory the cryptography in code like yours.
Request a demo