Skip to content

Composite Hybrid Keys Explained

Target Audience: Technical Marketing, Pre-sales Engineers
Document Type: Technical Explainer
Version: 3.0.0

What Are Composite Keys?

Imagine a safe with two locks - one classical, one quantum-resistant. To open it, you need BOTH keys.

Composite Hybrid Keys work the same way for encryption:

  • Lock 1: Classical algorithm (X25519, analysed for about two decades)
  • Lock 2: Post-quantum algorithm (ML-KEM, resistant to quantum computers)
  • Security: Data safe even if one lock is picked

The Quantum Threat: Harvest Now, Decrypt Later

Harvest Now, Decrypt Later

The Attack: 1. Today: Adversary intercepts and stores encrypted data 2. Tomorrow (no consensus date): a cryptographically relevant quantum computer becomes available 3. Decrypt: Adversary uses quantum computer to break classical encryption 4. Result: Confidential data exposed years later

Real-World Impact:

  • State secrets compromised
  • Financial transactions exposed
  • Healthcare records breached
  • Intellectual property stolen

Why It Matters NOW

Timeline:

  • Today: quantum computers exist, far from breaking RSA-2048
  • NIST IR 8547 (initial public draft, November 2024): quantum-vulnerable public-key algorithms deprecated after 2030, disallowed after 2035
  • Your data: may still be valuable when a cryptographically relevant quantum computer exists

Example: 

Today: encrypt a patient medical record with RSA-2048
Later: a quantum computer breaks RSA-2048
Result: a record that must stay confidential for decades is exposed

How ANKASecure Solves This

COMPOSITE_KEM_COMBINE

Two-Lock System:

Encryption:
1. Run X25519 (classical) as a KEM → secret₁ + ciphertext₁
2. Run ML-KEM-768 (quantum-resistant) as a KEM → secret₂ + ciphertext₂
3. Combine both secrets AND both ciphertexts with the key combiner → final encryption key
4. Encrypt data with final key

Decryption (requires BOTH):
1. Recover secret₁ from ciphertext₁ with the X25519 private key
2. Recover secret₂ from ciphertext₂ with the ML-KEM private key
3. Combine both secrets AND both ciphertexts with the key combiner → final encryption key
4. Decrypt data

Quantum Attack Scenario: 

Later: a quantum computer breaks X25519
Result: Adversary gets secret₁
Problem: Still needs secret₂ (protected by ML-KEM)
Outcome: ✅ Data remains confidential

Real-World Analogy

Bank Vault Comparison

Traditional Encryption (SIMPLE key): 

Bank Vault:  [Single Lock - RSA]
Risk:        Quantum computer picks lock
Result:      Vault opens, money stolen

ANKASecure COMPOSITE_KEM_COMBINE (AND-decrypt): 

Bank Vault:  [Lock A: X25519] AND [Lock B: ML-KEM]
Risk:        Must pick BOTH locks
Protection:  Even if Lock A picked (quantum), Lock B remains secure
Result:      ✅ Vault stays locked

Technical Highlights (Simplified)

The Key Combiner

What: A cryptographic function that derives the encryption key from both algorithms' secrets and both ciphertexts, so breaking one algorithm is not enough

Why: The NIST SP 800-227 method (not ad-hoc XOR), with five choices: HKDF-SHA256, HKDF-SHA384, HKDF-SHA512, or ETSI's CatKDF and CasKDF

Analogy: Like mixing two colors - you get a new color that's not either original

Code (simplified): 

encryption_key = KeyCombine(classical_secret, pqc_secret, classical_ciphertext, pqc_ciphertext)

JWE General JSON Format

SIMPLE keys use (compact): 

eyJhbGc...header.key.iv.ciphertext.tag

COMPOSITE keys use (general JSON): 

{
  "recipients": [
    {"header": {"alg": "X25519"}, "encrypted_key": "..."},
    {"header": {"alg": "ML-KEM-768"}, "encrypted_key": "..."}
  ],
  "ciphertext": "..."
}

Why: Standard RFC format, multiple recipients supported natively

Use Cases

Financial Services

Scenario: Wire transfer data
Requirement: multi-year retention, regulatory compliance
Solution: COMPOSITE_KEM_COMBINE (X25519 + ML-KEM-768)
Benefit: Quantum-safe transactions, the hybrid approach the GSA PQC Buyer's Guide lists

Healthcare

Scenario: Electronic health records
Requirement: decades-long record retention (state medical-record laws), HIPAA security rule
Solution: COMPOSITE_SIGNATURE (Ed25519 + ML-DSA-65)
Benefit: Long-term signature validity, crypto-agility

Government

Scenario: Classified document encryption
Requirement: Agency PQC transition plan
Solution: COMPOSITE_KEM_COMBINE (P-384 + ML-KEM-1024)
Benefit: a hybrid classical + post-quantum key the agency's transition plan can reference (classified use needs the agency's own accreditation; the platform holds none)

Key Selling Points

For CISOs

Message: "Quantum-proof your data WITHOUT disrupting operations"

Proof Points:

  • ✅ No application code changes after the one-time integration
  • ✅ Same API, enhanced security
  • ✅ Gradual migration (SIMPLE→COMPOSITE)
  • ✅ Full audit trail

For CTOs

Message: "Future-proof architecture, standards-based"

Proof Points:

  • ✅ Aligned with NIST CSWP 39
  • ✅ RFC 7516/7515 formats
  • ✅ Extensible design
  • ✅ Performance measured in the proof of concept, on the prospect's hardware

For Procurement

Message: "Standards-aligned capabilities"

Proof Points:

  • ✅ Aligned with the GSA PQC Buyer's Guide
  • ✅ AND-decrypt per NIST SP 800-227 §4.6
  • ✅ Production-ready (not beta)
  • ✅ Comprehensive documentation

Objection Handling

"Quantum computers are 10+ years away"

Response: "Harvest-now-decrypt-later attacks happen TODAY. Data harvested now will be decrypted later. Protect long-lived data NOW."

Supporting Data: NIST IR 8547 ipd proposes disallowing quantum-vulnerable public-key algorithms after 2035; data encrypted today may still be valuable then

"Too expensive / complex"

Response: "No application code changes after integration. Two key establishments per operation buy protection that holds as long as either algorithm holds."

Supporting Data: the illustrative cost model*; measure the overhead in the proof of concept

"PQC algorithms may have vulnerabilities"

Response: "Exactly why we use HYBRID. If PQC breaks, classical protects. If classical breaks (quantum), PQC protects."

Supporting Data: Defense-in-depth, min(classical, PQC) security

"We'll wait for competitors"

Response: "Federal mandates are already active, and composite keys are available today."

Supporting Data: hybrid key establishment is what BSI and ANSSI recommend for the transition

Marketing Campaign Ideas

Campaign 1: "Quantum Ready NOW"

Theme: Don't wait for quantum computers to arrive
Channels: Federal procurement, InfoSec conferences
CTA: "Get quantum protection aligned with the GSA PQC Buyer's Guide today"

Campaign 2: "The Harvest-Now-Decrypt-Later Threat"

Theme: Education on harvest now, decrypt later
Channels: Webinars, white papers, technical blogs
CTA: "Calculate your harvest-now-decrypt-later exposure"

Campaign 3: "Zero Disruption Quantum"

Theme: Quantum protection without re-architecture
Channels: CTO roundtables, technical demos
CTA: "See quantum protection deploy in 5 minutes"

Sales Playbook

Discovery Questions

  1. "What's your data retention period?" (>5 years → composite)
  2. "Do you bid on federal contracts?" (yes → GSA PQC Buyer's Guide alignment)
  3. "How sensitive is your data to future exposure?" (high → harvest-now-decrypt-later threat)
  4. "What's your quantum readiness plan?" (none → we provide solution)

Demo Script

5-Minute Demo: 1. Generate composite key (1 min) 2. Encrypt data, show JWE General JSON (2 min) 3. Explain AND-decrypt protection (1 min) 4. Show the NIST CSWP 39 and GSA alignment pages (1 min)

Impact: "That's it. Quantum protection deployed."

Proof of Concept

30-Day POC:

  • Week 1: Deploy ANKASecure
  • Week 2: Generate composite keys, encrypt sample data
  • Week 3: Performance testing
  • Week 4: Compliance review, decision

Success Criteria:

  • ✅ GSA PQC Buyer's Guide considerations reviewed against the alignment page
  • ✅ Performance acceptable
  • ✅ Integration successful

Competitive Battle Card

When Competing Against AWS KMS

Their Strength: Cloud-native, easy integration
Their Position: a managed cloud service; check its current algorithm list (AWS KMS added ML-DSA signing on 13 June 2025)

Our Counter:

  • "Every composite decrypt requires both components (AND-decrypt)"
  • "Standard JOSE formats"
  • "On-premise option available"

When Competing Against "Do Nothing"

Their Position: "We'll implement when needed"
Their Risk: harvest-now-decrypt-later attacks happening NOW

Our Counter:

  • "Data harvested today, decrypted once a quantum computer can"
  • "Federal mandates already active"
  • "Zero disruption deployment"

Conclusion

Composite Hybrid Keys give ANKASecure these quantum-resistant capabilities:

  • ✅ AND-decrypt implementation available today
  • ✅ Alignment with the GSA PQC Buyer's Guide

Recommendation: Prioritise federal-sector go-to-market with current production capabilities

Document Version: 1.0
Last Updated: December 2025
Prepared by: ANKATech Marketing Team

* restricted content — see higher-tier documentation