Skip to main content
Cryptography is one of the three domains Earnie governs, alongside open source and AI provenance. Earnie finds every place your code and its dependencies use cryptography, judges how weak each use is, and checks whether your application can actually run it. Cryptographic findings go through the same steps as every other finding. You review them in the same Review Workspace, the same policies judge them, they gate the same pull requests, and Earnie exports them in the same SBOM snapshots. A few places exist only for cryptography: the project’s Cryptography page, the Settings → Crypto Assessment page, the CBOM, and the export-control evidence report. This page gives an overview of each part and links to the page that covers it in full.
Cryptography is available where your organisation has it enabled. Without it, Earnie hides the cryptography scanner, pages, dashboard panels, policy fields, and export options this page describes.

What Earnie Finds

A cryptography scan records one finding for each use of a cryptographic asset. There are four kinds of asset: On a finding and in the Asset type filter, key material is shown as Related crypto material. Earnie looks in two places:
  • Your own code. Detection rules find calls to cryptography APIs and libraries, and record the exact lines.
  • Your dependencies. Earnie resolves the libraries your project depends on and finds the cryptography inside them. This catches a weak algorithm that a library uses on your behalf. Dependency resolution supports Go, Java, JavaScript and TypeScript projects with a package-lock.json, Python projects with a requirements.txt, pyproject.toml, setup.py, or setup.cfg, and Rust projects. Earnie installs JavaScript and Python dependencies itself, in the sandbox, without running package install scripts. Ruby, C, C++, and C# dependencies aren’t resolved, so only your own code is scanned for them. A Self-check doesn’t resolve dependencies.
Each finding records what Earnie could resolve about the asset, such as its primitive, mode, padding, and key size, and which library provides it. Detection runs inside your own Earnie deployment. See Deployment & data flow.

Running a Cryptography Scan

When your organisation has cryptography enabled, every scan runs it unless you turn it off. To skip it for one scan, clear Cryptography under Scanners on the New scan page. That section appears only when your organisation has more than one scanner. From the Earnie CLI, --scanners chooses the scanners: leave out crypto to skip cryptography, or pass --scanners crypto to run only cryptography. While it runs, the scan shows a Detecting cryptography stage, with steps for scanning your source, scanning dependencies, and building the call graph. See Cryptography steps.

How Earnie Judges It

Earnie gives every cryptographic finding three judgements:
  • Severity. How weak the cryptography is. Earnie looks this up in curated tables of algorithm families, key sizes, modes, protocol versions, and key material. MD5 is weak whatever you use it for, and RSA with a 1024-bit key is weaker than RSA with a 3072-bit key.
  • Post-quantum status. Whether a future quantum computer breaks it: Vulnerable, Safe, Not applicable, or Unassessed. Not applicable covers hashes and symmetric ciphers, which have nothing for a quantum computer to attack.
  • Export-control signals. Evidence for your own export-control self-classification. Earnie never states an export classification for you.
Earnie judges only what its tables cover, and no table covers certificates. An algorithm it hasn’t curated gets the post-quantum status Unassessed, and its severity is a placeholder, Medium, rather than a judgement. To find these findings, use the Risk assessed filter in the Review Workspace.

The Crypto Assessment Page

Earnie publishes its curated tables at Settings → Crypto Assessment, so you can check why a finding got its severity. The page is read-only, because the tables ship with Earnie. It has one table, with a row per family. Switch between Algorithms, Key material, and Protocols, search for a family, and use Show to narrow the rows to High severity, Quantum-vulnerable, or Export-controlled. Select a row to see its key-size and mode variants, its post-quantum reasoning, its export-control line, and the sources each value cites. Export ruleset downloads the whole ruleset as JSON. See Where the severity comes from for everything on the page.

Reachability

A weak algorithm your application never runs is less urgent than one on a code path that runs. Earnie traces calls through your code and its dependencies to tell them apart:
Not reached is not the same as not used. Reachability is static analysis. It can’t follow code that runs only through reflection or configuration. Treat a reachable finding as more urgent, but never treat an unreached one as harmless.
In Review, a cryptographic finding shows its proof under the source: the verdict and why, the route from the entry point to the cryptographic call as lanes, one per library it passes through, with the code of each hop, and where the call’s value comes from. Reachability also changes severity. Earnie raises a reachable finding one level above its curated severity, and the finding explains why. The curated tables stop at High, so only a reachable finding can be Critical. An unassessed finding is never raised. See Reachability for path strength, dependency chains, and reading the route.

Reviewing Cryptographic Findings

In the Review Workspace

In the Review Workspace, a cryptographic finding highlights the exact lines in the same source panel as any other finding. To see only cryptography, open + Filter and choose one of the preset views: Weak crypto, Quantum vulnerable, or Reachable crypto. You can also filter by the Cryptography evidence type, or by crypto-specific facts such as algorithm, algorithm family, reachability, post-quantum status, and key size. See Filtering. You can record one of three decisions on each finding: There’s no “Fixed” decision. You fix a weak algorithm by removing it, and the next scan reports it gone. See the cryptography decisions in Triaging findings.

On the Cryptography Page

Each project’s sidebar has a Cryptography page, with three tabs:
  • Overview shows an exposure funnel: the distinct assets, how many your code reaches from an entry point, how many of those are weak or quantum-vulnerable, and how many a policy blocks. It also shows where reached cryptography comes from (your code, a direct dependency, or a transitive dependency) and a Needs attention table of the reached assets a policy blocks, sends for approval, or warns about, with the route to each.
  • Libraries has one row per library that ships cryptography.
  • Assets lists every asset type, with presets for Post-quantum, Export control, and Certificates and keys.
Use it to answer questions such as “where do we use RSA?”, “what here isn’t quantum-safe?”, or “what does a policy block?”. Select an asset to open the Review Workspace filtered to it. See Cryptography.

On the Dashboard

The project Dashboard has a Cryptography tab with five panels: Reachable crypto, Reachability by severity, Reachability by scan, Post-quantum status, and Algorithm families. On the Overview tab, the Reachable crypto and Export evidence panels track how your cryptography and its export-control evidence change across scans. See The Cryptography tab.

What Changed Between Scans

A completed scan’s page has a Crypto changes card. It compares the scan with the nearest earlier scan that measured the project’s cryptography in full, and counts findings as New, Resolved, Re-detected, or Still open. Resolved means the finding is absent from this scan, and Re-detected means it disappeared in an earlier scan and came back. The card appears only when there’s an earlier scan to compare against. Without one, Earnie hides the card rather than showing zeros. See Crypto changes between scans.

Policies for Cryptography

The same policies govern cryptographic findings as every other finding. With cryptography enabled, the policy editor offers a Crypto field group and seven cryptography templates: Two regulatory template sets, PCI DSS 4.0 — 12.3.3 and CRA — Annex I(2)(e), select every cryptography template mapped to their clause in one action. See Rules about cryptography for what each template catches and every Crypto field. A cryptography policy gates pull requests, the pre-commit hook, and coding agents the same way as any other policy. See Merge gate.

Evidence: CBOM and Export Control

CBOM

A CBOM (cryptography bill of materials) lists your cryptographic assets in a standard format. In Earnie, it’s a CycloneDX 1.7 document generated from an SBOM snapshot. SPDX can’t carry cryptographic assets, so a CBOM is always CycloneDX. On a project’s SBOMs page, select New export and choose CBOM. To put open-source components and cryptographic assets in one document, choose SBOM, select Customize contents, and turn on Cryptographic assets; turning on AI models as well adds them. Each asset carries its cryptographic properties, where it occurs in your code, its reachability, and its export-control signals. From the command line, earnie export --include crypto writes the same document. See Exporting SBOMs.

The Export-Control Evidence Report

When a snapshot includes cryptographic assets and its scan ran cryptography detection, Earnie also produces an export-control evidence report. It’s one HTML file with the evidence you need to classify your own product under export-control rules. It lists the detected assets and their export-control signals, what Earnie scanned, and which ruleset it used. The report is evidence for your own self-classification. It isn’t legal advice, and it states no export classification. Download it from the ECR chip on the snapshot’s row on the SBOMs page, or as Export-control evidence report from the Dashboard’s Export menu. See The export-control evidence report.

What’s Next

  • Triaging findings explains how to work through cryptographic findings in the Review Workspace.
  • Setting policies explains how to turn your cryptography standards into rules.
  • Exporting SBOMs explains how to produce a CBOM for a customer or an auditor.