Macher

[ 01 ]US small businessCryptographic inventory and post-quantum migrationTexas

Quantum-safeby 2030.

Cryptographic inventory, risk-based prioritization and migration engineering for federal agencies, contractors and healthcare.

OMB M-26-15

Oct 222026

Agency migration plans due to OMB

EO 14412

Dec 312030

Quantum-safe key exchange for high value systems

EO 14412

Dec 312031

Quantum-safe signatures for high value systems

What NIST proposes to retire

Source: NIST IR 8547, draft
Algorithm and useStatusReplacement
RSA-2048Certificates, signing, key transportDeprecated after 2030ML-DSA, ML-KEM
ECDSA P-256TLS certificates, tokensDisallowed after 2035ML-DSA (FIPS 204)
X25519, ECDHTLS key exchange, VPNsDisallowed after 2035ML-KEM (FIPS 203), hybrid first
AES-256Data at rest and in transitRemains approvedNo change

RSA at 112-bit strength is proposed for deprecation after 2030; quantum-vulnerable public-key algorithms for disallowance after 2035.

  • EO 14412
  • OMB M-26-15
  • FIPS 203
  • FIPS 204
  • FIPS 205
  • NIST IR 8547
  • NIST SP 800-53
  • NIST SP 800-171
  • CMMC
  • HIPAA Security Rule
  • CycloneDX CBOM

How an engagement runs

Find every algorithm.

Code, containers, network endpoints, cloud key stores and live Kubernetes traffic, merged into one CycloneDX cryptography bill of materials.

Rank what matters first.

Ranked by data lifetime, exposure and migration effort, with a justification you can defend to OMB, your contracting officer or your auditor.

Replace it, with evidence.

Hybrid key exchange, reissued certificates and dated milestones, with a reproducible run record behind every finding.

[ 02 ] Federal timeline

The clock is running.

Every date below comes from EO 14412 and OMB M-26-15. The next one is highlighted.

DateMilestoneStatus
EO 14412 signed
Agencies name a PQC migration lead
Agency migration plans due to OMB and ONCD
FAR proposed rule due on contractor FIPS and PQC compliance
CISA and NIST guidance on CBOM minimum elements due
PQC key establishment for HVAs and high impact systems
PQC digital signatures for HVAs and high impact systems

Dates are computed from the deadlines in EO 14412 (signed June 22, 2026) and OMB M-26-15 (June 24, 2026). Rulemaking dates are deadlines to publish proposed rules.

[ 03 ] Tooling

Our own tooling.

Built in-house and tested against planted cryptography before every release. No third-party platform to license.

How we run it safely

  • Live

    Code and dependency scanner

    Source code, configuration, key and certificate files, and dependency manifests, merged into a CycloneDX cryptography bill of materials.

  • Live

    Network and TLS probe

    Protocol versions, certificates, and a direct test for quantum-safe X25519MLKEM768 key exchange on every in-scope endpoint.

  • In development

    Kubernetes runtime observer

    eBPF sensors that record the handshakes your workloads actually negotiate.

  • In development

    Cloud key inventory

    Key specifications and certificates across AWS, Azure and Google Cloud key services.

  • In development

    Vendor readiness index

    Post-quantum support status for the products in your environment, with sources and dates.

  • Live

    Evidence reports

    Findings mapped to NIST, CMMC and HIPAA, with a reproducible run record behind each one.

[ 04 ] Coverage

What other assessments miss.

Most scanners stop at source code. Much of the real exposure sits in runtime traffic, infrastructure and machine identities.

E-01 Tested, not guessed

Which endpoints are already quantum-safe.

Most TLS tools cannot even offer the post-quantum hybrid group, so they cannot tell you whether a server supports it. We built our own handshake test for X25519MLKEM768 and run it on every endpoint in scope.

  • X25519MLKEM768
  • ML-KEM
  • TLS 1.3
  • Every endpoint
E-02Runtime, in development

What services actually negotiate

Code shows what could run. Our eBPF runtime observer will record every TLS handshake between workloads, including east-west traffic a perimeter scanner never sees.

E-08Service mesh

Workload identity certificates

mTLS certificates issued by Istio, Cilium and SPIFFE, which rarely appear in any inventory.

E-03Healthcare

Clinical interfaces and devices

HL7 and FHIR endpoints, DICOM links, certificate-signed EDI exchanges, and medical devices that stay in service for a decade or more.

E-04

Cluster configuration

Certificate issuers, ingress TLS, admission webhooks and stored secrets.

E-05

Cloud key services

RSA and elliptic-curve keys in managed key stores, and every issued certificate.

E-06

Machine identities

JWT and SAML signing keys, SSH host keys and code-signing certificates.

E-07

Legacy code

C, C++ and C#, where scanners are weakest. AI-assisted review on models inside the engagement environment, confirmed by an engineer.

[ 06 ] Start here

Three ways to start.

Published prices, written scopes and no hourly surprises. Pay by card, ACH, government purchase card or purchase order.

Exposure checkFree

One domain

Public TLS endpoints and certificates on a domain you control, with a two-page summary.

Request a check

Readiness Snapshot$5,000

One or two systems

A cryptography bill of materials and ranked findings in one to two weeks. Credited in full toward an inventory.

Order a Snapshot

Inventory and planFrom $14,500

Every system in scope

Full inventory and a migration plan covering all nine OMB M-26-15 elements.

Book a briefing

Full pricing and payment options

[ 07 ] Mission

Securing government systems for the quantum era.

We help US federal agencies, their contractors and healthcare organizations move to quantum-safe cryptography and close the security gaps around it.

The same transition is under way in governments around the world. As standards take hold internationally, we bring the same tooling and method to public-sector partners abroad.

[ 08 ] People

Engineers on every engagement.

The people who scope your engagement run the tools, review the code and sign the findings.

SY

Principal engineer

Member

Cloud, AI and security infrastructure engineer with about a decade across federal, healthcare and large-scale cloud environments. Specializes in Kubernetes, eBPF and zero-trust networking, the kernel-level visibility behind our runtime analysis. Sets the technical approach behind our tooling and findings.

  • Kubernetes
  • eBPF and Cilium
  • Zero trust
  • Cloud security
VM

Director of daily operations

Hands-on engineer

Hands-on engineer who runs day-to-day operations, from engagement scheduling to delivery. Seasoned across front end and back end, he builds the reporting, interfaces and monitoring platform that turn scan results into evidence clients can act on.

  • Operations
  • Front end
  • Back end
  • Reporting

Start with 30 minutes.

We review your systems, frameworks and deadlines. You leave with a fixed quote.

Book a briefing

Small business. NAICS 541512, 541519, 541690. SAM.gov registration in progress.