GDPR Denmark vs PCI DSS
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 15 of 20 topics. Each verdict names what it rests on; read the wording before relying on it.
- GDPR Denmark Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- PCI DSS Asks more on 0 topics Alone on 13 topics More detailed on 2 topics
| Topic | GDPR Denmark | PCI DSS | Verdict |
|---|---|---|---|
| Governance | |||
| Management accountability | GDPR Denmark: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Security policy | GDPR Denmark: – | PCI DSS: 2 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Awareness and training | GDPR Denmark: – | PCI DSS: 2 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Risk management | |||
| Risk assessment | GDPR Denmark: 1 | PCI DSS: 1 | Both cover itread the wording below |
| Asset management | GDPR Denmark: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Protection | |||
| Access control | GDPR Denmark: – | PCI DSS: 4 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Authentication | GDPR Denmark: – | PCI DSS: 5 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Cryptography and encryption | GDPR Denmark: 1 | PCI DSS: 3 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Data security | GDPR Denmark: 2 | PCI DSS: 4 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Network security | GDPR Denmark: – | PCI DSS: 7 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Secure communications | GDPR Denmark: – | PCI DSS: 2 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Secure acquisition and development | GDPR Denmark: – | PCI DSS: 3 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Configuration, change and patch management | GDPR Denmark: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Vulnerability handling | GDPR Denmark: – | PCI DSS: 4 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Human resources security | GDPR Denmark: 1 | PCI DSS: 1 | Both cover itread the wording below |
| Physical and environmental security | GDPR Denmark: – | PCI DSS: 5 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Detection and response | |||
| Monitoring and detection | GDPR Denmark: – | PCI DSS: 12 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Incident handling | GDPR Denmark: 1 | PCI DSS: 1 | Both cover itread the wording below |
| Continuity and resilience | |||
| Security testing | GDPR Denmark: 1 | PCI DSS: 2 | Both cover itread the wording below |
| Third parties and supply chain | |||
| Supplier and third-party risk | GDPR Denmark: 2 | PCI DSS: 2 | Both cover itread the wording below |
What This Covers
The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.
Key Numbers
Deadline
GDPR Denmark: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
PCI DSS: Not in the acts covered
Threshold
GDPR Denmark: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)
PCI DSS: Not in the acts covered
Goes to
GDPR Denmark: Controller (Processors); Data subjects (Controllers)
PCI DSS: Not in the acts covered
Evidence to keep
GDPR Denmark: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
PCI DSS: Not in the acts covered
Incident reports go to
GDPR Denmark: Competent supervisory authority (Controllers)
PCI DSS: Not in the acts covered
First notice of an incident
GDPR Denmark: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)
PCI DSS: Not in the acts covered
Intermediate report
GDPR Denmark: In phases, without undue further delay (Controllers)
PCI DSS: Not in the acts covered
External assessment or certification
GDPR Denmark: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
PCI DSS: Not in the acts covered
Review of the risk framework
GDPR Denmark: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
PCI DSS: Not in the acts covered
Testing of critical systems
GDPR Denmark: Regularly
PCI DSS: Not in the acts covered
Maximum fines
GDPR Denmark: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher
PCI DSS: Not in the acts covered
Governance
Management accountability
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4
Nothing in the acts covered.
PCI DSS compliance is managed
PCI DSSPayment Card Industry Data Security Standard compliance is managed.
Security policy
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1
Nothing in the acts covered.
A comprehensive information security policy that governs and provides direction for protection of the entity's information assets is known and current
A comprehensive information securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. policy that governs and provides direction for protection of the entity's information assets is known and current.
Acceptable use policies for end-user technologies are defined and implemented
Acceptable use policies for end-user technologies are defined and implemented.
Awareness and training
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3
Nothing in the acts covered.
Anti-phishing mechanisms protect users against phishing attacks
Anti-phishing mechanisms protect users against phishingAn attack that impersonates a trusted person or organisation through electronic communications, often an email or a fake website, to trick someone into revealing information such as passwords or bank details. The attacker uses apparent familiarity or credibility to persuade the person to respond. Training simulations practise recognising these deceptive requests. attacks.
Security awareness education is an ongoing activity
Security awareness education is an ongoing activity.
Risk management
Risk assessment
Both cover it read the wording below
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2
Assess security risk
When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.
GDPR, Article 32(2) · applies as in the Directive
Risks to the cardholder data environment are formally identified, evaluated, and managed
Risks to the cardholder data environmentThe system components, people and processes that store, process or transmit cardholder data or sensitive authentication data, plus components with unrestricted connectivity to them. Defining the CDE sets the scope of a PCI DSS assessment. are formally identified, evaluated, and managed.
Asset management
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13
Nothing in the acts covered.
PCI DSS scope is documented and validated
PCI DSSPayment Card Industry Data Security Standard scope is documented and validated.
Protection
Access control
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3
Nothing in the acts covered.
Processes and mechanisms for restricting access to system components and cardholder data by business need to know are defined and understood
Processes and mechanisms for restricting access to system components and cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. by business need to know are defined and understood.
Access to system components and data is appropriately defined and assigned
Access to system components and data is appropriately defined and assigned.
Access to system components and data is managed via an access control system(s)
Access to system components and data is managed via an access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. system(s).
User identification and related accounts for users and administrators are strictly managed throughout an account's lifecycle
User identification and related accounts for users and administrators are strictly managed throughout an account's lifecycle.
Authentication
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5
Nothing in the acts covered.
Processes and mechanisms for identifying users and authenticating access to system components are defined and understood
Processes and mechanisms for identifying users and authenticating access to system components are defined and understood.
Strong authentication for users and administrators is established and managed
Strong authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. for users and administrators is established and managed.
Multi-factor authentication (MFA) is implemented to secure access into the CDE
Multi-factor authenticationAuthentication through verification of at least two different types of factor: something a person knows, such as a password; something they have, such as a token; or something they are, such as a biometric. NIS2, PCI DSS, the NYDFS regulation and the FTC Safeguards Rule call for it. (MFA) is implemented to secure access into the CDECardholder Data Environment.
Multi-factor authentication (MFA) systems are configured to prevent misuse
Multi-factor authenticationAuthentication through verification of at least two different types of factor: something a person knows, such as a password; something they have, such as a token; or something they are, such as a biometric. NIS2, PCI DSS, the NYDFS regulation and the FTC Safeguards Rule call for it. (MFA) systems are configured to prevent misuse.
Use of application and system accounts and associated authentication factors is strictly managed
Use of application and system accounts and associated authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. factors is strictly managed.
Cryptography and encryption
PCI DSS more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24
Pseudonymisation and encryption
Apply pseudonymisation and encryption of personal data, as appropriate to the risk.
GDPR, Article 32(1)(a) · applies as in the Directive
Primary account number (PAN) is secured wherever it is stored
Primary account numberThe unique payment card number that identifies the card issuer and the cardholder account, used on credit, debit and prepaid cards. Under PCI DSS the full PAN is the minimum element of cardholder data, so where it is stored, processed or transmitted drives the scope of an assessment. (PAN) is secured wherever it is stored.
Cryptographic keys used to protect stored account data are secured
Cryptographic keys used to protect stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. are secured.
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
Where cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. is used to protect stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security., key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.
Data security
PCI DSS more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12
Integrity and confidentiality
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.
GDPR, Article 5(1)(f) · applies as in the Directive
Security of systems and services
Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.
GDPR, Article 32(1)(b) · applies as in the Directive
Processes and mechanisms for protecting stored account data are defined and understood
Processes and mechanisms for protecting stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. are defined and understood.
Storage of account data is kept to a minimum
Storage of account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. is kept to a minimum.
Sensitive authentication data (SAD) is not stored after authorization
Sensitive authentication dataSecurity-related information used to authenticate cardholders or authorise payment card transactions, such as card verification codes, full track data, PINs and PIN blocks. Together with cardholder data it makes up account data under PCI DSS. (SAD) is not stored after authorization.
Access to displays of full PAN and ability to copy PAN are restricted
Access to displays of full PANPrimary Account Number and ability to copy PANPrimary Account Number are restricted.
Network security
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22
Nothing in the acts covered.
Processes and mechanisms for installing and maintaining network security controls are defined and understood
Processes and mechanisms for installing and maintaining network security controls are defined and understood.
Network security controls (NSCs) are configured and maintained
Network security controls (NSCs) are configured and maintained.
Network access to and from the cardholder data environment is restricted
Network access to and from the cardholder data environmentThe system components, people and processes that store, process or transmit cardholder data or sensitive authentication data, plus components with unrestricted connectivity to them. Defining the CDE sets the scope of a PCI DSS assessment. is restricted.
Network connections between trusted and untrusted networks are controlled
Network connections between trusted and untrusted networks are controlled.
Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated
Risks to the CDECardholder Data Environment from computing devices that are able to connect to both untrusted networks and the CDECardholder Data Environment are mitigated.
Wireless environments are configured and managed securely
Wireless environments are configured and managed securely.
Wireless access points are identified and monitored, and unauthorized wireless access points are addressed
Wireless access points are identified and monitored, and unauthorized wireless access points are addressed.
Secure communications
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14
Nothing in the acts covered.
Processes and mechanisms for protecting cardholder data with strong cryptography during transmission over open, public networks are defined and understood
Processes and mechanisms for protecting cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. with strong cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. during transmission over open, public networks are defined and understood.
PAN is protected with strong cryptography during transmission
PANPrimary Account Number is protected with strong cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. during transmission.
Secure acquisition and development
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31
Nothing in the acts covered.
Processes and mechanisms for developing and maintaining secure systems and software are defined and understood
Processes and mechanisms for developing and maintaining secure systems and software are defined and understood.
Bespoke and custom software are developed securely
Bespoke and custom software are developed securely.
Public-facing web applications are protected against attacks
Public-facing web applications are protected against attacks.
Configuration, change and patch management
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.9, A.8.19, A.8.32
Nothing in the acts covered.
Changes to all system components are managed securely
Changes to all system components are managed securely.
Vulnerability handling
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8
Nothing in the acts covered.
Processes and mechanisms for applying secure configurations to all system components are defined and understood
Processes and mechanisms for applying secure configurations to all system components are defined and understood.
System components are configured and managed securely
System components are configured and managed securely.
Security vulnerabilities are identified and addressed
Security vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. are identified and addressed.
External and internal vulnerabilities are regularly identified, prioritized, and addressed
External and internal vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. are regularly identified, prioritized, and addressed.
Human resources security
Both cover it read the wording below
NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6
Staff act only on instructions
Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.
GDPR, Articles 29 and 32(4) · applies as in the Directive
Personnel are screened to reduce risks from insider threats
Personnel are screened to reduce risks from insider threats.
Physical and environmental security
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14
Nothing in the acts covered.
Processes and mechanisms for restricting physical access to cardholder data are defined and understood
Processes and mechanisms for restricting physical access to cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. are defined and understood.
Physical access controls manage entry into facilities and systems containing cardholder data
Physical access controls manage entry into facilities and systems containing cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment..
Physical access for personnel and visitors is authorized and managed
Physical access for personnel and visitors is authorized and managed.
Media with cardholder data is securely stored, accessed, distributed, and destroyed
Media with cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. is securely stored, accessed, distributed, and destroyed.
Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution
Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution.
Detection and response
Monitoring and detection
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16
Nothing in the acts covered.
Processes and mechanisms for protecting all systems and networks from malicious software are defined and understood
Processes and mechanisms for protecting all systems and networks from malicious softwareSoftware or firmware deliberately designed to harm a computer system or the information it holds. Malware can steal or destroy data, change information without permission, spy on activity or stop systems working. Examples include viruses, worms and spyware. Screening email or uploads for malware means looking for this harmful code before it can affect people or systems. are defined and understood.
Malicious software (malware) is prevented, or detected and addressed
Malicious software (malware) is prevented, or detected and addressed.
Anti-malware mechanisms and processes are active, maintained, and monitored
Anti-malwareSoftware designed to find malicious software, prevent it from infecting computers and, in some cases, remove an existing infection. Malicious software, or malware, includes programs such as viruses and spyware that can damage systems, steal information or disrupt operations. In security requirements, anti-malware refers to this protective capability rather than a particular product. mechanisms and processes are active, maintained, and monitored.
Processes and mechanisms for logging and monitoring all access to system components and cardholder data are defined and understood
Processes and mechanisms for logging and monitoring all access to system components and cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. are defined and understood.
Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events
Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
Audit logs are protected from destruction and unauthorized modifications
Audit logs are protected from destruction and unauthorized modifications.
Audit logs are reviewed to identify anomalies or suspicious activity
Audit logs are reviewed to identify anomalies or suspicious activity.
Audit log history is retained and available for analysis
Audit log history is retained and available for analysis.
Time-synchronization mechanisms support consistent time settings across all systems
Time-synchronization mechanisms support consistent time settings across all systems.
Failures of critical security control systems are detected, reported, and responded to promptly
Failures of critical security control systems are detected, reported, and responded to promptly.
Network intrusions and unexpected file changes are detected and responded to
Network intrusions and unexpected file changes are detected and responded to.
Unauthorized changes on payment pages are detected and responded to
Unauthorized changes on payment pages are detected and responded to.
Incident handling
Both cover it read the wording below
NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28
Document every breach
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.
GDPR, Article 33(5) · applies as in the Directive
Suspected and confirmed security incidents that could impact the CDE are responded to immediately
Suspected and confirmed security incidents that could impact the CDECardholder Data Environment are responded to immediately.
Continuity and resilience
Security testing
Both cover it read the wording below
NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34
Testing the measures
Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.
GDPR, Article 32(1)(d) · applies as in the Directive
Processes and mechanisms for regularly testing security of systems and networks are defined and understood
Processes and mechanisms for regularly testing security of systems and networks are defined and understood.
External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected
External and internal penetration testingA security assessment in which authorised testers simulate attacks on an application, system or network to find weaknesses that could actually be exploited. Testing takes place within agreed limits, such as the systems included and the techniques permitted. It can reveal how several weaknesses combine to give an attacker greater access, helping an organisation understand and correct the resulting exposure. is regularly performed, and exploitable vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and security weaknesses are corrected.
Third parties and supply chain
Supplier and third-party risk
Both cover it read the wording below
NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23
Use only processors with sufficient guarantees
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.
GDPR, Article 28(1) · applies as in the Directive
Sub-processors
Applies to: Processors
Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.
GDPR, Article 28(2) and (4) · applies as in the Directive
Risk to information assets associated with third-party service provider (TPSP) relationships is managed
Risk to information assets associated with third-party service provider (TPSP) relationships is managed.
Third-party service providers (TPSPs) support their customers' PCI DSS compliance
Third-party service providers (TPSPs) support their customers' PCI DSSPayment Card Industry Data Security Standard compliance.
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022. 16 topics where all apply the Directive as it is are not shown.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.