2027 Cryptography Migration Map
As products prepare for French certification, it scans live communications paths and produces a cryptography migration checklist prioritized by deadline and owner.
For engineering and compliance teams preparing to sell connected products in France, the hardest part of meeting the 2027 certification requirements is not knowing they need quantum-resistant cryptography. It is finding the real communications path that has not yet been migrated. Teams import a software bill of materials—the list of components used in the product—then connect domain names, cloud resources, code repositories, and owner information.
The product begins by scanning the actual handshake results of live internet-facing interfaces, identifying the certificate and key algorithms used by each service. When it finds an interface still relying on traditional public-key cryptography, it follows deployment data to the gateway, dependent packages, code repository, and responsible owner. Rather than merely flagging a domain, the map shows which feature the connection serves, when certification must be submitted, and which clients may be affected by a replacement.
Owners can prioritize migrations by certification date, exposure scope, and implementation difficulty, then generate assignable tickets. Each ticket includes scan evidence, the relevant components, and regression tests to validate. The first version inventories only external communications paths and product dependencies. It does not replace cryptographic review or claim that a product has received French certification.
Why now
ANSSI has made clear that, from 2027, at least some cryptographic products must integrate post-quantum cryptography when entering qualification. S1 Related coverage reached Hacker News on July 21 and, as of July 22, had 85 points, 41 comments, and ranked 18th, making it easier for teams nearing submission to begin tracing the live paths that have not yet migrated. S2
Target user
The primary user is a product security lead preparing to seek ANSSI qualification. Their project has entered the submission schedule, yet domains, gateways, and dependencies are still tracked in spreadsheets. Any omission can lead to retesting, delays, or cross-team rework. Engineering leaders also need to turn an abstract requirement into assignable work.
Minimal entry point
Start by accepting a domain list and a CycloneDX SBOM. Use established TLS scanners to collect certificates, public-key algorithms, and negotiated handshake results. A CBOM can represent algorithms, certificates, protocols, and component dependencies, making it suitable as the correlation layer. S4 Then use a GitHub App to read repositories, commit history, and CODEOWNERS. Initially, support tags and resource identifiers from one major cloud platform. Explainable rules link domains, gateways, components, and owners. The first version neither changes keys nor automatically determines certification outcomes. Its output should focus on evidence, gaps, owners, and retesting requirements.
Punching above its weight
Enter through French cybersecurity consultants and certification labs rather than broad paid acquisition. Offer a free self-hosted domain scanner that retains a branded path into the report. Publish French-language templates for cryptographic asset inventory before submission. Then partner with consultants preparing clients for ANSSI qualification and onboard customers project by project.
Competitors & gaps
- AQtive GuardGoogle
- AQtive Guard already covers code, runtime environments, and networks, inventorying keys, certificates, and algorithms. It also maps owners, dependencies, and impact scope, and supports migration orchestration and compliance reporting. S3 So discovering cryptographic assets is not a unique capability. The opening is a lightweight collaboration layer for French certification projects. The interface should be organized around product models, submission batches, and qualification dates. Each external connection must retain handshake evidence and link to its repository and owner. Ticket templates can align with French submission materials and regression testing. Its public product pages do not clearly present this French qualification workflow. Whether the wedge works depends on deploying faster than general-purpose platforms. It must also let mid-sized manufacturers deliver a reviewable migration list without buying a large cryptographic management platform.
How it makes money
Charge per product line included in the map, with continuous scanning, owner mapping, and evidence exports included. Base plans cap product lines and interfaces; collaboration seats can be purchased monthly during certification sprints.
The case against
The largest risk is that the applicable market is narrower than the title suggests. ANSSI’s text concerns qualification for certain cryptographic products, not all connected products sold in France. S1 If a customer’s product does not enter that regime, the deadline provides far less purchase motivation. A second risk is asset-correlation quality. Domains, gateways, and repositories often lack shared identifiers, so incorrect attribution could assign tickets to unrelated teams. Scanning can see externally negotiated results, but cannot prove every code path has been covered. Customers may also refuse to upload SBOM and infrastructure information. Self-hosting raises delivery and support costs. If consultants or evaluators cannot reuse the evidence, the product could become just another expensive asset spreadsheet.