Post-quantum readiness for KSA and UAE

Your encryption has an expiry date.

NIST has finalised the quantum-safe standards, and the deprecation clock on RSA and ECC is running. Data Wide's PQC readiness assessment shows exactly where your organisation stands, and CipherTrust Manager gives you one place to manage every key through the migration.

The risk starts before the quantum computer does

The question is not when a quantum computer arrives. It's whether your data will still matter when it does.

Harvest now, decrypt later

Attackers can copy encrypted traffic and backups today and read them later. Anything that must stay confidential for years is already exposed.

Migration takes years

Cryptography sits inside applications, devices, PKI, payment systems and vendor products. Finding it all is usually the slowest part.

The deadlines are set

NIST deprecates RSA-2048 and ECC after 2030 and disallows them after 2035. Most regulators take their lead from NIST.

Check your exposure

Three numbers decide whether your data outlives your encryption.

Exposed by 6 years. Data you still encrypt with RSA or ECC at the end of your migration needs protecting until 2041, six years past your quantum horizon of 2035.

Based on Mosca's inequality: if shelf life plus migration time is longer than the time until a quantum threat, you are exposed.

Post Quantom Migration timeline

Quantum-safe migration timeline
Source: NIST IR 8547
  1. Standards are final

    FIPS 203, 204 & 205 published: ML-KEM, ML-DSA and SLH-DSA

  2. You are here

    Assess, discover, test

    Inventory every key and certificate, test crypto-agility, start migrating long-lived data

  3. Transition

    RSA-2048 and ECC deprecated for federal use — most regulators follow NIST

  4. Quantum-safe only

    Quantum-vulnerable algorithms disallowed

Harvest now, decrypt later. Data encrypted with RSA-2048 and stolen today can be decrypted the day a cryptographically relevant quantum computer exists. That is why the deadline is now, not 2035.

From inventory to crypto-agility

Three phases, delivered on Thales technology and coordinated with the partners and cloud providers you already work with.
Phase 1

Assess

Know what you have and what is at risk before you change anything.

PQC risk assessment

A migration strategy with priorities ranked by data value, shelf life and exposure.
Data Wide advisory

Crypto inventory through discovery

A baseline of every key, certificate and algorithm in use, so crypto posture becomes something you manage.
CipherTrust Manager
Discovery tooling
Phase 2

Test and transition

Prove PQC works in your environment, then move system by system.

Set up a test environment

Run quantum-safe algorithms against your own workloads without touching production.
Luna HSM
High Speed Encryptors
CipherTrust

Encryption and key hygiene

Centralise key lifecycle and policy first, so changing algorithms later is a configuration change.
Luna HSM
CipherTrust Manager

Test priority applications

Start where exposure is highest: externally facing services and long-lived trust chains.
TLS & VPN
PKI
Code signing
CLM

Switch to PQC

Hybrid classic-plus-PQC where it lowers transition risk, then full post-quantum algorithms.
ML-KEM
ML-DSA
Phase 3

Operate crypto-agile

Stay ready for the next change instead of repeating this project.

Remain flexible

Swap algorithms, keys and certificates as standards evolve, without re-engineering applications.
Thales portfolio
Managed services

The risk starts before the quantum computer does

The question is not when a quantum computer arrives. It's whether your data will still matter when it does.

Cryptographic inventory

Every key, certificate and algorithm, and the systems that depend on them.

Cryptographic inventory

Which systems hold long-lived data and rely on quantum-vulnerable algorithms.

Migration roadmap

A sequenced, budget-ready plan mapped to the NIST 2030 and 2035 deadlines.

Quick wins

Key management and certificate fixes you can make now, before any algorithm changes.

Three rules we migrate by

Hybrid only where it helps

Classic plus PQC together where it reduces operational or interoperability risk during transition. A temporary safeguard, not the end state.

Plan for the whole ecosystem

Changing algorithms, protocols and key infrastructure touches vendors, cloud providers and partners. We coordinate them in one plan.

Move with the standards

Start with NIST-standardised algorithms. As standards evolve, implement, validate and re-certify as required.

Common questions