> NIS2 vs Swift CSP side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# NIS2 vs Swift CSP

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[NIS2](https://grc.plus/regulation/nis2/)Essential and important entities

[Swift CSP](https://grc.plus/regulation/swift-customer-security-program-swift-csp/)Swift users, for their architecture type

## At a Glance

They differ on 27 of 32 topics. Each verdict names what it rests on; read the wording before relying on it.

- **NIS2** Asks more on 4 topics Alone on 17 topics More detailed on 0 topics
- **Swift CSP** Asks more on 0 topics Alone on 1 topic More detailed on 5 topics

| Topic | NIS2 | Swift CSP | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Management accountability | NIS2: 1 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Roles and independence | NIS2: 1 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Security policy | NIS2: 2 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Awareness and training | NIS2: 2 | Swift CSP: 1 | **Both cover it**read the wording below |
| Risk management |  |  |  |
| Risk management framework | NIS2: 3 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Risk assessment | NIS2: 2 | Swift CSP: 1 | **NIS2 asks more**binding, where the other is optional |
| Review, audit and improvement | NIS2: 3 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Asset management | NIS2: 2 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | NIS2: 2 | Swift CSP: 2 | **Both cover it**read the wording below |
| Authentication | NIS2: 2 | Swift CSP: 4 | **Swift CSP more detailed**more requirements on this, not necessarily stricter |
| Cryptography and encryption | NIS2: 1 | Swift CSP: 1 | **NIS2 asks more**binding, where the other is optional |
| Data security | NIS2: – | Swift CSP: 4 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Network security | NIS2: 1 | Swift CSP: 4 | **Swift CSP more detailed**more requirements on this, not necessarily stricter |
| Secure communications | NIS2: 1 | Swift CSP: 3 | **Swift CSP more detailed**more requirements on this, not necessarily stricter |
| Secure acquisition and development | NIS2: 1 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Configuration, change and patch management | NIS2: 1 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Vulnerability handling | NIS2: 1 | Swift CSP: 4 | **Swift CSP more detailed**more requirements on this, not necessarily stricter |
| Human resources security | NIS2: 2 | Swift CSP: 1 | **NIS2 asks more**binding, where the other is optional |
| Physical and environmental security | NIS2: 2 | Swift CSP: 1 | **Both cover it**read the wording below |
| Detection and response |  |  |  |
| Monitoring and detection | NIS2: 1 | Swift CSP: 3 | **Swift CSP more detailed**more requirements on this, not necessarily stricter |
| Incident handling | NIS2: 1 | Swift CSP: 1 | **Both cover it**read the wording below |
| Incident classification | NIS2: 3 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Reporting to authorities | NIS2: 5 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Informing customers and the public | NIS2: 2 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Threat intelligence and information sharing | NIS2: 1 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | NIS2: 1 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Backup and recovery | NIS2: 2 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Security testing | NIS2: 1 | Swift CSP: 1 | **NIS2 asks more**binding, where the other is optional |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | NIS2: 2 | Swift CSP: 1 | **Both cover it**read the wording below |
| Register of third-party arrangements | NIS2: 1 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Registration with authorities | NIS2: 2 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |
| Penalties and liability | NIS2: 2 | Swift CSP: – | **Only NIS2**no specific requirement on the other side in the acts covered |

## 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.

Included

- [NIS2](https://grc.plus/regulation/nis2/) Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
- [NIS2 Implementing Regulation](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/) Commission Implementing Regulation (EU) 2024/2690 Articles 3 to 14 · Annex · 17 requirements Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

Status

Reviewed against the official texts.

Included

- [Swift CSP](https://grc.plus/regulation/swift-customer-security-program-swift-csp/) Swift Customer Security Controls Framework v2026 (CSCF v2026) 32 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Incident reports go to

NIS2: CSIRT or competent authority

Swift CSP: Not in the acts covered

### First notice of an incident

NIS2: Without undue delay and in any event within 24 hours of becoming aware

Swift CSP: Not in the acts covered

### Incident notification

NIS2: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust service providers, for incidents affecting their trust services)

Swift CSP: Not in the acts covered

### Intermediate report

NIS2: On request

Swift CSP: Not in the acts covered

### Final report

NIS2: Within one month of the incident notification

Swift CSP: Not in the acts covered

### Review of the risk framework

NIS2: Risk assessment and treatment plan at planned intervals, at least annually, and after significant incidents or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

Swift CSP: Not in the acts covered

### Register of third-party arrangements

NIS2: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

Swift CSP: Not in the acts covered

### Registration with the authority

NIS2: Required; changes without delay and in any event within two weeks

Swift CSP: Not in the acts covered

### Management body training

NIS2: Required

Swift CSP: Not in the acts covered

### Management body liability

NIS2: Yes, for infringements of Article 21

Swift CSP: Not in the acts covered

### Maximum fines

NIS2: Essential entities: maximum of at least EUR 10 million or 2% of the undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. Important entities: maximum of at least EUR 7 million or 1.4%, whichever is higher.

Swift CSP: Not in the acts covered

## Governance

### Management accountability

**Only NIS2** 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

- Management approves and oversees the measures
  The management body approves the cybersecurity risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
  [NIS2, Article 20(1)](https://grc.plus/regulation/nis2/#requirements)

Nothing in the acts covered.

### Roles and independence

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

- Roles, responsibilities and authorities
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Security roles assigned and communicated to the management bodies, at least one person reporting directly to them, conflicting duties segregated where applicable, and the assignment reviewed by the management bodies at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

Nothing in the acts covered.

### Security policy

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements)
- Network and information system security policy
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A security policy approved by the management body, reviewed at least annually and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

Nothing in the acts covered.

### Awareness and training

**Both cover it** read the wording below

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

- Management body training
  Members of the management body follow training to identify risks and assess cybersecurity risk-management practices. Entities are encouraged to offer similar training to employees regularly.
  [NIS2, Article 20(2)](https://grc.plus/regulation/nis2/#requirements)
- Cyber hygiene and training
  Basic cyber hygiene practices and cybersecurity training.
  [NIS2, Article 21(2)(g)](https://grc.plus/regulation/nis2/#requirements)

- Security Training and Awareness
  Applies to: All types
  Train staff with access to Swift on security, including role-specific training for privileged users.
  [Swift CSP, Control 7.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## Risk management

### Risk management framework

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

- Appropriate and proportionate measures
  Technical, operational and organisational measures to manage the risks to network and information systems, set by the state of the art, relevant standards, cost, the entity's exposure and size, and the likelihood and severity of incidents.
  [NIS2, Article 21(1)](https://grc.plus/regulation/nis2/#requirements)
- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements)
- Risk management framework
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

Nothing in the acts covered.

### Risk assessment

**NIS2 asks more** binding, where the other is optional

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements)
- Risk management framework
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

- Scenario-based Risk Assessment (advisory) Recommended
  Applies to: All types (advisory)
  Assess the risk of Swift-related attack scenarios regularly.
  [Swift CSP, Control 7.4A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Review, audit and improvement

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

- Assessing effectiveness
  Policies and procedures to assess whether the cybersecurity risk-management measures work.
  [NIS2, Article 21(2)(f)](https://grc.plus/regulation/nis2/#requirements)
- Corrective measures
  An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.
  [NIS2, Article 21(4)](https://grc.plus/regulation/nis2/#requirements)
- Independent review
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Independent reviews of network and information security at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

Nothing in the acts covered.

### Asset management

**Only NIS2** 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

- Asset management
  Asset management.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Asset inventory
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A complete, accurate, up-to-date and consistent inventory of assets, with changes recorded in a traceable way.
  [NIS2 Implementing Regulation, Annex, point 12.4](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

Nothing in the acts covered.

## Protection

### Access control

**Both cover it** read the wording below

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

- Access control policies
  Access control policies.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Access rights and privileged accounts
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Management of access rights, and stricter controls on privileged and system administration accounts.
  [NIS2 Implementing Regulation, Annex, points 11.2 and 11.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

- Operating System Privileged Account Control
  Applies to: A1, A2, A3, A4; advisory for B
  Restrict and control the use of administrator accounts on the operating systems of in-scope components.
  [Swift CSP, Control 1.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Logical Access Control
  Applies to: All types
  Grant access on need-to-know, least privilege and segregation of duties, and review it regularly.
  [Swift CSP, Control 5.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Authentication

**Swift CSP more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

- Multi-factor authentication
  Multi-factor or continuous authentication solutions, where appropriate.
  [NIS2, Article 21(2)(j)](https://grc.plus/regulation/nis2/#requirements)
- Multi-factor authentication
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Multi-factor or continuous authentication where appropriate, in line with the classification of the asset accessed.
  [NIS2 Implementing Regulation, Annex, point 11.7](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

- Password Policy
  Applies to: All types
  Make passwords resistant to common attacks through an enforced password policy.
  [Swift CSP, Control 4.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Multi-Factor Authentication
  Applies to: All types
  Require multi-factor authentication for interactive access to Swift-related applications and operating system administration.
  [Swift CSP, Control 4.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Token Management
  Applies to: All types
  Manage hardware authentication tokens and keep them under the control of their owners.
  [Swift CSP, Control 5.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Password Repository Protection
  Applies to: All types
  Protect stored passwords, physical and logical, against disclosure.
  [Swift CSP, Control 5.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Cryptography and encryption

**NIS2 asks more** binding, where the other is optional

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24

- Cryptography
  Policies and procedures on the use of cryptography and, where appropriate, encryption.
  [NIS2, Article 21(2)(h)](https://grc.plus/regulation/nis2/#requirements)

- External Transmission Data Protection (advisory) Recommended
  Applies to: A1, A2, A3, A4 (advisory)
  Protect Swift-related data sent or stored outside the secure zone, such as back-ups or files moved to other sites.
  [Swift CSP, Control 2.5A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Data security

**Only Swift CSP** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

Nothing in the acts covered.

- Transaction Business Controls
  Applies to: All types
  Restrict transaction activity to what is expected for your business, such as hours, counterparties and value limits, and detect deviations.
  [Swift CSP, Control 2.9](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- RMA Business Controls (advisory) Recommended
  Applies to: All types (advisory)
  Review Relationship Management Application relationships regularly and remove those no longer needed.
  [Swift CSP, Control 2.11A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Software Integrity
  Applies to: A1, A2, A3; advisory for A4
  Check the integrity of the Swift-related software you run.
  [Swift CSP, Control 6.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Database Integrity
  Applies to: A1, A2; advisory for A4
  Check the integrity of the database records of the messaging interface.
  [Swift CSP, Control 6.3](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Network security

**Swift CSP more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

- Network security and segmentation
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Network security measures, and systems segmented into networks or zones by risk and from third parties' systems.
  [NIS2 Implementing Regulation, Annex, points 6.7 and 6.8](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

- Swift Environment Protection
  Applies to: A1, A2, A3
  Place the Swift infrastructure in a secure zone, separated from the general IT environment, with controlled access into and out of it.
  [Swift CSP, Control 1.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Virtualisation or Cloud Platform Protection
  Applies to: A1, A2, A3, A4; advisory for B
  Secure the virtualisation or cloud platform that hosts in-scope components to the same level as the components themselves.
  [Swift CSP, Control 1.3](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Restriction of Internet Access
  Applies to: All types
  Limit internet access from operator PCs and in-scope systems to what is needed, and control it.
  [Swift CSP, Control 1.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Customer Environment Protection
  Applies to: A4
  For users with a customer connector, protect that environment in a dedicated, separated zone.
  [Swift CSP, Control 1.5](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Secure communications

**Swift CSP more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14

- Secured communications
  Secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate.
  [NIS2, Article 21(2)(j)](https://grc.plus/regulation/nis2/#requirements)

- Internal Data Flow Security
  Applies to: A1, A2, A3
  Protect the confidentiality, integrity and authenticity of data flows between Swift-related components.
  [Swift CSP, Control 2.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Back Office Data Flow Security
  Applies to: A1, A2, A3, A4
  Protect data flows between the back office and the secure zone, starting with bridging servers. Mandatory since v2026; legacy direct flows tentatively from 2028.
  [Swift CSP, Control 2.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Operator Session Confidentiality and Integrity
  Applies to: All types
  Protect interactive operator sessions to Swift-related applications against eavesdropping and tampering.
  [Swift CSP, Control 2.6](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Secure acquisition and development

**Only NIS2** 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

- Secure acquisition, development and maintenance
  Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
  [NIS2, Article 21(2)(e)](https://grc.plus/regulation/nis2/#requirements)

Nothing in the acts covered.

### Configuration, change and patch management

**Only NIS2** 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

- Configuration, change and patch management
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Secure configurations, controlled changes, repairs and maintenance, and security patches applied within a reasonable time after release, unless the disadvantages outweigh the cybersecurity benefits and the reasons are documented.
  [NIS2 Implementing Regulation, Annex, points 6.3, 6.4 and 6.6](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

Nothing in the acts covered.

### Vulnerability handling

**Swift CSP more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8

- Secure acquisition, development and maintenance
  Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
  [NIS2, Article 21(2)(e)](https://grc.plus/regulation/nis2/#requirements)

- Security Updates
  Applies to: All types
  Install vendor security updates on in-scope hardware and software within a risk-based time frame.
  [Swift CSP, Control 2.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- System Hardening
  Applies to: All types
  Harden operating systems, databases and network devices of the Swift environment against attack.
  [Swift CSP, Control 2.3](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Vulnerability Scanning
  Applies to: A1, A2, A3, A4; advisory for B
  Scan in-scope components for vulnerabilities and act on the results.
  [Swift CSP, Control 2.7](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Application Hardening
  Applies to: A1, A2, A3
  Harden the Swift messaging and communication interfaces and related applications.
  [Swift CSP, Control 2.10](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Human resources security

**NIS2 asks more** binding, where the other is optional

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

- Human resources security
  Human resources security.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Background verification
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Background checks on employees, and where applicable on direct suppliers and service providers, to the extent feasible and where the role needs it.
  [NIS2 Implementing Regulation, Annex, point 10.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

- Staff Screening Process (advisory) Recommended
  Applies to: All types (advisory)
  Screen staff who operate or administer the Swift environment before and during employment, where local law allows.
  [Swift CSP, Control 5.3A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Physical and environmental security

**Both cover it** read the wording below

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14

- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements)
- Physical and environmental security
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Supporting utilities, protection against physical and environmental threats, and perimeter and physical access control.
  [NIS2 Implementing Regulation, Annex, points 13.1 to 13.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

- Physical Security
  Applies to: All types
  Prevent unauthorised physical access to sensitive equipment, workplaces, tokens and storage media.
  [Swift CSP, Control 3.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## Detection and response

### Monitoring and detection

**Swift CSP more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

- Monitoring and logging
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Monitoring and logging of network and information systems to detect events that could be incidents.
  [NIS2 Implementing Regulation, Annex, point 3.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

- Malware Protection
  Applies to: All types
  Protect in-scope components with up-to-date anti-malware.
  [Swift CSP, Control 6.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Logging and Monitoring
  Applies to: All types
  Record security events and monitor them to detect anomalous activity and operations.
  [Swift CSP, Control 6.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Intrusion Detection (advisory) Recommended
  Applies to: A1, A2, A3, A4 (advisory)
  Detect and contain anomalous network activity inside and towards the secure zone.
  [Swift CSP, Control 6.5A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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

- Incident handling
  Procedures to handle incidents.
  [NIS2, Article 21(2)(b)](https://grc.plus/regulation/nis2/#requirements)

- Cyber Incident Response Planning
  Applies to: All types
  Keep and test a cyber incident response plan that covers Swift, including informing Swift and using its threat intelligence.
  [Swift CSP, Control 7.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Incident classification

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25

- When an incident is significant
  An incident is significant when it has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to others.
  [NIS2, Article 23(3)](https://grc.plus/regulation/nis2/#requirements)
- Event assessment and classification
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Suspicious events are assessed to decide whether they are incidents and, if so, their nature and severity. Recurring incidents under Article 4 are checked quarterly.
  [NIS2 Implementing Regulation, Annex, point 3.4](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)
- When an incident is significant
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Criteria that make an incident significant: general criteria for all these providers (Article 3), recurring incidents (Article 4) and criteria for each kind of provider (Articles 5 to 14).
  [NIS2 Implementing Regulation, Articles 3 to 14](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

Nothing in the acts covered.

### Reporting to authorities

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

- Notify significant incidents
  Notify the CSIRT or competent authority without undue delay of any significant incident, with the information needed to judge any cross-border impact.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements)
- Early warning
  An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.
  [NIS2, Article 23(4)(a)](https://grc.plus/regulation/nis2/#requirements)
- Incident notification
  An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.
  [NIS2, Article 23(4)(b)](https://grc.plus/regulation/nis2/#requirements)
- Intermediate report
  An intermediate report on status updates, when the CSIRT or authority asks for one.
  [NIS2, Article 23(4)(c)](https://grc.plus/regulation/nis2/#requirements)
- Final report
  A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.
  [NIS2, Article 23(4)(d) and (e)](https://grc.plus/regulation/nis2/#requirements)

Nothing in the acts covered.

### Informing customers and the public

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

- Inform affected recipients
  Where appropriate, notify recipients of the services without undue delay of significant incidents likely to affect the provision of those services.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements)
- Warn of significant cyber threats
  Where applicable, tell recipients potentially affected by a significant cyber threat, without undue delay, what they can do about it and, where appropriate, about the threat itself.
  [NIS2, Article 23(2)](https://grc.plus/regulation/nis2/#requirements)

Nothing in the acts covered.

### Threat intelligence and information sharing

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.5.6, A.5.7

- Information-sharing arrangements Optional
  Entities may exchange cybersecurity information such as threats, vulnerabilities and indicators of compromise within information-sharing arrangements. Essential and important entities notify the competent authority when they join or withdraw.
  [NIS2, Article 29](https://grc.plus/regulation/nis2/#requirements)

Nothing in the acts covered.

## Continuity and resilience

### Business continuity and crisis management

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30

- Business continuity and crisis management
  Business continuity, such as backup management and disaster recovery, and crisis management.
  [NIS2, Article 21(2)(c)](https://grc.plus/regulation/nis2/#requirements)

Nothing in the acts covered.

### Backup and recovery

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

- Business continuity and crisis management
  Business continuity, such as backup management and disaster recovery, and crisis management.
  [NIS2, Article 21(2)(c)](https://grc.plus/regulation/nis2/#requirements)
- Backup and redundancy
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Backup copies and sufficient redundancy, with regular integrity checks on the copies and regular testing of recovery of copies and redundancies.
  [NIS2 Implementing Regulation, Annex, point 4.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

Nothing in the acts covered.

### Security testing

**NIS2 asks more** binding, where the other is optional

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

- Security testing
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A policy and procedures for security testing of network and information systems.
  [NIS2 Implementing Regulation, Annex, point 6.5](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

- Penetration Testing (advisory) Recommended
  Applies to: All types (advisory)
  Test the security of the Swift environment through penetration tests.
  [Swift CSP, Control 7.3A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## 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

- Supply chain security
  Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.
  [NIS2, Article 21(2)(d)](https://grc.plus/regulation/nis2/#requirements)
- What to weigh for each supplier and service provider
  Entities weigh the specific vulnerabilities of each direct supplier and service provider, the quality of their products and cybersecurity practices, including secure development, and the results of EU coordinated risk assessments of critical supply chains.
  [NIS2, Article 21(3)](https://grc.plus/regulation/nis2/#requirements)

- Outsourced Critical Activity Protection
  Applies to: All types
  Ensure that critical activities outsourced to third parties are protected to the same standard.
  [Swift CSP, Control 2.8](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Register of third-party arrangements

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

- Directory of suppliers
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A directory of direct suppliers and service providers, kept up to date.
  [NIS2 Implementing Regulation, Annex, point 5.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

Nothing in the acts covered.

## Supervision and enforcement

### Registration with authorities

**Only NIS2** no specific requirement on the other side in the acts covered

- Register with the authority
  Submit to the competent authority the entity's name, address, contact details including IP ranges and, where applicable, its sector and the Member States where it provides services. Report changes without delay and within two weeks.
  [NIS2, Article 3(4)](https://grc.plus/regulation/nis2/#requirements)
- Registry of digital providers
  DNS, TLD, domain name registration, cloud, data centre, content delivery, managed (security) service providers, marketplaces, search engines and social networks submit their details to the competent authority by 17 January 2025 for the ENISA registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).
  [NIS2, Article 27](https://grc.plus/regulation/nis2/#requirements)

Nothing in the acts covered.

### Penalties and liability

**Only NIS2** no specific requirement on the other side in the acts covered

- Management approves and oversees the measures
  The management body approves the cybersecurity risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
  [NIS2, Article 20(1)](https://grc.plus/regulation/nis2/#requirements)
- Administrative fines
  Infringements of Article 21 or 23 can be fined. Member States set maximums of at least the amounts below, whichever is higher.
  [NIS2, Article 34(4) and (5)](https://grc.plus/regulation/nis2/#requirements)

Nothing in the acts covered.

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.

## More Comparisons

- [Compare NIS2](https://grc.plus/compare/nis2/)
- [Compare Swift CSP](https://grc.plus/compare/swift-csp/)

Source: https://grc.plus/compare/nis2-vs-swift-csp/
