Every time a user logs into your application, a JWT signed with RSA or ECDSA validates their identity. Every banking transaction, every sensitive data exchange, every SSL certificate relies on these algorithms. And they're all going to become vulnerable. Not tomorrow. But the timeline is shorter than most executives think. Here's what Moroccan and African businesses need to know to prepare.
The Quantum Threat in Plain Terms
Quantum computers exploit quantum physics phenomena to solve certain problems exponentially faster than classical computers. Shor's algorithm, published in 1994, demonstrates that a sufficiently powerful quantum computer can break RSA and ECDSA in polynomial time.
Today, the most advanced quantum computers (IBM Condor, Google Willow) have between 1,000 and 1,500 qubits. Breaking an RSA-2048 key requires approximately 4,000 stable logical qubits. At first glance, we have time.
Except that:
-
Quantum Moore's Law is accelerating: Qubit count roughly doubles every 18 months. Industry forecasts place the first "cryptographically relevant" quantum processors between 2029 and 2035.
-
The "harvest now, decrypt later" attack: State actors are collecting encrypted data today to decrypt once quantum capability is available. If your data has a lifespan exceeding 10 years (trade secrets, medical data, intellectual property), it's already at risk.
-
Migration cycles are long: Changing a company's cryptographic algorithms takes 3-7 years. Starting in 2026 means being ready around 2030, just in time.
What This Means for JWT and Authentication
JSON Web Tokens (JWT) are everywhere: API authentication, single sign-on, microservices. Most use RS256 (RSA) or ES256 (ECDSA) for signatures.
When an attacker can forge valid signatures, they can:
- Impersonate any user
- Elevate privileges at will
- Access all token-protected resources
Your entire authentication system collapses.
Post-Quantum Standards Are Ready
In August 2024, NIST (National Institute of Standards and Technology) finalized three post-quantum algorithms:
ML-KEM (CRYSTALS-Kyber)
For key exchange. Replaces Diffie-Hellman and RSA for establishing secure sessions.
ML-DSA (CRYSTALS-Dilithium)
For digital signatures. Replaces RSA and ECDSA for signing documents, tokens, and certificates.
SLH-DSA (SPHINCS+)
For digital signatures with a different approach (hash-based). Slower but based on more conservative cryptographic assumptions.
These algorithms aren't experimental. They've undergone years of cryptographic analysis and are now recommended for new implementations.
Action Plan for Businesses
Phase 1: Cryptographic Inventory (1-3 months)
Before migrating, you need to know what you use. Map:
- Applications: What signing and encryption algorithms do your APIs, authentication systems, and databases use?
- Libraries: What versions of OpenSSL, BouncyCastle, or Node.js crypto are you running?
- Certificates: When do your SSL/TLS certificates expire? What algorithms do they use?
- Partners: What cryptographic protocols do you use for B2B exchanges (EDI, partner APIs)?
For SMEs, this inventory can be completed in a few weeks. For large enterprises, plan 2-3 months with a dedicated team.
Phase 2: Migration Strategy (2-4 months)
Two main approaches:
Hybrid approach: Combine a classical algorithm (RSA/ECDSA) with a post-quantum one. If one is broken, the other still protects. This is the recommended approach for transition.
Pure post-quantum approach: Replace directly with post-quantum algorithms. Simpler to maintain long-term but riskier if a vulnerability is discovered in the new algorithms.
For JWT specifically, the hybrid strategy involves signing with two algorithms and verifying both signatures. Libraries like jose (Node.js) or python-jose are beginning to support these modes.
Phase 3: Progressive Deployment (6-18 months)
Don't migrate everything at once. Start with:
- Internal environments: Test systems, internal tools, non-critical applications
- New applications: All new development uses post-quantum algorithms from the start
- Critical applications: Planned migration with extensive testing and rollback plans
At Claro Digital, our custom development services now systematically include a post-quantum posture assessment for new projects.
The Cost of Inaction
Waiting isn't a viable strategy. Here are the risks:
Regulatory Risk
The US government (via NSA and NIST) already imposes migration timelines for federal systems. The European Union is preparing similar requirements through the Cyber Resilience Act. Morocco, aligned with international standards, will likely follow.
Commercial Risk
Large enterprises are starting to require post-quantum guarantees from their vendors. If your competitor can demonstrate a more robust cryptographic posture, you'll lose contracts.
Operational Risk
A forced emergency migration (after a quantum breakthrough) will cost 5-10x more than a planned multi-year migration.
What You Can Do Right Now
Immediate Actions (This Week)
-
Train your team: Ensure your developers and architects understand post-quantum challenges.
-
Update your libraries: Recent versions of OpenSSL (3.2+), BoringSSL, and liboqs support post-quantum algorithms.
-
Enable TLS drafts: Chrome and Firefox already support hybrid X25519+ML-KEM key exchanges in TLS 1.3.
Medium-Term Actions (This Quarter)
-
Launch the cryptographic inventory: Use tools like CryptoSense or IBM Quantum Safe Explorer to scan your applications.
-
Define a policy: What's your target date for complete migration? Which systems are priorities?
-
Budget: Allocate necessary resources in your IT planning.
Long-Term Actions (This Year)
-
Post-quantum pilot: Deploy a first system in hybrid mode to gain experience.
-
Commission an audit: Have your roadmap evaluated by an external expert. For a complete cybersecurity posture analysis, a specialized audit will identify gaps and priorities.
-
Communicate: Inform your partners and clients about your post-quantum strategy. It's a competitive advantage.
The Moroccan Context
Morocco has modern cryptographic infrastructure thanks to banking and telecom investments. However, several specific challenges exist:
Local Expertise
Post-quantum cryptography experts are rare globally, even more so locally. Moroccan businesses will either need to train internally or engage international consultants.
Vendor Ecosystem
Most software vendors used in Morocco (ERP, CRM, business tools) don't yet have clear post-quantum roadmaps. Check with your vendors.
Banking Sector
Bank Al-Maghrib hasn't yet published specific directives but closely follows Basel Committee recommendations. Expect formal requirements by 2028.
Crypto Agility: A Sustainable Approach
Rather than planning a single major migration, adopt a "crypto-agile" architecture:
-
Algorithm abstraction: Never hardcode a specific algorithm. Use interfaces that allow changing implementations without touching business code.
-
Dynamic configuration: Algorithms should be changeable through configuration, not redeployment.
-
Automated testing: Your CI/CD pipeline must validate that cryptographic changes don't break functionality.
This approach protects you not only against the quantum threat but also against any future cryptographic vulnerability.
Sector-Specific Use Cases
Financial Services
Banks and payment institutions are on the front line. Swift transactions, electronic signature certificates, and interbank connections all rely on vulnerable algorithms. Regulatory pressure will be strong in this sector.
Priority: Start with client authentication systems and interbank communication channels. Real-time transactions can wait, but archived data is already at risk.
Healthcare
Medical records have a lifespan of several decades. A 30-year-old patient today will have relevant medical data for 50 years or more. If this data is collected today by malicious actors, it can be decrypted before the patient's end of life.
Priority: Long-term archive encryption and exchanges between healthcare facilities.
Industry and Intellectual Property
Trade secrets, pending patents, and R&D data are prime targets for state espionage. The value of this data doesn't diminish over time, unlike a one-time financial transaction.
Priority: Identify high strategic value data and migrate its protection first.
Common Migration Mistakes to Avoid
Based on early adoption experiences, here are pitfalls to watch for:
Underestimating Scope
Many teams initially inventory only their own applications, forgetting third-party integrations. Your payment processor, CRM, and cloud services all have cryptographic dependencies. A complete inventory must include the entire supply chain.
Skipping the Hybrid Phase
Some teams attempt direct migration to pure post-quantum algorithms. This creates unnecessary risk. The hybrid approach (classical + post-quantum) provides a safety net during transition and is explicitly recommended by NIST for the coming years.
Ignoring Performance Impact
While post-quantum algorithms are production-ready, they have different performance characteristics. ML-DSA signatures are larger (2-4KB vs 256 bytes for ECDSA), which impacts bandwidth-constrained applications. Test thoroughly in realistic conditions.
Treating It as a One-Time Project
Cryptography evolves. New vulnerabilities are discovered, algorithms are refined, and standards update. Build infrastructure that can adapt, not a one-time migration to a static target.
Resources to Go Further
To deepen your understanding and begin migration:
- NIST Post-Quantum Cryptography: Official documentation of finalized algorithms
- Open Quantum Safe: Open-source library implementing post-quantum algorithms
- Cloudflare Research: Technical articles on large-scale post-quantum deployment
- IBM Quantum Safe: Inventory and migration planning tools
Investing in technology monitoring today will avoid much higher migration costs tomorrow. The organizations that move early will have competitive advantages in vendor selection, talent acquisition, and regulatory compliance.
FAQ
When will quantum computers be able to break RSA-2048?
Industry consensus estimates place this capability between 2029 and 2035. Google and IBM have both announced roadmaps targeting processors with more than 10,000 logical qubits by 2030. However, progress can accelerate unpredictably.
Is my current data at risk?
If your data must remain confidential for more than 10 years (intellectual property, trade secrets, medical data), yes. State actors are collecting encrypted communications today to decrypt later. This is the "harvest now, decrypt later" attack.
How much does a post-quantum migration cost?
For an SME with 5-10 applications, expect $20,000-50,000 over 2-3 years (inventory, training, migration, testing). For large enterprises, budgets often exceed several hundred thousand dollars. Starting early significantly reduces these costs.
Are post-quantum algorithms slower?
Yes, generally. ML-DSA (Dilithium) generates signatures approximately 2-5x slower than ECDSA. ML-KEM is comparable to X25519 for key exchange. These differences are negligible for most applications but can impact very high-frequency systems.
What if my software vendor doesn't support post-quantum?
Document the risk, escalate to management, and include contractual clauses requiring a post-quantum roadmap in your next renewals. If the vendor refuses, evaluate alternatives.