Compliance evidence for retail and e-commerce on Azure
If you take card payments, PCI DSS v4.0.1 applies, and its requirements on logging, retention, network security controls and access are explicit. The same customer data is also covered by GDPR.
The regulatory context
PCI DSS is contractual rather than statutory. Enforcement and any non-compliance penalties are set by the payment brands and applied through acquiring banks, not by the PCI Security Standards Council.
Between two annual assessments, configuration changes every day, while the configuration evidence is gathered once a year.
GDPR applies to the same customer data, with fines of up to €20 million or 4% of worldwide annual turnover.
What you receive
- 110 PCI DSS rules applied on every scan
- Log retention and monitoring checked against the actual Azure settings
- Network segmentation and public exposure, resource by resource
- Evidence grouped by subscription for your QSA
Limits of general-purpose tools
Point in time
The annual assessment model predates infrastructure that changes every day.
Prioritisation is not proof
A ranked risk list helps engineers. It does not tell a QSA what the log retention was on a given date.
Scope discipline
The cardholder data environment is defined by its boundary. When it is isolated in dedicated subscriptions, exports per subscription follow that boundary.
Framework coverage
All five frameworks are included on both plans.
| Framework | Rules | Relevance |
|---|---|---|
| PCI DSS | 110 | Primary |
| GDPR | 74 | Also evaluated |
| ISO/IEC 27001 | 90 | Also evaluated |
| NIS2 | 82 | Also evaluated |
| DORA | 81 | Also evaluated |
Contact
Demonstrations are run in French or English, in thirty minutes, by the people who build the platform.
The Black Church, St. Mary's Place
Dublin 7, D07 P4AX, Ireland
contact@equalistech.comRequest a demonstration (opens in a new tab)