Quantum-Network Security and Key-Management Operations

Quantum networks are not just faster or more exotic networks. They combine classical control channels, optical or microwave quantum channels, timing systems, key-management systems, trusted nodes, quantum memories, entanglement sources, and measurement stations. The security model depends on what is being transported: key material, entanglement, telemetry, calibration data, or application payloads.

ETSI's QKD work focuses on interoperability, safe implementation, common interfaces, and mitigating side channels and active attacks in quantum-communication deployments. [R182] At the same time, the NSA does not recommend QKD or quantum cryptography for securing National Security Systems unless identified limitations are overcome, which is a useful reminder that QKD is not a universal replacement for post-quantum cryptography or conventional key management. [R183]

Diagram loads as you read

Quantum-Network Security and Key-Management Operations · Figure 1

View diagram source

flowchart LR
    QuantumChannel[Quantum channel] --> Measurement[Measurement outcomes]
    Measurement --> Sifting[Sifting and parameter estimation]
    ClassicalChannel[Authenticated classical communication] --> Sifting
    Sifting --> Reconciliation[Information reconciliation and verification]
    Reconciliation --> Privacy[Privacy amplification]
    ClassicalChannel --> Reconciliation
    ClassicalChannel --> Privacy
    Privacy --> Accept{Security checks pass?}
    Accept -- yes --> KeyManager[Key manager]
    Accept -- no --> Abort[Abort and discard candidate key]
    KeyManager --> Application[Application encryption]

Network assets

Asset	Operational concern
quantum channel	loss, tamper evidence, fiber path, alignment
classical channel	authentication, integrity, replay resistance
key manager	key lifecycle, export policy, audit
trusted node	insider risk, custody, physical security
entanglement source	quality, scheduling, calibration
quantum memory	coherence window, storage errors, supported error correction, routing
timing system	synchronization, drift, spoofing
evidence logs	proof of key creation and consumption

Diagram loads as you read

Network assets · Figure 2

View diagram source

mindmap
  root((Quantum network assets))
    Quantum channel
    Classical channel
    Key manager
    Trusted node
    Entanglement source
    Quantum memory
    Timing system
    Evidence logs

Trust boundaries

Diagram loads as you read

Trust boundaries · Figure 3

View diagram source

flowchart TB
    SiteA[Site A] --> Node1[Trusted or repeater node]
    Node1 --> Node2[Intermediate node]
    Node2 --> SiteB[Site B]
    SiteA -. classical auth .-> SiteB
    Node1 --> Audit[Custody evidence]
    Node2 --> Audit

A network with trusted relay nodes inherits trust in each relay. A network with repeaters and entanglement swapping has different operational risks, but it still needs classical authentication, timing discipline, routing policy, and evidence.

Key-management lifecycle

Diagram loads as you read

Key-management lifecycle · Figure 4

View diagram source

stateDiagram-v2
    [*] --> Generated
    Generated --> Buffered
    Buffered --> Allocated
    Allocated --> Consumed
    Consumed --> Retired
    Buffered --> Expired
    Allocated --> Revoked

Key material should be treated as a governed inventory. The platform should know source, generation time, path, entropy claims, usage authorization, consuming application, retention policy for metadata, and destruction record.

QKD and PQC are different controls

Diagram loads as you read

QKD and PQC are different controls · Figure 5

View diagram source

flowchart LR
    Threat[Quantum-era cryptographic risk] --> PQC[PQC algorithms]
    Threat --> QKD[QKD link]
    PQC --> SoftwareMigration[Software and protocol migration]
    QKD --> PhysicalNetwork[Physical network deployment]
    SoftwareMigration --> Hybrid[Hybrid assurance posture]
    PhysicalNetwork --> Hybrid

PQC is a cryptographic migration problem. QKD is a physical network and key-distribution system problem. They can complement each other in some contexts, but they do not substitute for each other operationally.

Control plane for quantum networks

Recent quantum-network testbeds emphasize automation, centralized control, extensible control planes, and real-time software for quantum-network operations. The DOE's 2026 QUANT-NET highlight describes progress toward automating basic network operations in a testbed with a scalable quantum control plane. [R184]

Diagram loads as you read

Control plane for quantum networks · Figure 6

View diagram source

flowchart TB
    Request[Entanglement or key request] --> Policy[Network policy]
    Policy --> Scheduler[Path and time scheduler]
    Scheduler --> QuantumOps[Quantum operation]
    Scheduler --> ClassicalOps[Classical coordination]
    QuantumOps --> Quality[Quality estimate]
    ClassicalOps --> Evidence[Evidence record]
    Quality --> Evidence

Operational telemetry

Diagram loads as you read

Operational telemetry · Figure 7

View diagram source

flowchart LR
    Channel[Channel metrics] --> Monitor[Network monitor]
    Timing[Timing metrics] --> Monitor
    KeyRate[Key rate] --> Monitor
    QBER[Error rate] --> Monitor
    Monitor --> SLO[SLO evaluation]
    SLO --> Alert[Alert or reroute]

Minimum metrics include link availability, loss, key generation rate, quantum bit error rate, reconciliation failure rate, authentication failure rate, timing drift, key buffer level, and path custody status.

Incident response

Diagram loads as you read

Incident response · Figure 8

View diagram source

flowchart TB
    Alert[Network alert] --> Classify{Classify}
    Classify --> Loss[Loss or alignment]
    Classify --> Auth[Classical auth failure]
    Classify --> Custody[Trusted-node custody]
    Classify --> Key[Key-manager fault]
    Loss --> Repair[Repair or reroute]
    Auth --> Quarantine[Quarantine channel]
    Custody --> Freeze[Freeze key export]
    Key --> Reconcile[Reconcile inventory]

The most important operational rule is conservative key handling. When provenance, custody, authentication, or evidence is ambiguous, freeze export and preserve evidence.

Operational rule

A quantum network is not secure merely because it uses quantum effects. Security depends on authenticated classical control, implementation quality, custody, key lifecycle controls, telemetry, and honest limitation statements.

Diagram loads as you read

Operational rule · Figure 9

View diagram source

flowchart LR
    QuantumEffect[Quantum effect] --> Partial[Partial security property]
    Partial --> Implementation[Implementation controls]
    Implementation --> Operations[Operational controls]
    Operations --> Claim[Defensible security claim]

Additional technical sources: [R254], [R268], [R274].