IBM hardware supports quantum-safe (post-quantum) encryption algorithms by combining cryptographic hardware acceleration, secure key management (ICSF/Crypto Express), and firmware-integrated algorithm support so that new post-quantum cryptography (PQC) can run efficiently and securely alongside classical cryptography.

The goal is:

Ensure systems remain secure even against future quantum computers, without losing the performance and isolation benefits of IBM Z and IBM Power hardware crypto.

1. Core idea: what “quantum-safe support” means

Quantum-safe encryption means using algorithms that are resistant to attacks from quantum computers, such as:

• lattice-based cryptography (e.g., Kyber, Dilithium)
• hash-based signatures (e.g., SPHINCS+)
• code-based or isogeny-based schemes (less common now)

IBM hardware does not “invent” these algorithms—it provides:

hardware acceleration + secure execution + key protection for PQC algorithms implemented in firmware and crypto stacks.

2. Where quantum-safe crypto runs in IBM systems

A. CPACF (on-chip crypto acceleration)

• accelerates symmetric crypto (AES, SHA)
• supports building blocks used by PQC (hashing, symmetric primitives)
• future-ready for PQC performance needs

B. Crypto Express (HSM-level support)

• executes high-assurance cryptographic operations
• protects private keys for PQC algorithms
• isolates signature generation and key usage

👉 Critical for:

• digital signatures (Dilithium-like operations)
• key encapsulation mechanisms (KEMs)

C. ICSF (software crypto layer)

• provides APIs for applications
• integrates PQC algorithms as they become available
• routes operations to hardware where possible

3. How IBM hardware enables PQC execution

Step 1: Algorithm integration

PQC algorithms are implemented in:

• ICSF updates
• z/OS crypto libraries
• Linux on Z crypto stacks

Step 2: Hardware acceleration mapping

Even if PQC is new, IBM maps heavy primitives to hardware:

• hashing → CPACF
• symmetric crypto → CPACF
• key operations → Crypto Express

Step 3: Secure key handling

For PQC keys:

• private keys are stored as secure tokens
• wrapped under hardware master keys
• never exposed in plaintext memory

Step 4: Execution isolation

When Crypto Express is used:

• PQC signing or key exchange happens inside secure hardware
• keys never leave adapter boundary
• results only are returned

4. Hybrid cryptography support (important today)

IBM systems support hybrid TLS and hybrid key exchange, combining:

• classical algorithms (RSA, ECC)
• quantum-safe algorithms (Kyber, etc.)

This allows:

• backward compatibility
• gradual migration to PQC

👉 Hardware accelerates both types simultaneously.

5. Performance challenges and hardware solution

PQC algorithms are:

• computationally heavier than ECC/RSA
• require large key sizes and more hashing

IBM addresses this using:

A. Parallel crypto engines

• CPACF multi-engine execution
• Crypto Express concurrent request handling

B. Offload model

• CPU only orchestrates
• hardware executes heavy math

C. Low-latency secure paths

• avoids software crypto bottlenecks

6. Key protection for quantum-safe cryptography

Even with PQC, keys must be protected:

A. Master key wrapping

• PQC keys are encrypted under hardware master keys

B. Non-exportable private keys

• Crypto Express enforces key non-extraction

C. Secure lifecycle management

• generation, rotation, destruction all hardware-controlled

7. Role of secure enclaves (confidential computing)

Secure execution environments ensure:

• PQC operations cannot be observed by OS or hypervisor
• keys remain hidden during computation
• resistance to side-channel + quantum threats combined

8. Future readiness (IBM roadmap conceptually)

IBM Z and Power architectures are designed so that:

• new PQC algorithms can be added via firmware/software updates
• hardware crypto engines continue to accelerate primitives
• no need for full CPU replacement

👉 This is called crypto-agile architecture

9. Simple mental model

Think of IBM quantum-safe support as:

A system where new post-quantum cryptographic algorithms run in software stacks but are accelerated and protected by specialized hardware engines that ensure keys remain isolated, operations are fast, and execution is secure against both classical and future quantum threats.

10. Key takeaway

IBM hardware supports quantum-safe encryption by:

• integrating PQC algorithms into ICSF and crypto stacks
• accelerating cryptographic primitives using CPACF
• securing key operations in Crypto Express (HSM-level protection)
• isolating execution in secure hardware domains
• enabling hybrid classical + quantum-safe encryption models
• providing crypto agility for future algorithm updates