Evidence first. These answers only repeat what our product pages, trust center and published evidence state. If your question is not here, ask us and we reply within one business day.
No question matches that search. Try another word, or ask us directly.
Post-quantum risk
Is “harvest now, decrypt later” a real threat?
Yes. Recording encrypted traffic or stored data needs no quantum computer: an adversary can capture it today and decrypt it once a cryptographically relevant quantum computer exists. If the data must still be confidential at that point, it is already exposed. The risk is highest for data with a long confidentiality lifetime, such as health records, financial data or long-term contracts, protected by quantum-vulnerable key exchange (RSA, ECDH, Diffie-Hellman).
When will a quantum computer break RSA and elliptic-curve cryptography?
Nobody knows, so the arrival year has to be treated as a planning assumption. CRYPTAGION uses a configurable planning scenario of 2032 by default, with 2030 and 2038 as reference values to test how sensitive your plan is. That is a planning assumption, not a prediction.
More: HNDL exposure calculator
Why act in 2026 if the threat is years away?
Because the first EU milestone is the end of 2026, and the time a migration takes counts against you too. The EU coordinated post-quantum roadmap expects first steps by the end of 2026 (including cryptographic inventories, dependency mapping and quantum risk analysis), high-risk use cases moved to post-quantum cryptography by the end of 2030, and medium-risk ones by 2035. The roadmap is addressed to Member States and creates no new legal obligation on its own, but it sets the date against which existing NIS2 and DORA obligations will be read.
Does the quantum threat affect signatures as well as encryption?
Yes, on a different timeline. RSA, ECDSA and Ed25519 signatures are sound today but breakable by Shor’s algorithm, so they need migrating, for example to ML-DSA (FIPS 204) or SLH-DSA (FIPS 205). Signatures cannot be harvested the way encrypted traffic can: forging one needs a quantum computer at the moment of the attack. Publicly trusted post-quantum TLS certificates do not exist yet, so an RSA or ECDSA certificate today is expected, not a misconfiguration.
More: HNDL calculator: assumptions and limits · TLS quantum checker
Is AES at risk?
Not in the same way. Grover’s algorithm gives at most a quadratic speed-up, so AES-256 is generally considered to remain secure, and some guidance asks for 256-bit keys for long-term protection. CRYPTAGION classes AES-256, SHA-256 and above, SHA-3 and HMAC as “retain and monitor”: keep them, track them in the inventory and re-check as guidance evolves.
More: Glossary: AES
What replaces RSA and elliptic-curve cryptography?
NIST published three final standards on 13 August 2024: ML-KEM (FIPS 203) for key establishment, and ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) for signatures. EU agencies such as ANSSI and BSI recommend deploying them in hybrid mode, combined with a classical algorithm, during the transition. CRYPTAGION maps each quantum-vulnerable finding to its recommended replacement.
More: PQC standards tracker
What CRYPTAGION finds
What does CRYPTAGION scan?
Three surfaces, combined in one inventory: source code in Python, JavaScript/TypeScript, Java, Go and C/C++; X.509 certificates in PEM, DER, CRT and CER, with issuer, validity and signature algorithm; and live TLS endpoints, with negotiated protocols and cipher suites. Every finding keeps its provenance: file and line, certificate or endpoint.
More: Cryptographic inventory
Is every detection a vulnerability?
No. Imports, algorithm lookup tables, test vectors and capability checks all count as detections, and they mean different things. Each finding is tagged by scope (production, test, example or vendor), so test fixtures and vendored libraries are not confused with production cryptography and can be kept out of a CI gate. In our published pyca/cryptography scan, 1,746 of the 1,804 detections were in tests and 46 in library source.
Will it find every use of cryptography in our code?
We do not claim that. Coverage depends on the language and the code style, and values passed from one method to another can still be missed. In our published comparison on Keycloak, CBOMkit found production lines our first run missed; we fixed the Java rules and published the re-run, including the 4 lines it still misses. Run any tool on code like yours before you choose.
More: CBOMkit vs CRYPTAGION
How is risk scored, and can we tune it?
Each asset gets a 0–100 score, traced to its exact line and explained factor by factor: algorithm, key size, data lifetime and harvest-now-decrypt-later exposure, anchored to NIST IR 8413, BSI TR-02102-1 and CNSA 2.0. You tune it with a .cryptagion.yaml policy that gives each path its own data classification and confidentiality lifetime, so long-lived secrets score higher than public traffic. The quantum planning year is configurable too.
Do we have to replace all our cryptography?
No. CRYPTAGION separates three cases. Remediate now: MD5, SHA-1, RSA-1024 and expired certificates, which are already broken or out of policy. Migrate to post-quantum: RSA, ECDSA, ECDH, DH and Ed25519, sound today but breakable by Shor’s algorithm. Retain and monitor: AES-256, SHA-256 and above, SHA-3 and HMAC.
What is a CBOM, and why CycloneDX 1.6?
A cryptographic bill of materials (CBOM) is a machine-readable inventory of the cryptographic assets in your systems, with where each one was found. CRYPTAGION exports it as CycloneDX 1.6, validated against the official schema: an open standard your GRC tooling can ingest, which stays usable if you stop working with us. Risk scores and recommendations go into separate outputs, so the CBOM remains a vendor-neutral record of what was found.
More: CBOM generator
What do we actually receive?
A CycloneDX 1.6 CBOM; an executive PDF mapped to DORA, NIS2, the EU CRA and FIPS 203/204/205, with a posture score and a 30/90/180-day plan; a 4-wave migration roadmap with effort estimates; and SARIF for engineering teams. All are open formats that remain usable without our platform.
More: How it works
How is this different from open-source CBOM tools?
Open-source CBOM tools generate a cryptographic inventory; they are free, capable and the right call if you have the in-house expertise and time to assemble and maintain them. CRYPTAGION uses the same open standard and adds the decision layer: per-asset quantum-risk scoring, HNDL exposure, a board report, a wave-based migration roadmap and regulatory mapping, with a named practitioner accountable for the result. We also published a head-to-head with CBOMkit on two real repositories, including where CBOMkit found more than we did.
More: Compare tools · CBOMkit vs CRYPTAGION
Can we see real output before a call?
Yes. We published a pinned scan of pyca/cryptography: 243 Python files, 1,804 detections, a CycloneDX 1.6 CBOM validated against the official schema, the validation results and the evidence bundle. The scan explorer lets you filter every detection and open it at its exact source line on GitHub. The case study also states its limits, for example that the 109 Rust files were not scanned.
More: Python CBOM case study · Scan explorer
Deployment, security and intrusiveness
Does our source code leave our environment?
No. Discovery runs inside your perimeter; only aggregated findings are produced. Air-gapped runs are supported. Static analysis, certificate parsing, TLS handshakes, risk scoring, CBOM and report generation all run locally.
More: Deployment and data flow
Can it run air-gapped?
Yes. Fully offline runs are supported, and the executive narrative falls back to a deterministic offline mode with no external call. Partners working in air-gapped customer environments get an offline install bundle.
More: Deployment and data flow · Partners
Does a scan affect our production systems?
Code and certificate analysis is static: files are read and parsed, and the scanned code is not executed. TLS discovery opens handshakes with the endpoints you put in scope, as a connecting client would. There is no agent to install across your fleet: you point the CLI at a repository, a certificate directory or a TLS target.
More: Deployment and data flow
What access does CRYPTAGION need?
When you run it yourself, it only needs to reach what you point it at: a repository, a certificate directory or a TLS target, on your own servers, in your CI/CD or offline. In a discovery engagement where we run the scan for you, you choose how code reaches us: a read-only deploy key on a mirror you control, a one-time expiring transfer, or a live screen-share scan where you watch every command.
More: Trust center
Where does our data go during a discovery engagement?
To a dedicated virtual machine on a dedicated server we lease from OVHcloud in Gravelines, France. VMs are never shared between customers, and no customer data is transferred to or processed outside the European Economic Area. Deliverables are pushed to a destination you control, with SHA-256 checksums. Within 7 days of closure the VM is destroyed and you receive a signed data destruction certificate.
More: Trust center
Is AI or an LLM used on our data?
Not by default. The executive narrative is policy-generated and runs in a deterministic offline mode with no external call. Optional LLM assistance for that narrative uses an EU-sovereign backend that you choose and can swap; it is the only optional external call, and your source code is never uploaded.
More: Deployment and data flow
Can it run in our CI/CD pipeline?
Yes. Discovery executes in the pipeline, so source code never leaves the runner. It produces a CycloneDX 1.6 CBOM on every change, can fail the build when new broken or quantum-vulnerable cryptography breaches your policy, and writes SARIF for code-scanning tools. Start in report-only mode, baseline your estate, then tighten the policy wave by wave.
More: CI/CD gate
What do you sign, and what happens if there is an incident?
A mutual NDA, a statement of work and a GDPR Article 28 data processing agreement, all signed before any technical work; deliverables are your property. If an incident is reasonably suspected to involve your data, we notify your DPO or named security contact within 48 hours, take part in your incident response, and make no public statement about it without your written approval.
More: Trust center
How do we report a vulnerability in CRYPTAGION?
Write to security@cryptagion.io with a description, its impact, steps to reproduce and the affected component. We acknowledge reports within 5 business days, practise coordinated disclosure and offer safe harbour for good-faith research. The machine-readable policy is at /.well-known/security.txt.
Pricing and engagements
How much does CRYPTAGION cost?
Pricing is public. The PQC Readiness Pilot is €18,000. Discovery is a €45,000 fixed fee over 60 days. The Platform starts from €80,000 per year. Migration advisory is scoped to your estate and billed separately.
More: Pricing
What is the pilot, and who qualifies?
A fixed-scope engagement to baseline one critical domain: 3–5 repositories and up to 20 TLS endpoints, producing a sample CycloneDX CBOM, a quantum-risk summary and an executive overview. It is offered at a reference-programme rate of €18,000, in exchange for a public reference and a 30-minute case-study interview, and is open to the first 5 reference customers only. It is the natural first step before a full Discovery.
More: Pricing
What does Discovery include?
A €45,000 fixed fee over 60 days, covering up to 50 repositories, 100 TLS endpoints and your certificate stores, on-prem or air-gapped, with one results workshop. You receive full discovery across code, certificates and TLS, a CycloneDX 1.6 CBOM, a board-ready PDF executive report, a 4-wave migration roadmap and regulatory mapping to DORA, NIS2 and the CRA.
More: Post-quantum discovery · Pricing
What happens after Discovery?
There are two optional next steps. The Platform, from €80,000 per year, keeps the inventory current: continuous scans of unlimited repositories, CI/CD and API integration, quarterly CBOM refresh, diff alerting on new cryptography and an audit trail. Migration advisory, quoted separately, supports the migration itself and is delivered directly or through your security integrator.
More: Pricing
Can we work through our integrator or consultancy?
Yes. Integrators and consultancies can take a partner licence to use CRYPTAGION across their customer engagements, inside each customer’s environment, and KOR IT can co-deliver an assessment or the migration advisory with them. Partner terms depend on volume and delivery model and are quoted on request; OEM and redistribution need a separate agreement.
More: Partner programme
Is there a free trial?
Our public pricing does not include a free trial. The free starting points are a 30-minute live demo on a public repository, and three browser tools: a 2-minute readiness assessment, a harvest-now-decrypt-later calculator and a TLS quantum checker for a public domain.
More: Request a demo · Readiness assessment
Do you need access to our code for a demo?
No. The demo only uses public code: we run discovery live on a public repository, such as one of your open-source projects or a library your stack depends on, and we never ask for access to your repositories. You keep a CycloneDX CBOM preview and the top quantum-vulnerable findings.
More: Request a demo
What happens to our deliverables if we stop using CRYPTAGION?
All outputs are open standards (CycloneDX CBOM, PDF) and remain fully usable without the platform. Source-code escrow is available on Platform engagements, with a documented right-to-audit and a reversibility clause.
More: Why a focused practice
Compliance
Does using CRYPTAGION make us DORA, NIS2 or CRA compliant?
No tool does that on its own. CRYPTAGION supports evidence for cryptographic risk-management, resilience and governance activities relevant to frameworks such as NIS2, DORA and the Cyber Resilience Act. Use of the product does not by itself establish regulatory compliance.
More: Homepage FAQ
What standards does the CBOM comply with?
CycloneDX 1.6 Crypto-BOM, validated against the strict schema, with reporting mapped to DORA, NIS2, the EU CRA and FIPS 203/204/205. Each quantum-vulnerable finding is mapped to its replacement among ML-KEM, ML-DSA and SLH-DSA.
More: CBOM generator
What do DORA and NIS2 actually say about cryptography?
NIS2 Article 21(2)(h) requires policies and procedures regarding the use of cryptography and, where appropriate, encryption. Under DORA, the risk-management RTS (Delegated Regulation (EU) 2024/1774) requires a documented encryption and cryptographic controls policy that provides for updating cryptographic technology as cryptanalysis develops, together with key management and a register of certificates. Without knowing where your cryptography lives, those expectations are hard to evidence.
Can the output be used as audit evidence?
Yes, as supporting evidence. Every finding carries its provenance (file, line or endpoint), the CBOM is schema-validated CycloneDX 1.6, an artefact auditors increasingly expect, and the Platform keeps an audit trail to support regulatory evidence. Use of the product does not by itself establish compliance.
More: Cryptographic inventory
Company
Who is behind CRYPTAGION?
KOR IT, a French SAS based in Bordeaux, incorporated in 2021 and registered with the Bordeaux RCS under number 905 247 706. CRYPTAGION is built by a focused security-engineering practice, and the people who scope your engagement are the people who run the tool against your code.
More: Legal notice
Is CRYPTAGION built in the EU?
Yes. It is built in Bordeaux, France, by KOR IT, for regulated EU organisations. When we run a discovery engagement for you, the scan runs in France, and no customer data is transferred to or processed outside the European Economic Area. When you run the product yourself, we process none of your data.
More: Trust center
How do we get security documents for procurement?
The security posture document is public: download it (PDF). For DPA, NDA or statement-of-work templates, answers to your security questionnaire or a call with the engagement lead, use the request form in the trust center; we reply within one business day.
More: Request documents
Are you hiring?
There are no formal openings right now, but we read every open application. We most want to hear from cryptography experts and B2B cybersecurity marketing specialists, working hybrid from France. Email contact@cryptagion.io with the subject “Open application”.
More: Careers
Still have a question?
See CRYPTAGION scan a public repository that matches your stack in a free 30-minute demo, or get a first score in 2 minutes.
Book a demo → Take the readiness assessment