🔐 NIST FIPS 203 · 204 · 205 Finalized — August 2024

Your encryption has an expiry date.
Do you know where it lives?

RSA, ECDSA, and Diffie-Hellman — the algorithms protecting your data today — will be deprecated by 2030. Enterprises need 2–3 years to migrate. NIST finalized post-quantum cryptography standards in August 2024. The window to act is now.

Scan My Domain — Free 🧮 Calculate My Debt
StandardsNIST FIPS 203/204/205 Aligned
ProductionML-DSA-65 in AuthentiScan
DeliverableEnd-to-End Migration Roadmap
The Threat

Harvest Now, Decrypt Later is not a future threat.

Nation-state actors are recording your encrypted traffic today — to decrypt it when quantum computers arrive. Any data you transmit now that must stay confidential for 5+ years is already at risk.

This is not speculation. The US government, Cloudflare, and Google are already running post-quantum encryption in production. The question is not if you need to migrate — it is whether you will have enough time.

"The companies that start their cryptographic inventory in 2026 will migrate in time. The ones that wait for the mandate will scramble — and pay 10× more."
Migration Window — Act Now
2024
NIST finalizes FIPS 203, 204, 205Post-quantum standards locked. The clock starts.
2026
Buying window opens TODAYEnterprises begin cryptographic inventory.
2027
US federal mandates cascadeSupply chain compliance requirements reach vendors.
2028
NIST IR 8547 hard deadlinesMigration must be underway for critical systems.
2030
RSA/ECDSA/DH deprecatedMigration must be complete. No exceptions.
2035
Full post-quantum enforcementClassical algorithms phased out globally.
What We Do

Crypto Inventory & PQC Migration

From discovery to roadmap — we scan your entire cryptographic surface and tell you exactly what to replace, what to keep, and in what order.

01
🔍
Discovery
We scan your repositories, infrastructure, and public endpoints for every instance of RSA, ECDSA, Diffie-Hellman, and legacy TLS in use. Most organisations discover 3× more crypto than they expected.
02
⚡
Risk Mapping
Every finding is scored against quantum threat level, data retention requirements, and NIST IR 8547 timelines. You see exactly what is CRITICAL, HIGH, MEDIUM, or SAFE — and why.
03
🗺️
Migration Roadmap
A prioritised remediation plan: which algorithm to replace with what, estimated migration effort, and deadline by asset. Your engineering team knows exactly what to do next.
What We Scan

Your Complete Cryptographic Attack Surface

💻
Source Code Repositories
What we find
RSA, ECDSA, DH usage in application code
How
AST and pattern scanning across GitHub/GitLab
📦
Package Dependencies
What we find
Vulnerable crypto libraries — openssl, jose, pyca/cryptography
How
package.json, requirements.txt, pom.xml, go.mod
🔒
TLS Certificates
What we find
Key type, cipher suite, protocol version, expiry
How
Domain scanning, certificate transparency logs
🔑
SSH Keys
What we find
RSA-2048 vs Ed25519 across infrastructure
How
Infrastructure config scanning
🌐
API Endpoints
What we find
Cipher suites negotiated in production
How
TLS handshake inspection
Sample Output

What Your Report Looks Like

Clear, prioritised, actionable — not a wall of jargon.

PQC Readiness Report — Novaders
Acme Corp — PQC Readiness Report
Scanned: 847 assets across 12 services
● CRITICAL  12 assets
  Action required before 2028
● HIGH      8 assets
  Action required before 2030
● MEDIUM    5 assets
  Monitor, low urgency
● SAFE     23 assets
  No action needed
Top Findings:
1. payments-service
  RSA-2048 → ML-KEM-768 [FIPS 203]
  CRITICAL · Effort: Medium — library swap
2. auth-service
  ECDSA P-256 → ML-DSA-65 [FIPS 204]
  CRITICAL · Effort: Medium — library swap
3. api.acme.com
  TLS 1.2 RSA → TLS 1.3 + hybrid PQC
  HIGH · Effort: Low — config change
4. 14 SSH keys
  RSA-2048 → Ed25519
  HIGH — rotate immediately
↓ Download Sample Report (PDF)
What's in the report
  • Full asset inventory with location in your stack
  • NIST FIPS 203/204/205 replacement mapped per finding
  • Effort estimate (Low / Medium / High) for engineering
  • Prioritised by data sensitivity and retention period
  • Hybrid migration path — classical + PQC in parallel
  • Deadline mapping to NIST IR 8547 timelines
Why Novaders

We've shipped post-quantum cryptography in production.

Most vendors in this space talk about PQC. We implemented ML-DSA-65 (NIST FIPS 204) in AuthentiScan — our anti-counterfeit authentication platform — including key rotation, signing key versioning, and backward compatibility.

ML-DSA-65
Implemented in production via AuthentiScan — among the first production systems in India on NIST FIPS 204.
FIPS 203 · 204 · 205
Full coverage of all three finalized NIST PQC standards in our rules engine and migration mapping.
Hybrid-first
We recommend running classical + PQC in parallel, exactly as Cloudflare and Google do in production today.
Vendor-neutral
No lock-in to specific libraries or cloud providers — we recommend based on your existing stack.
Who Needs This

If any of these apply, your window is 2026–2027.

🛡️
Defence & Aerospace
US federal supply chain mandates are already live. CMMC compliance now touches cryptographic standards.
🏦
Banking & Financial Services
Transaction data with long retention is already at risk from harvest-now-decrypt-later attacks.
🏥
Healthcare & Pharma
Patient records held for 20–30 years. The HNDL threat is not theoretical for your data class.
☁️
SaaS & Cloud Vendors
Your enterprise clients will ask before you are ready. Be ahead of the question, not behind it.
🏛️
Government & Public Sector
Infrastructure with decade-long operational lifespans must begin planning migration now.
🌐
Any Company Processing EU/US Data
DPDP, NIS2, and CISA are converging on PQC requirements. Cross-border compliance points the same direction.
Self-Assessment

Not sure where you stand?
Find out in 3 minutes.

Answer 9 questions about your stack. Get an instant Cryptographic Debt Score — and know which systems to fix first.

Pricing

Start with an assessment.
No platform commitment needed.

Starter Assessment
TLS + Dependencies
Public surface scan, risk score, PDF report within 48 hours.
  • Public TLS certificate scan
  • Dependency file analysis
  • Risk score + top findings
  • PDF report within 48 hours
  • Code repository scan
  • SSH/infra scan
Most Popular
Full Assessment
Complete Cryptographic Audit
Every surface, every asset, full roadmap with a briefing call.
  • Everything in Starter
  • GitHub/GitLab code scan
  • SSH key inventory
  • API endpoint inspection
  • Prioritised migration roadmap
  • NIST IR 8547 deadline mapping
  • 60-minute briefing call
Ongoing Monitoring
Post-Migration Assurance
Continuous scanning, alerts, and dedicated advisory support.
  • Everything in Full Assessment
  • Continuous scanning
  • New vulnerability alerts
  • Monthly readiness report
  • Change tracking over time
  • Dedicated advisory support

Assessments delivered remotely. Air-gapped and on-premise options available for sensitive environments.

FAQ

Frequently Asked Questions

Everything your CTO and CISO are already wondering.

The computers that will break RSA do not exist yet — but that is not the right question to ask. The threat that exists today is called Harvest Now, Decrypt Later. Nation-state actors are recording your encrypted traffic right now, storing it, and waiting for quantum computers to arrive to decrypt it. If any data you transmit today must stay confidential for 5 or more years — financial records, healthcare data, contracts, IP — it is already at risk. The migration also takes 2–3 years minimum. By the time quantum computers are ready, it will be too late to start.
TLS protects data in transit, but TLS 1.2 and even TLS 1.3 rely on RSA or ECDH for the key exchange — both of which are broken by Shor's algorithm on a quantum computer. Chrome and Firefox have already begun shipping hybrid post-quantum TLS (X25519 + ML-KEM) by default. Your servers need to support it too, or the connection falls back to classical crypto. The bigger risk is usually not your public website — it is your internal services, APIs, certificate infrastructure, SSH keys, and dependencies that still use RSA or ECDSA and are invisible until you scan for them.
No — not for the initial scan. We start with what requires zero code access: your public TLS certificates, cipher suites, and dependency manifest files (package.json, requirements.txt, pom.xml). These alone surface 60–70% of your cryptographic risk. The full assessment adds GitHub or GitLab repository scanning, but even that is read-only and scoped to specific repos you authorise. For organisations with air-gapped or highly sensitive environments, we provide a CLI tool that runs locally — your code never leaves your environment, only the risk report does.
The scan itself runs in hours. A Starter Assessment (TLS + dependencies) is delivered within 48 hours of engagement. A Full Assessment — covering code, infrastructure, SSH keys, and API endpoints — takes 5–7 working days including the briefing call where we walk your team through findings and answer questions. The migration roadmap is part of the deliverable, not a separate engagement.
A hard cutover from RSA to ML-KEM overnight would break compatibility with any client, partner, or system that has not yet upgraded. Hybrid mode runs classical and post-quantum algorithms in parallel — for example, X25519 + ML-KEM-768 together for key exchange. If either algorithm is safe, the connection is safe. This is exactly how Cloudflare, Google, and Apple have deployed PQC in production. We recommend hybrid first, full cutover second — giving your ecosystem time to catch up while you are already protected.
Directly, NIST standards are US government requirements. But they apply to you in three ways. First, if you process or store data for US or EU clients, your enterprise customers will start asking for NIST PQC compliance in contracts by 2027. Second, RBI, SEBI, and CERT-In typically follow NIST and BIS guidance with a 1–2 year lag — the Indian regulatory mandate is coming, just not yet announced. Third, the NIST standards are the global benchmark — every major cloud provider, browser, and OS vendor is aligning to FIPS 203/204/205. Your stack will be affected regardless of which country you operate in.
The assessment gives your engineering team everything they need: a prioritised list of findings, the exact replacement algorithm for each, effort estimates, and deadline mapping. Most migrations — library swaps, TLS config updates, certificate reissuance — are handled by your own team using our roadmap. For organisations that need hands-on implementation support, we offer migration engineering as a separate engagement. We are also available for review and sign-off once your team has completed the changes.
Free Domain Scan

Know your risk in 60 seconds.

Enter your domain. We scan your public TLS certificates and cipher suites — no code access, no signup required.

No account required. Results emailed within 24 hours. We never store your domain data.