What's coming — and the quantum clock that's already ticking
"The data you encrypt today, a quantum computer may decrypt in fifteen years. For a network's long-lived secrets, the future is already a threat."
— THE HARVEST-NOW-DECRYPT-LATER PROBLEM
Security doesn't stand still. 5G-Advanced (Rel-18+) refines the architecture; Rel-19 and the early 6G studies are shaping what comes next. Two themes dominate the horizon: post-quantum cryptography (a clock already ticking for long-lived secrets) and AI-native, sensing-rich networks that expand both capability and attack surface. This closing chapter of Part 7 previews where 5G security is heading and how to prepare.
🎯 Learning objectives
Summarize Rel-18 security themes and Rel-19 directions.
Explain the post-quantum threat and migration.
Describe crypto agility.
Preview AI-native and 6G trust concepts.
📘 Standards reference box — Chapter 32
Reference
Title
Note
TS 33.501
5G security (Rel-18 baseline)
Rel-18, v18.11.0 (2026-04)
SA3 Rel-19 work plan
Ongoing security studies (PQC, AIML, ambient IoT)
in progress — verify
NIST PQC / IETF
Post-quantum standards & protocol integration
current
Checked June 2026. Rel-19 and 6G are moving targets — verify against the latest 3GPP version.
32.1 The Security Evolution Timeline
FIGURE 32.1Security Evolution — Rel-15 to 6G
Purpose: the arc this book sits on. Rel-18 is the baseline; Rel-19 and 6G are moving targets — which is why the standing instruction is always to verify the latest version.
FIGURE 32.2Rel-18 Security Theme Map
Purpose: what 5G-Advanced added on the security side — incremental refinement (AKMA roaming, AI/ML, sidelink, NPN) rather than a new architecture.
FIGURE 32.3Rel-19 Directions (Verify Latest)
Purpose: honesty about the horizon. Rel-19 security was unfrozen at writing; treat these as directions to track, not specifications to design against yet.
32.2 The Quantum Clock
FIGURE 32.4Quantum Threat Timeline vs Network Lifetimes
Purpose: why quantum is a present concern. Harvest-now-decrypt-later means data with a long confidentiality lifetime — and long-lived keys — must be protected against quantum before quantum exists.
FIGURE 32.5PQC Candidates and Where They Land
Purpose: where post-quantum algorithms fit in 5G. KEMs replace/augment key exchange (incl. SUCI's ECIES successor); PQC signatures protect the PKI; hybrid modes bridge the transition safely.
FIGURE 32.6Crypto Agility Architecture
Purpose: the real preparation for PQC. You can't predict the winning algorithm, but you can build systems that swap algorithms cheaply — 5G's algorithm-ID design (Chapters 7–8) is a head start.
FIGURE 32.7AI-Native Security Concept for 6G
Purpose: the 6G direction and its caution. AI-native networks promise autonomous security but multiply the AI attack surface — the governance of Chapter 31 becomes more important, not less.
FIGURE 32.86G Trust Architecture Preview
Purpose: the shape of what's next. 6G security will evolve 5G's foundations — PQC by design, AI-native, sensing-aware (ISAC privacy), more distributed — but the trust triangle (Chapter 1) endures.
32.2 The Practical Operator View
Start crypto-agility now — inventory where algorithms are hard-coded; make them swappable. This is the single most valuable PQC preparation.
Identify long-lived secrets (subscription keys, long-confidential data) most exposed to harvest-now-decrypt-later.
Track SA3 Rel-19 and NIST/IETF PQC — adopt hybrid modes as they standardize.
Apply Chapter-31 AI governance as networks become more AI-native.
Keep verifying — Rel-19/6G are moving targets; this book's flags say "verify latest" for a reason.
Capturing ciphertext today to decrypt with future quantum
crypto agility
Ability to swap algorithms without re-architecting
hybrid mode
Classical + PQC together during transition
ISAC
Integrated Sensing and Communication (6G theme)
Real network example. A forward-looking operator commissioned a "quantum readiness" assessment. Rather than wait for final PQC standards, they focused on crypto agility: they inventoried every place algorithms were hard-coded (some vendor NFs pinned cipher suites in ways that couldn't be changed without a software release), and they made vendor crypto-agility a procurement requirement going forward. They also identified that their subscription keys and certain long-retention subscriber data were the assets most exposed to harvest-now-decrypt-later, and prioritized those for hybrid-mode protection as it standardized. They didn't try to deploy PQC prematurely — they made sure that when the standards arrived, they could adopt them in months, not years. The winning quantum strategy isn't picking the algorithm; it's being able to change it.
★ Chapter Summary
Security keeps evolving: Rel-18 (5G-Advanced) refined the model; Rel-19 and 6G are moving targets — verify the latest.
Post-quantum is a present concern via harvest-now-decrypt-later on long-lived secrets.
PQC lands in key exchange (KEMs) and signatures; hybrid modes bridge the transition.
Crypto agility — swapping algorithms cheaply — is the most valuable preparation; 5G's algorithm-ID design is a head start.
6G points to AI-native, PQC-by-design, sensing-aware, distributed security — evolving, not replacing, 5G's foundations.
? Review Questions
What were the main Rel-18 security themes, and why are Rel-19 items flagged "verify"?
Explain harvest-now-decrypt-later and why it makes quantum a present concern.
Where does PQC land in a 5G system, and what is a hybrid mode?
What is crypto agility and why is it the most valuable PQC preparation?
How does 5G's existing design (algorithm IDs) help with agility?
What new risks does an AI-native 6G introduce?
Which assets are most exposed to the quantum threat, and why?
Why is "being able to change the algorithm" a better strategy than "picking the algorithm"?
🧪 Mini lab — a quantum-readiness inventory
For a 5G network (real or modeled): (1) Inventory every place cryptographic algorithms are used: SUCI ECIES, TLS/IPsec, certificate/token signing, AKA. (2) For each, note whether the algorithm is swappable (configurable/negotiable) or hard-coded (needs a software release) — your crypto-agility map. (3) Identify the assets with the longest confidentiality lifetime (subscription keys, long-retention data) — your harvest-now-decrypt-later priorities. (4) Write the procurement requirement that would make future NFs crypto-agile. (5) Decide where you'd pilot a hybrid mode first when standards land. You've now built the practical quantum-readiness plan — focused on agility, not premature algorithm choice — that closes the forward-looking part of this book.