Latest feature: Compare your cloud architecture against known frameworks such as NIS and SOC2.Compare your cloud against NIS and SOC2.

Book a demo
AKRIBOS AI
ProductComplianceEngineersSecurityFAQ
Sign InTry AKRIBOSTry AKRIBOS
Home/Compliance/PCI DSS v4

PCI DSS v4

Requirements for every environment that stores, processes or transmits cardholder data.

Updated 13 October 2026

Version 4 of the Payment Card Industry Data Security Standard keeps the twelve requirements, among them network security controls, secure configurations, protection of data at rest and in transit, strict access control with MFA, and logging of all access to cardholder data.

Version 4.0 became mandatory on 31 March 2024 and its future-dated requirements on 31 March 2025, so every assessment now runs against v4.0.1. Beyond the twelve requirements, v4 lets you meet controls through a customised approach, provided you can show it meets the objective, which makes continuous evidence more valuable than ever.

Official text: PCI DSS at the PCI Security Standards Council.

Who needs it

Any organisation that stores, processes or transmits cardholder data, and the service providers that could affect its security: merchants, payment facilitators, processors, issuers and SaaS platforms with payment flows. Assessment is annual, by a Qualified Security Assessor for larger entities or by self-assessment questionnaire for smaller ones.

Scope is everything

PCI DSS applies to the cardholder data environment and every system that can affect it. In the cloud, scope is defined by network boundaries and access paths: a flat network or a role that can reach the CDE from elsewhere pulls those systems into scope. Reducing scope through segmentation is the single biggest lever, and it has to be verified, not assumed.

Configuration requirements, continuously

Requirements 1, 2, 3, 4, 7, 8 and 10 are largely configuration: network controls, secure settings and no vendor defaults, protection of stored data, encryption in transit, least-privilege access, strong authentication with MFA, and logging of all access. Requirement 11 adds regular testing. v4 expects these to operate as business as usual, with evidence between assessments.

What PCI DSS asks of your cloud

The control areas that map onto infrastructure configuration in AWS, Google Cloud and Azure.

Req. 1 · Network security controls

Rules that restrict traffic between trusted and untrusted networks, and no direct access to systems holding account data from the internet.

Req. 2 · Secure configurations

No vendor defaults, hardened configuration standards for every system component, and encrypted non-console administrative access.

Req. 3 and 4 · Stored and transmitted account data

Primary account numbers unreadable wherever stored, strong cryptography in transit, and managed keys.

Req. 7 and 8 · Access and authentication

Access by business need to know, least privilege, unique IDs, strong authentication and MFA for all access into the cardholder data environment.

Req. 10 · Logging and monitoring

Audit logs for all access to system components and cardholder data, protected from modification, reviewed daily and retained for twelve months.

Req. 11 · Testing

Vulnerability scans at least quarterly and after significant change, penetration testing, and detection of unauthorised changes.

How AKRIBOS checks PCI DSS

Mapped to your resources

Every PCI DSS control is evaluated against the actual accounts, roles, networks and storage in your estate, with the setting behind each result.

Findings come with the fix

A failing control is shown with the exact change as CLI commands or Terraform. You review and approve; nothing is applied on its own.

Evidence over time

Scheduled reviews and a full audit trail give you a dated record of each control for the whole audit period, not just the day of the audit.

Common issues under PCI DSS

Misconfigurations that fail PCI DSS controls, with the control reference for each.

Storage bucket open to the internet

Critical

Object storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.Req. 1.3 and 1.4 (no direct access from untrusted networks), Req. 7.2 (need to know).

Read more

Root or owner account without MFA

Critical

The most privileged identity in the account protected by a password alone.Req. 8.4 (MFA for administrative access and all access into the CDE).

Read more

Database reachable from the internet

Critical

A managed database with a public address and a firewall that lets the world in.Req. 1.4.4 (systems storing account data not directly accessible from untrusted networks).

Read more

Snapshots or machine images shared publicly

Critical

Disk snapshots, database snapshots or machine images that anyone with a cloud account can copy.Req. 3 (stored account data protected), 7.2 (need to know).

Read more

Over-permissive IAM policies

High

Identities, often service accounts, that can do anything in the account because a wildcard or a basic role was easier than a scoped policy.Req. 7.2 (least privilege), 7.3 (access control system).

Read more

SSH or RDP open to 0.0.0.0/0

High

Management ports reachable from any address on the internet.Req. 1.3 and 1.4 (traffic between trusted and untrusted networks), 2.2.7 (encrypted administrative access).

Read more

Audit logging incomplete

High

Gaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.Req. 10.2 (audit logs for all access), 10.3 (logs protected), 10.5 (retention).

Read more

Long-lived or unused credentials

High

Access keys, service account keys and client secrets that never rotate and are no longer needed.Req. 8.2.6 (inactive accounts removed), 8.3.9 and 8.6.3 (credential rotation).

Read more

Instance metadata without session tokens

High

Compute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.Req. 2.2 (secure configuration), 6.3 (vulnerabilities addressed).

Read more

Trust policies open to any account

High

Roles or bindings that let identities outside your organisation assume access, often for a vendor integration that was set up too generously.Req. 7.2 (least privilege), 8.6 (system and application accounts), 12.8 (third-party service providers).

Read more

Data at rest without the encryption you intended

Medium

Volumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.Req. 3.5 (stored PAN unreadable), 3.6 and 3.7 (key management).

Read more

Transport encryption not enforced

Medium

Endpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.Req. 4.2.1 (strong cryptography in transit), 2.2.7 (encrypted non-console administrative access).

Read more

Network flow logs off

Medium

No record of which addresses talked to which, so traffic to and from a compromised host cannot be reconstructed.Req. 10.2 (audit logs) and 11.5 (intrusion detection).

Read more

Default network with permissive rules

Medium

Workloads running in the cloud-created default network, which ships with rules nobody would write deliberately.Req. 1.2 (network security controls configured), 2.2 (no vendor defaults).

Read more

PCI DSS questions

Which systems are in PCI scope in the cloud?

Anything that stores, processes or transmits cardholder data, anything on the same network segment, and anything that can affect their security, such as identity providers and management hosts. Verified segmentation keeps the rest out.

Does PCI DSS require MFA everywhere?

v4 requires MFA for all access into the cardholder data environment and for all administrative access, not just remote access. Privileged cloud identities without MFA are a direct failure.

How long must logs be kept?

Requirement 10 asks for at least twelve months of audit log history, with the most recent three months immediately available for analysis.

Can a cloud review replace my QSA assessment?

No. The assessment is performed by your QSA or through your SAQ. A continuous review gives you and your assessor configuration evidence for the technical requirements, and catches drift between assessments.

Other frameworks

CIS Benchmarks

The baseline configuration standard for AWS, Google Cloud and Azure.

Read more

SOC 2

Evidence that your cloud controls work, not just that they exist.

Read more

ISO/IEC 27001

The international standard for an information security management system, applied to your cloud.

Read more

DORA

The EU Digital Operational Resilience Act, applied to the cloud behind your financial services.

Read more

NIS2

EU-wide cyber risk-management obligations for essential and important entities.

Read more

NIST CSF 2.0

The US framework of outcomes: Govern, Identify, Protect, Detect, Respond, Recover.

Read more

BSI C5

Germany's cloud computing compliance criteria catalogue.

Read more

DNB Good Practice Information Security

What De Nederlandsche Bank expects of the financial institutions it supervises.

Read more
All frameworks

Attackers don't wait for your next audit. Neither does AKRIBOS.

Connect AWS, Google Cloud or Azure and get your first review today.

Run your first reviewRun your first review
Cinematic desert landscape at dusk with a lone silhouette standing before a warm amber glow, surrounded by dark rolling hills and a deep blue sky.
AKRIBOS

The AI agent that reviews and hardens your cloud, right from your terminal or our dashboard.

Navigation

How It WorksAttack PathsContinuous ReviewsComplianceCommon Cloud IssuesFor EngineersSecurityFAQ

Information

ContactPrivacy PolicyTerms of ServiceData Processing AgreementResponsible Disclosure

Socials

LinkedIn

© 2026 AKRIBOS AI B.V. All rights reserved.

AKRIBOS is a trade name of AKRIBOS AI B.V., registered with the Netherlands Chamber of Commerce (KvK) under number 83548335, Amsterdam, The Netherlands.