PCI DSS v4.0.1: the requirements that became mandatory on 1 April 2025, seen from Azure
v4.0 was retired on 31 December 2024; the future-dated requirements of v4.x became mandatory after 31 March 2025. About a third of them depend on cloud configuration.
PCI DSS v4.0.1, published by the PCI Security Standards Council in June 2024, is the current version of the standard. v4.0 was retired on 31 December 2024. The requirements marked as future-dated in v4.x were best practice until 31 March 2025 and are mandatory in every assessment since. There is no further transition date.
Requirements with a configuration side on Azure
- Requirement 1 — network security controls
- Network security groups, firewall rules, public endpoints, segmentation between the cardholder data environment and other networks. Observable as resource properties.
- Requirement 3 — stored account data
- Encryption at rest of databases, storage and disks, key management in Azure Key Vault, key rotation. Observable; the presence of account data itself is not.
- Requirement 4 — encryption in transit
- Minimum TLS versions, HTTPS-only settings, certificate configuration on public services. Observable.
- Requirements 7 and 8 — access control and authentication
- Role assignments, privileged roles, multi-factor enforcement in Microsoft Entra ID. Partly observable.
- Requirement 10 — logging and monitoring
- Diagnostic settings, log retention of at least twelve months with three months immediately available (10.5.1), time synchronisation, alerting. Observable.
- Requirements 6, 9, 11 and 12
- Secure development, physical security, testing and policies. Organisational or procedural; not observable in configuration.
What an assessor expects
A Qualified Security Assessor samples systems and asks for evidence that each applicable requirement was in place during the assessment period, not only on the day of the visit. Point-in-time screenshots satisfy the day; dated, repeated configuration records satisfy the period. Equalis OpsReg records 110 rules mapped to the requirements above on every scan, scoped to one Azure subscription, so the evidence boundary matches the assessment boundary. The PCI DSS page lists the areas.
Shared responsibility
Microsoft Azure holds its own PCI DSS attestation of compliance for the platform; its responsibility matrix states which requirements are Microsoft's, which are the customer's, and which are shared. Configuration evidence covers the customer and shared rows only.
Reviewed monthly; the date above is the last review.
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)