Banking & payments | Modelled case study
Evidence post-quantum signing for cardholder-data paths
How do we evidence post-quantum signing and integrity for cardholder-data paths under PCI DSS 4.0.1?
Reviewed as of 2026-10-26 · primary scenario
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Payments Security Lead · QSA Liaison · Platform Engineering functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A regulated bank operates real-time and batch payment services across internal platforms, clearing schemes, processors, HSMs, fraud controls, and external counterparties.
What is at stake
A cryptographic change must preserve authorization, settlement finality, scheme interoperability, evidence retention, and uninterrupted customer access.
Situation
PCI DSS 4.0.1 expects cryptographic agility and documented key management, and assessors increasingly ask about PQC posture for future-dated obligations.
Event that forces action
PCI DSS 4.0.1 assessment cycles and acquiring-bank PQC questionnaires.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
cardholder-data-path signing services
algorithm inventory and policy history
audit chain evidence
transition rehearsal environment
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
PCI DSS 4.0.1 expects cryptographic agility and documented key management, and assessors increasingly ask about PQC posture for future-dated obligations.
Frame the decision the owners must make
How do we evidence post-quantum signing and integrity for cardholder-data paths under PCI DSS 4.0.1?
Apply QNSI to the controlled boundary
Record cardholder-path signing operations with policy-enforced algorithms, produce audit-chain evidence and rehearse algorithm transitions.
Leave the team with a concrete result
An assessor-ready evidence pack: algorithm inventory, signing records, policy history and transition plan.
Prove the result in the organisation's environment
The QSA validates control mapping; payments engineering verifies no CHD-path latency or scheme-rule regression.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
An assessor-ready evidence pack: algorithm inventory, signing records, policy history and transition plan.
Independent validation boundary
The QSA validates control mapping; payments engineering verifies no CHD-path latency or scheme-rule regression.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.