What your vendor says about PQC tells you if they are ready
Allot CTO outlines a telecom post-quantum migration playbook: inventory crypto, deploy hybrid ML-KEM on TLS first, and avoid missed interfaces.
Dr. Yaakov Stein, VP CTO of Allot, explains how mobile operators should triage post-quantum migration by data shelf life, protecting subscriber identity mappings, billing records, and call metadata that stay sensitive for years. He recommends starting with a comprehensive crypto inventory, then hybrid ML-KEM key exchange on TLS-protected 5G SBA and management interfaces, followed by IPsec backhaul and roaming links. Stein warns that migrations most often fail operationally through missed legacy interfaces such as SSH, RADIUS, or forgotten load balancers, and cites the early Kyber multi-packet TLS client hello issue as an example of middlebox incompatibility.
- Inventory all public-key cryptography including 5G SBA, IPsec, DNSsec, and encrypted APIs
- Deploy hybrid X25519+ML-KEM on TLS interfaces first, then IPsec backhaul and roaming links
- Long-shelf-life data includes subscriber mappings, billing records, and call metadata
- Suspicious vendor answers include waiting for standards and claiming symmetric-only quantum safety
- Migration often fails via missed interfaces like SSH, RADIUS, or old load balancers
From the original article
4 min read at helpnetsecurity.com
In this interview with Help Net Security, Dr. Yaakov Stein, VP CTO of Allot , discusses what post-quantum readiness looks like inside a mobile network. The discussion covers which operator traffic stays sensitive for years, including subscriber identity mappings, billing records and call metadata, and which becomes worthless within hours.
By @helpnetsecurity · helpnetsecurity.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.