Your digital compliance
Operational resilience: NIS2 and DORA
NIS2 and, in financial services, DORA: keep your services running, manage your suppliers and report incidents on time.
NIS2 applies to medium-sized and large entities in listed sectors, and DORA to financial entities, and both ask you to keep services running, manage ICT suppliers and report incidents on time. Pitch helps you check whether either applies, review supplier contracts and prepare the incident reporting steps.
Your digital compliance
Explore the nine themes of your digital compliance.
Scroll on, or turn the needle yourself, and see what clients ask us along the way. Anything that catches your eye? Click that part of the circle to dive in.
- GDPR and privacy Personal data, handled lawfully: your record of processing, cookies, data subject requests, and what to do after a breach.
- AI Act Find out which AI Act duties apply to you as a provider or user of AI, and when.
- Data Act and data sharing Share or license your data on your terms, and meet the access and switching rules of the Data Act.
- NIS2: does it apply to your company? NIS2 applies to medium-sized and large companies in the sectors of its two annexes. If you are in scope, you register with the CCB, take security measures, report incidents in stages and answer for it at board level. Pitch tells you where you stand.
- Operational resilience: NIS2 and DORA You are here NIS2 and, in financial services, DORA: keep your services running, manage your suppliers and report incidents on time.
- Secure products: Cybersecurity Act and Cyber Resilience Act Bring hardware and software to the EU market that meet the Cyber Resilience Act, and use EU cybersecurity certification where it counts.
- Online platforms: Digital Services Act Host user content or run a marketplace? Set up notice and action, transparent terms and trader checks under the DSA and the P2B Regulation.
- Consumer law and e-commerce Selling online to consumers comes with a long checklist. Information duties, withdrawal and guarantees, pricing and reviews, green claims, accessibility.
- Sanctions and anti-money laundering Screen customers and partners, and know what the sanctions and anti-money laundering rules expect of you.
GDPR and privacy
AI Act
Data Act and data sharing
NIS2: does it apply to your company?
Operational resilience: NIS2 and DORA
Secure products: Cybersecurity Act and Cyber Resilience Act
Online platforms: Digital Services Act
Consumer law and e-commerce
Sanctions and anti-money laundering
What clients ask us
Do NIS2 or DORA apply to us, directly or as a supplier?
NIS2 applies to medium-sized and large entities in the sectors of its two annexes, such as energy, transport, health, digital infrastructure, ICT services, manufacturing and online marketplaces. NIS2 is an EU directive that each Member State transposes into national law, so details and supervisors differ per country. DORA applies to financial entities and, through contracts, to their ICT providers. Smaller suppliers often meet the rules through customer requirements. Pitch helps you assess scope and contract exposure.
- AcademyThe NIS2 Directive →
- SolutionsCommercial Contracts & Transactions →
We are a financial entity. What does DORA require of us?
DORA (Regulation (EU) 2022/2554, applicable since 17 January 2025) is about staying operational, not only about security. Your management body must approve and oversee an ICT risk management framework, including business continuity and recovery plans. You classify ICT-related incidents and report major ones to your supervisor, test your digital operational resilience regularly (the largest entities with threat-led penetration tests), and manage ICT third-party risk, including a register of information on all your ICT contracts. Pitch helps with the governance documents, the register and the contracts.
What must we report after a security incident, and to whom?
Under NIS2, a significant incident goes to the national CSIRT or competent authority in stages: an early warning within 24 hours of becoming aware, a notification within 72 hours and a final report within one month. If personal data are affected, a separate GDPR notification to the data protection authority is due within 72 hours. Addressees and content differ, so prepare both from one set of facts. Financial entities under DORA report major ICT incidents to their financial supervisor.
- AcademyThe NIS2 Directive →
- AcademyGDPR Breach Notification: the 72-Hour Rule →
- SolutionsData Breach Response →
What do we need to agree with our ICT suppliers?
Both regimes make you responsible for your supply chain. Expect to need security requirements, incident notification duties with short deadlines, audit and information rights, sub-contractor controls, business continuity and exit or data return terms. DORA lists mandatory contract content for ICT services to financial entities. Supplier standard terms rarely cover this, so review and renegotiate them. Pitch drafts and reviews these clauses.
Do we have to register as a NIS2 entity?
Often yes, if you fall within NIS2 scope: Member States require in-scope entities to register or notify the national authority, but procedures, platforms and deadlines differ per country. Registration also requires you to determine whether you are essential or important, which affects supervision. If you are unsure, do a scope analysis first. Essential entities must also have their compliance assessed, with the method set nationally (often by reference to standards such as ISO/IEC 27001).
- AcademyThe NIS2 Directive →
Can management be held liable under NIS2?
NIS2 puts governance on the board: management bodies must approve the cybersecurity risk measures, oversee their implementation and follow training, and can be held liable for infringements. Fines can reach EUR 10 million or 2% of worldwide turnover for essential entities and EUR 7 million or 1.4% for important entities. Minutes showing that the board reviewed and approved the measures are your best evidence.
- AcademyThe NIS2 Directive →
What security measures does NIS2 actually require?
Article 21 requires appropriate and proportionate technical, operational and organisational measures based on an all-hazards approach. The list includes risk analysis, incident handling, business continuity and backups, supply chain security, vulnerability handling, cryptography, access control and multi-factor authentication. There is no fixed checklist, so run a gap assessment, have the board approve a plan and keep evidence. Pitch advises on the legal and contractual side, not on technical security testing.
- AcademyThe NIS2 Directive →
- SolutionsCommercial Contracts & Transactions →
We are a small software company serving banks. What does DORA mean for us?
DORA, applicable since 17 January 2025, binds financial entities, not you directly, unless you are designated a critical ICT third-party provider. But your bank customers must put specific terms in their contracts with you: service descriptions, locations of data, security and incident support, audit access, sub-contracting conditions and exit assistance. Expect these requests and prepare a standard addendum rather than negotiating each one from scratch.
- SolutionsCommercial Contracts & Transactions →
- TechnologyContract Review →
How we help
-
Data Breach Response
Help from the first hours of a personal data breach: assessment, notification to the authority and individuals, documentation, and action against the source.
-
Commercial Contracts & Transactions
Supply, distribution, services, SaaS and procurement contracts, and the deals around them, drafted and reviewed with the IP, data and tax angles in view.
-
NIS2 Cybersecurity Compliance
Are you an essential or important entity under the Belgian NIS2 law, and what does that ask of your board, your suppliers and your incident handling? We answer the legal side and keep the evidence in order.
-
DORA and ICT Third-Party Risk
For financial entities and the ICT providers that serve them. We keep the DORA register of information complete and bring ICT contracts in line with Article 30.
Read more
-
The NIS2 Directive
Who falls under NIS2, what the directive requires, how the 24-hour, 72-hour and one-month incident reports work and how they relate to GDPR breach notification.
-
GDPR Breach Notification: the 72-Hour Rule
Article 33 GDPR: notify the authority within 72 hours of becoming aware of a personal data breach. When to notify, how hours count, when to tell people.
-
AI Clauses in Vendor Contracts: 9 Terms to Negotiate
The AI clauses to negotiate when you buy or supply AI: AI Act roles, training on your data, output ownership, IP indemnity, audit and logs, liability.
-
SaaS Agreements
Subscriptions, service levels, data ownership, liability and exit in SaaS contracts, with the GDPR, the Data Act and national contract rules.
-
The 2026 cybersecurity package: revised Cybersecurity Act and NIS2 amendments
What the Commission proposed on 20 January 2026 in COM(2026) 11 (the Cybersecurity Act 2, replacing Regulation (EU) 2019/881) and COM(2026) 13 (targeted amendments to the NIS2 Directive), where the procedures stand and what companies can prepare now.
-
Cyber incidents across borders: the Cyber Solidarity Act
What Regulation (EU) 2025/38 sets up, the European Cybersecurity Alert System, the Cybersecurity Emergency Mechanism with the EU Cybersecurity Reserve and the incident review mechanism, how a company hit by a major incident can benefit, and what it means for managed security service providers.
Let’s talk
Tell us what you’re working on. We’ll get the right person on it and reply within one business day. The first chat is free.