mlsanityData to 14 Oct 2026

QML-PipeGuard: Drift-Aware Behavioral Fingerprinting for Quantum Machine Learning Pipeline Integrity

arXiv 2605.25066 ↗First posted 24 May 2026quant-ph cs.CR cs.LGcited by 0

Not on the map. Why?

Abstract (arXiv)

Quantum machine learning (QML) is moving from research prototypes to deployed cloud services. As QML enters regulated industries, the integrity of the quantum stage becomes a practical concern on two fronts: noisy hardware drifts at the channel level between recalibrations, and an adversary with control over the execution environment can substitute the declared quantum channel with a behaviorally similar but mathematically distinct one. Neither concern is covered by existing QML verification work on pulse-level noise, input drift, input-perturbation robustness, or device identity. We introduce QML-PipeGuard, a contract-based framework addressing both concerns under a single mathematical machinery. It characterizes a QML pipeline at runtime by its behavioral fingerprint, the vector of observable expectation values under a tomographically structured measurement family, and operates in two modes: drift-aware monitoring that absorbs benign calibration changes within a calibrated tolerance, and adversarial detection that catches channel substitution as a violation of an informationally complete observable contract. The framework contributes a pipeline-composition treatment of the encoder-ansatz-measurement channel with a QML-specific threat model (tight frame-bound C=sqrt(3) for the single-qubit Pauli family), a finite-shot sample-complexity bound, and a tolerance decomposition separating adversarial and natural-drift contributions. We validate the framework end-to-end on a two-qubit QSVM pipeline on the IBM Heron r2 processor (ibm_fez), with a sample-complexity validation on a noise-matched simulator. The prescribed measurement budget (about 1.4e4 shots) fits in a single batched job, the sneaky channel is detected with a wide safety margin while evading the weak contract, and the typical hardware drift sits within tolerance.

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 5 of its 45 references that are in the map. First posted on arXiv 24 May 2026.

Builds on

5 of 45 references.

References · 5

  1. 2025"Show Me You Comply... Without Showing Me Anything": Zero-Knowledge Software Auditing for AI-Enabled Systemscited by 6
  2. 2025ExpProof : Operationalizing Explanations for Confidential Models with ZKPscited by 2
  3. 2025Refinement orders for quantum programscited by 1
  4. 2025Trustworthy Quantum Machine Learning: A Roadmap for Reliability, Robustness, and Security in the NISQ Eracited by 1
  5. 2026QCIVET: A Quantum--Classical Pipeline Integrity Framework with Contract-Based Subtype Verification and Hash-Chained Audit Tracescited by 1

Built on by

Not cited yet.