| Component | Role | Use in the trial |
|---|---|---|
| QKD | Quantum key distribution | NEC optical system supplies secret material |
| ML-KEM-768 | Post-quantum key encapsulation | Establishes mathematical shared secret |
| HKDF-SHA256 | Key derivation | Combines QKD and ML-KEM secret material |
| ML-DSA-44 | Digital signatures | Certificate-based peer authentication |
| ETSI GS QKD 014 | REST API | Key delivery interface between systems |
- The secrets that must outlive today’s encryption
- Two meanings of “quantum-safe”
- Inside the NEC–IBM Japan trial
- A precise division of cryptographic labor
- From the BB84 idea to NIST’s 2024 standards
- Why the clock starts before the quantum machine arrives
- The costs and limits that a laboratory success cannot remove
- Why banks and data centers are the obvious candidates
- International standards, not a proprietary island
- What would turn this into infrastructure?
The secrets that must outlive today’s encryption
A bank sends instructions between data centers. A manufacturer transfers designs that will remain sensitive for a decade. A government agency stores records that must be protected long after the computers used to create them have been replaced. In each case, the security question extends beyond the moment a message crosses the network: could someone record the encrypted traffic now and decipher it years later?
NEC and IBM Japan said on November 17 that they had demonstrated a hybrid form of quantum-safe communications combining quantum key distribution, or QKD, with post-quantum cryptography, or PQC. The trial ran from July through September 2026. The companies describe the specific integration method as a first in Japan.
The novelty is not a claim that a quantum computer has broken today’s banking networks, or that a finished network is ready to install everywhere. It is a practical attempt to connect two fundamentally different methods of creating cryptographic key material to the communications infrastructure institutions already use.
Two meanings of “quantum-safe”
Quantum key distribution sends quantum states over a physical channel, commonly optical fiber, so participants can generate and share secret key material under defined assumptions. Its security properties arise from quantum physics, but operating it requires purpose-built components and careful protection of devices and key management. QKD is not an ordinary software update.
Post-quantum cryptography takes a different route. It consists of mathematical algorithms designed to resist attacks from future large quantum computers, while running on conventional computers. PQC can be incorporated into protocols and software deployed across networks where quantum optical equipment would be impractical.
Combining the two is therefore not redundancy in the everyday sense of using the same mechanism twice. One source of secret material comes from QKD hardware; the other arises from a standardized mathematical key-establishment scheme. Each brings strengths and constraints. Integration can diversify the security architecture, but does not erase vulnerabilities in endpoints, authentication or operations.
Inside the NEC–IBM Japan trial
The reported system connected NEC’s QKD equipment to a customized IBM Quantum Safe Proxy through a REST-based interface conforming to ETSI GS QKD 014. The IBM component was adapted for a TLS proxy architecture, positioned in front of an existing application or communications system.
This positioning matters. Banks and infrastructure operators may depend on decades-old applications that cannot be rewritten rapidly. A proxy can introduce changes at a network boundary rather than requiring major modifications within every program. NEC and IBM Japan verified the feasibility of that approach in their test environment, not universal drop-in compatibility across all legacy software.
The European Telecommunications Standards Institute interface also serves a less glamorous but essential purpose: enabling a QKD key-management system and an application-side component to communicate through specified data formats and operations. Without dependable interfaces, promising cryptographic methods remain isolated laboratory products.
A precise division of cryptographic labor
The technical arrangement is unusually clear in the companies’ release. It combined secret material delivered through QKD with a secret established using ML-KEM-768, a NIST-standardized post-quantum key-encapsulation mechanism. HKDF-SHA256 was used to derive material for protecting the TLS communication. This is not a simple either-or switch choosing the quantum or mathematical method.
Authentication had a separate role. The demonstration used certificate-based authentication with ML-DSA-44, a post-quantum digital signature scheme. ML-KEM handles key establishment; ML-DSA provides signatures and identity assurance. Both are designed for a quantum-resilient future, but do not perform the same job.
The companies added an important qualification: they did not evaluate QKD as a substitute for certificate-based authentication, nor as an independently operating backup communications channel. A story claiming their design automatically fails over to QKD-only communication would misrepresent the experiment.
From the BB84 idea to NIST’s 2024 standards
The roots of the demonstration lie in two scientific timelines. In 1984, Charles Bennett and Gilles Brassard proposed a quantum key-distribution approach that became known as BB84. Decades of work on optics, detectors, fiber links and network engineering followed. NEC says it has worked on quantum cryptographic communication technologies for more than twenty years.
A different research path began with the threat quantum computation poses to conventional public-key systems. Peter Shor’s 1990s algorithm showed how a sufficiently capable quantum computer could undermine mathematical problems used by RSA and elliptic-curve cryptography. That hypothetical capability is not equivalent to the capabilities of quantum systems available today.
The U.S. National Institute of Standards and Technology launched its post-quantum standardization work in 2016 and approved three principal standards in August 2024. FIPS 203 specifies ML-KEM; FIPS 204 specifies ML-DSA; and FIPS 205 specifies SLH-DSA. The NEC–IBM Japan trial built on two of those standardized algorithm families rather than inventing an alternative proprietary cryptographic primitive.
Why the clock starts before the quantum machine arrives
No public consensus can specify the year when a cryptographically relevant quantum computer will exist. That uncertainty sometimes obscures the strongest reason to begin migration now: data intercepted today can still matter when future computing capabilities change. NIST calls this problem “harvest now, decrypt later.”
Its October 2026 migration guidance reinforces the need for organizations to inventory vulnerable algorithms and plan transitions. Replacing cryptography is not a single patch. Certificates, hardware security modules, gateways, embedded software and services from many vendors may all be involved. The systems with the longest confidentiality requirements are particularly exposed to delays.
PQC migration does not imply every internet connection needs QKD hardware. Indeed, broadly deployable software-oriented post-quantum methods are necessary for systems that cannot support specialized optical connections. The hybrid approach in this demonstration is most relevant where the physical infrastructure and sensitivity of traffic justify both mechanisms.
The costs and limits that a laboratory success cannot remove
Quantum key distribution is often discussed as if physical laws alone guarantee complete security. Real deployments still depend on receivers, optical links, secure rooms, access controls and trusted nodes. The International Telecommunication Union’s QKD network framework emphasizes authentication and protection of the systems that generate, transport and store keys.
Long-distance optical loss and the use of intermediate trusted nodes introduce design and governance challenges. Hybrid QKD–PQC systems also create new places where implementation mistakes, configuration errors or compromised management interfaces could undermine an otherwise strong cryptographic foundation.
The November 17 announcement did not publish a comparable production benchmark for throughput, latency, failure recovery, cost or years of continuous operation. It established particular interoperability and key-establishment functions. Readers should not infer that a production banking deployment has passed independent operational testing.
Why banks and data centers are the obvious candidates
The two companies point to financial core and transaction systems and links between banks and data centers as potential future uses. These networks often carry information that must retain confidentiality well beyond the lifetime of the hardware that sends it.
A managed fiber connection between two controlled facilities may offer a workable location for dedicated QKD equipment and a proxy. That is a plausible application scenario, not an announcement of a bank customer. Whether it is economical depends on fiber access, distance, network design, certificate management, reliability requirements and the ability of operators to maintain both systems.
Financial services tend to value change control and predictable recovery as much as technological novelty. A migration approach will be judged not only on whether it establishes keys securely on a good day, but on how it responds to equipment failure, patches, expired credentials and unexpected traffic.
International standards, not a proprietary island
The ETSI GS QKD 014 API defines how an application can request and receive key material from a QKD network or key-management system. NEC and IBM Japan used that specification to bridge systems supplied by different vendors. It addresses a practical barrier to adoption: specialized cryptographic products are of limited use if they cannot be integrated with the network stack around them.
The ITU issued a technical report in June 2026 on key management for hybrid quantum-safe communications. It discusses the benefits and operational complexities of integrating QKD with PQC, including questions around trusted nodes and end-to-end protection. The broader standards work shows the Japanese trial belongs to an international design conversation.
Interoperability in one documented laboratory configuration, however, does not establish seamless interoperation with every vendor or certify overall security. Independent testing, configuration standards and lifecycle management remain necessary.
What would turn this into infrastructure?
The next milestone is evidence from realistic operational environments: measured latency, sustained data rates, key availability, monitoring, recovery behavior, device and fiber costs, and security review of the proxy and management plane. The companies said they would consider commercialization for uses requiring long-term secrecy; they did not specify a committed deployment date.
There is also a language trap in the headline “Japan’s first.” NEC and IBM Japan refer to the particular hybrid QKD/PQC proxy arrangement they demonstrated. They do not claim to have invented QKD, PQC or secure fiber communications in Japan.
The achievement is more modest—and more useful—than a promise of unbreakable encryption. It demonstrates one way to make quantum-resistant cryptography coexist with quantum key distribution in familiar TLS infrastructure. The question is now whether that architecture can become affordable, independently assessed, supportable and reliable enough for organizations whose secrets must survive the next computing era.
Primary sources and reporting limitations
This original report draws on the November 17 NEC/IBM Japan release and primary NIST, ETSI and ITU publications. We conducted no interviews or independent equipment testing. The announcement does not establish comparable distance, latency, throughput, resilience, commercial costs, independent audit findings, named customers or deployment dates.
- NEC and IBM Japan, joint technical announcement, November 17, 2026
- IBM Japan, official counterpart release
- NIST: approval of FIPS 203, 204 and 205, August 2024
- NIST post-quantum cryptography standardization
- ETSI quantum key distribution standards and interfaces
- ITU-T June 2026 technical report on hybrid quantum-safe key management
- ITU-T X.1710 QKD network security framework
- NIST October 2026 guidelines for post-quantum migration
