PCI DSS

PCI DSS v4.0.1 evidence for Azure

If you store, process or transmit cardholder data in Azure, many PCI DSS requirements come down to configuration. Equalis OpsReg checks them with 110 rules, every scan, between two assessments, for merchants and payment businesses in the EU and the United Kingdom.

110 of the 437 rules belong to PCI DSS. Both plans include all five frameworks.

What the text asks of your Azure environment

Requirement 1 covers network security controls, requirement 3 the protection of stored account data and requirement 4 strong cryptography to protect cardholder data during transmission over open, public networks.

Requirements 7 and 8 restrict access to system components and cardholder data by business need to know and require users to be identified and authenticated.

Requirement 10 asks for logging and monitoring of all access. Under 10.5.1, audit log history must be kept for at least 12 months, with the most recent three months immediately available. The rule shown on our evidence page checks that the workspace keeps at least 12 months of log history.

What Equalis OpsReg checks

110 rules, applied to every connected subscription on every scan. The areas below are the main ones.

Network security controls

Firewall rules, public endpoints and segmentation (requirement 1).

Stored account data

Encryption-at-rest and key-management settings (requirement 3). Disk- or partition-level encryption alone does not meet 3.5.1.2 for PAN on non-removable media.

Encryption in transit

TLS versions and HTTPS enforcement (requirement 4).

Access

Role assignments and privileged access (requirements 7 and 8).

Audit logs

Diagnostic settings and the 12-month retention of 10.5.1 (requirement 10).

Evidence for your QSA

Exports per subscription, which support CDE scoping when the CDE is isolated in dedicated subscriptions; connected or security-impacting systems elsewhere remain in scope.

What remains your responsibility

Equalis OpsReg evaluates technical configuration in Azure. The following obligations are organisational and are not scored by the platform.

  • Defining the scope of the cardholder data environment
  • Quarterly ASV scans and penetration tests at least once a year (requirement 11)
  • Security policies and the targeted risk analyses (requirement 12)
  • Application security and code review (requirement 6)
  • The Report on Compliance (ROC) or self-assessment questionnaire (SAQ), with the Attestation of Compliance (AOC) signed by you and, where involved, your QSA or ISA

Key facts

Standard
PCI DSS v4.0.1, published by the PCI Security Standards Council
Current status
v4.0 retired at the end of 2024; requirements that were future-dated became mandatory on 31 March 2025
Who it applies to
Any entity that stores, processes or transmits cardholder data or sensitive authentication data, or can affect their security
Assessment
By a Qualified Security Assessor (QSA), an Internal Security Assessor (ISA) or a self-assessment questionnaire, as required by your acquirer or the payment brands
Enforcement
Contractual: enforcement and any non-compliance penalties are set by the payment brands and applied through acquiring banks, not by the PCI SSC

Contact

Demonstrations are run in French or English, in thirty minutes, by the people who build the platform.

EqualisTech OpsReg Limited
The Black Church, St. Mary's Place
Dublin 7, D07 P4AX, Ireland
contact@equalistech.com
Request a demonstration (opens in a new tab)