Retail & ecommerce | Modelled case study
Find cryptography that actually touches a retailer's card-data environment
Which terminals, gateways, token services, applications, and vendors are inside or connected to the cryptographic scope?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Retail CISO · Payments · PCI Programme functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A retailer or marketplace connects stores, payment terminals, ecommerce services, loyalty data, seller applications, processors, and third-party software vendors.
What is at stake
A shared credential or untrusted update can cross merchants, stores, customer records, and payment scope while directly affecting revenue and customer access.
Situation
Network diagrams and SAQs miss keys and certificates in integrations, support tools, batch settlement, ecommerce plugins, and backup.
Event that forces action
PCI assessment, payment-platform change, acquisition, or cryptographic migration.
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.
payment terminals
store and ecommerce gateways
token and processor services
card-data connected vendors
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
Network diagrams and SAQs miss keys and certificates in integrations, support tools, batch settlement, ecommerce plugins, and backup.
Frame the decision the owners must make
Which terminals, gateways, token services, applications, and vendors are inside or connected to the cryptographic scope?
Apply QNSI to the controlled boundary
Use QNSI inventory to associate algorithms, keys, endpoints, owners, vendors, and observed data paths with the CDE.
Leave the team with a concrete result
A card-data cryptography register with scope rationale, unsupported dependencies, key owners, and evidence status.
Prove the result in the organisation's environment
The merchant and assessor determine PCI scope, segmentation, compensating controls, key ceremonies, and compliance.
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
A card-data cryptography register with scope rationale, unsupported dependencies, key owners, and evidence status.
Independent validation boundary
The merchant and assessor determine PCI scope, segmentation, compensating controls, key ceremonies, and compliance.
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.