Sign in
Menu
Sign up
Docs

PCI DSS v4.0

ActiveCore framework

Best for: The PCI DSS standard applies to any organization, no matter what size, that accepts, transmits, or stores cardholder data. Its scope includes all systems, networks, and applications that process, store, or transmit cardholder data, and systems used to secure and log access to them.

Mandatory?Mandatory for any entity processing card data
Who validates?QSA (Level 1 merchants/SPs); SAQ self-assessment (Levels 2–4)
RenewalAnnual
ScopeCardholder data environment (CDE) and connected systems
Governing bodyPCI Security Standards Council, PCI DSS v4.0. Official source

Controls by category

52 controls are Mapped to PCI DSS v4.0.

1.2.5: Network security controls (NSCs) are configured and maintained.

1.2.8: Network security controls (NSCs) are configured and maintained.

1.3.1: Network access to and from the cardholder data environment is restricted.

1.3.2: Network access to and from the cardholder data environment is restricted.

1.4.2: Network connections between trusted and untrusted networks are controlled.

1.4.5: Network connections between trusted and untrusted networks are controlled.

1.5.1: Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated.

10.2.1.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.2.1.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.2.1.3: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.2.1.4: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.2.1.5: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.2.1.6: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.2.1.7: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.2.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.2.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.

10.3.1: Audit logs are protected from destruction and unauthorized modifications.

10.3.2: Audit logs are protected from destruction and unauthorized modifications.

10.3.3: Audit logs are protected from destruction and unauthorized modifications.

10.3.4: Audit logs are protected from destruction and unauthorized modifications.

10.4.1.1: Audit logs are reviewed to identify anomalies or suspicious activity.

10.4.2: Audit logs are reviewed to identify anomalies or suspicious activity.

10.5.1: Audit log history is retained and available for analysis.

10.6.3: Time-synchronization mechanisms support consistent time settings across all systems.

10.7.1: Failures of critical security control systems are detected, reported, and responded to promptly.

11.3.1.2: External and internal vulnerabilities are regularly identified, prioritized, and addressed.

11.3.1.3: External and internal vulnerabilities are regularly identified, prioritized, and addressed.

11.3.1: External and internal vulnerabilities are regularly identified, prioritized, and addressed.

11.5.2: Network intrusions and unexpected file changes are detected and responded to.

11.6.1: Unauthorized changes on payment pages are detected and responded to.

12.10.5: Suspected and confirmed security incidents that could impact the CDE are responded to immediately.

2.2.5: System components are configured and managed securely.

2.2.7: System components are configured and managed securely.

3.5.1.1: Primary account number (PAN) is secured wherever it is stored.

3.5.1.3: Primary account number (PAN) is secured wherever it is stored.

3.5.1: Primary account number (PAN) is secured wherever it is stored.

3.6.1.2: Cryptographic keys used to protect stored account data are secured.

3.6.1.3: Cryptographic keys used to protect stored account data are secured.

3.6.1.4: Cryptographic keys used to protect stored account data are secured.

3.6.1: Cryptographic keys used to protect stored account data are secured.

3.7.1: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.

3.7.2: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.

3.7.4: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.

3.7.5: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.

3.7.6: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.

3.7.7: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.

4.2.1.1: PAN is protected with strong cryptography during transmission.

4.2.1: PAN is protected with strong cryptography during transmission.

5.3.4: Anti-malware mechanisms and processes are active, maintained, and monitored.

7.2.1: Access to system components and data is appropriately defined and assigned.

7.2.2: Access to system components and data is appropriately defined and assigned.

7.2.3: Access to system components and data is appropriately defined and assigned.

7.2.5.1: Access to system components and data is appropriately defined and assigned.

7.2.5: Access to system components and data is appropriately defined and assigned.

7.2.6: Access to system components and data is appropriately defined and assigned.

7.3.1: Access to system components and data is managed via an access control system(s).

7.3.2: Access to system components and data is managed via an access control system(s).

7.3.3: Access to system components and data is managed via an access control system(s).

8.3.10.1: Strong authentication for users and administrators is established and managed.

8.3.2: Strong authentication for users and administrators is established and managed.

8.3.4: Strong authentication for users and administrators is established and managed.

8.3.5: Strong authentication for users and administrators is established and managed.

8.3.7: Strong authentication for users and administrators is established and managed.

8.3.9: Strong authentication for users and administrators is established and managed.

8.6.3: Use of application and system accounts and associated authentication factors is strictly managed.

A1.1.2: Multi-tenant service providers protect and separate all customer environments and data.

A1.1.3: Multi-tenant service providers protect and separate all customer environments and data.

A1.2.1: Multi-tenant service providers facilitate logging and incident response for all customers.

A1.2.3: Multi-tenant service providers facilitate logging and incident response for all customers.

A3.3.1: PCI DSS is incorporated into business-as-usual (BAU) activities.

A3.4.1: Logical access to the cardholder data environment is controlled and managed.

A3.5.1: Suspicious events are identified and responded to.

FrameworkControl overlapNote
CIS GCP Benchmark v2.0.0High 96%
BSI C5:2025High 94%
CIS GCP Benchmark v3.0.0High 94%

Frequently asked questions

Who created PCI DSS and what is its purpose?

The PCI Security Standards Council created the Payment Card Industry Data Security Standards. Visa, MasterCard, American Express, Discover and JCB established the Council as a separate organization to define practices that protect cardholder data.

What systems fall within the scope of PCI DSS?

The scope covers all systems, networks, and applications that process, store, or transmit cardholder data. It also covers systems that are used to secure and log access to the systems in scope.

Who is responsible for PCI DSS compliance of applications running on Google Cloud?

Google Cloud services provide an infrastructure on which customers may build services or applications that handle cardholder data. Customers are still responsible for ensuring that their applications are PCI DSS compliant.

How often is Google Cloud audited against PCI DSS, and where can reports be requested?

Google Cloud undergoes at least an annual third-party audit to certify individual products against the PCI DSS. PCI DSS reports may be requested via the Compliance Reports Manager for Google Cloud.

On this page

Controls by category1.2.5: Network security controls (NSCs) are configured and maintained.1.2.8: Network security controls (NSCs) are configured and maintained.1.3.1: Network access to and from the cardholder data environment is restricted.1.3.2: Network access to and from the cardholder data environment is restricted.1.4.2: Network connections between trusted and untrusted networks are controlled.1.4.5: Network connections between trusted and untrusted networks are controlled.1.5.1: Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated.10.2.1.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.10.2.1.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.10.2.1.3: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.10.2.1.4: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.10.2.1.5: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.10.2.1.6: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.10.2.1.7: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.10.2.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.10.2.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.10.3.1: Audit logs are protected from destruction and unauthorized modifications.10.3.2: Audit logs are protected from destruction and unauthorized modifications.10.3.3: Audit logs are protected from destruction and unauthorized modifications.10.3.4: Audit logs are protected from destruction and unauthorized modifications.10.4.1.1: Audit logs are reviewed to identify anomalies or suspicious activity.10.4.2: Audit logs are reviewed to identify anomalies or suspicious activity.10.5.1: Audit log history is retained and available for analysis.10.6.3: Time-synchronization mechanisms support consistent time settings across all systems.10.7.1: Failures of critical security control systems are detected, reported, and responded to promptly.11.3.1.2: External and internal vulnerabilities are regularly identified, prioritized, and addressed.11.3.1.3: External and internal vulnerabilities are regularly identified, prioritized, and addressed.11.3.1: External and internal vulnerabilities are regularly identified, prioritized, and addressed.11.5.2: Network intrusions and unexpected file changes are detected and responded to.11.6.1: Unauthorized changes on payment pages are detected and responded to.12.10.5: Suspected and confirmed security incidents that could impact the CDE are responded to immediately.2.2.5: System components are configured and managed securely.2.2.7: System components are configured and managed securely.3.5.1.1: Primary account number (PAN) is secured wherever it is stored.3.5.1.3: Primary account number (PAN) is secured wherever it is stored.3.5.1: Primary account number (PAN) is secured wherever it is stored.3.6.1.2: Cryptographic keys used to protect stored account data are secured.3.6.1.3: Cryptographic keys used to protect stored account data are secured.3.6.1.4: Cryptographic keys used to protect stored account data are secured.3.6.1: Cryptographic keys used to protect stored account data are secured.3.7.1: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.3.7.2: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.3.7.4: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.3.7.5: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.3.7.6: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.3.7.7: Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.4.2.1.1: PAN is protected with strong cryptography during transmission.4.2.1: PAN is protected with strong cryptography during transmission.5.3.4: Anti-malware mechanisms and processes are active, maintained, and monitored.7.2.1: Access to system components and data is appropriately defined and assigned.7.2.2: Access to system components and data is appropriately defined and assigned.7.2.3: Access to system components and data is appropriately defined and assigned.7.2.5.1: Access to system components and data is appropriately defined and assigned.7.2.5: Access to system components and data is appropriately defined and assigned.7.2.6: Access to system components and data is appropriately defined and assigned.7.3.1: Access to system components and data is managed via an access control system(s).7.3.2: Access to system components and data is managed via an access control system(s).7.3.3: Access to system components and data is managed via an access control system(s).8.2.1: User identification and related accounts for users and administrators are strictly managed throughout an accounts lifecycle.8.2.2: User identification and related accounts for users and administrators are strictly managed throughout an accounts lifecycle.8.2.5: User identification and related accounts for users and administrators are strictly managed throughout an accounts lifecycle.8.2.7: User identification and related accounts for users and administrators are strictly managed throughout an accounts lifecycle.8.2.8: User identification and related accounts for users and administrators are strictly managed throughout an accounts lifecycle.8.3.10.1: Strong authentication for users and administrators is established and managed.8.3.2: Strong authentication for users and administrators is established and managed.8.3.4: Strong authentication for users and administrators is established and managed.8.3.5: Strong authentication for users and administrators is established and managed.8.3.7: Strong authentication for users and administrators is established and managed.8.3.9: Strong authentication for users and administrators is established and managed.8.6.3: Use of application and system accounts and associated authentication factors is strictly managed.A1.1.2: Multi-tenant service providers protect and separate all customer environments and data.A1.1.3: Multi-tenant service providers protect and separate all customer environments and data.A1.2.1: Multi-tenant service providers facilitate logging and incident response for all customers.A1.2.3: Multi-tenant service providers facilitate logging and incident response for all customers.A3.3.1: PCI DSS is incorporated into business-as-usual (BAU) activities.A3.4.1: Logical access to the cardholder data environment is controlled and managed.A3.5.1: Suspicious events are identified and responded to.Related frameworksFrequently asked questions

Ask AI about this

Help improve this page