SaaS Agreements – New EU and UK Data Security Laws

Below is a summary of the following data security laws, the EU Network and Information Systems Directive 2, the EU Digital Operational Resilience Act, the EU Cyber Resilience Act, the EU Critical Entities Resilience Directive and the UK Product Security and Telecommunications Infrastructure Act that will impact SaaS suppliers and SaaS customers in 2026. Some of these laws apply extra-territorially, meaning the laws apply even when a SaaS supplier is not located in the UK or the EU (respectively).

It is important to be aware of these new laws in order to assess whether or not they apply to your particular SaaS business, products and services.

The EU Network and Information Systems Directive 2 (NIS2)

NIS2 applies to “in-scope entities” that operate in, or have critical infrastructure located in the EU. This EU directive only comes into effect in each EU Member State once each EU Member State passes their own national law implementing the directive. This mean that the laws in each EU Member State under NIS2 will differ.

To date only around 5 EU Member States have implemented NIS2 into their national laws. France and Germany for example have not implemented their new draft laws yet.

In-Scope Entities

NIS2 makes a distinction between “essential” and “important” entities based on:

  • The size of the entity; and
  • The sector in which they operate.

Essential Entities

Essential entities are large entities operating in highly critical sectors (as listed in Annex I of NIS2), summarised below:

  • Health;
  • Energy;
  • Transport;
  • Digital infrastructures;
  • Drinking water;
  • Banking;
  • Financial markets;
  • Waste water;
  • Space;
  • ICT service management; and
  • Public administration.

These entities are subject to more active regulatory oversight and stricter penalties for non-compliance.

Important Entities

Important entities are other medium and large entities operating in critical sectors (as listed in Annex II of NIS2), summarised below:

  • Digital providers of market places, search engines or social networking platforms;
  • Waste management;
  • Manufacturing;
  • Chemicals manufacture and distribution;
  • Postal services;
  • Food production and distribution; and
  • Research.

These entities are subject to regulatory interest if authorities become aware of non-compliance.

Exempted Entities

Small businesses (i.e. businesses with fewer than 50 employees and an annual turnover of less than 10m Euros) are exempted from NIS2, unless they operate in certain high critical sectors.

NIS2 is extra-territorial in relation to entities who have a significant presence, such as a trading legal entity, facilities, operations, or staff, in an EU country, or provide services to the EU market.

Non-EU entities subject to NIS2 must appoint an EU Representative.

ENISA has published voluntary technical guidance to support Member States and in-scope entities in implementing the technical and methodological requirements for cyber security risk management measures applying to critical entities under NIS2.

The EU Digital Operational Resilience Act (DORA)

Since the 17th of January 2025, DORA provisions must be included in contracts entered into between financial services entities subject to DORA and their third party providers of ICT Services. As SaaS suppliers are third party providers of digital and data services on an ongoing basis they will be third party providers of ICT services where their SaaS customers are regulated by DORA.

Both the SaaS customer and the SaaS supplier must comply with their applicable mandatory obligations under DORA.

How to assess DORA compliance

Where a SaaS supplier provides ICT services to any SaaS customers regulated by DORA, SaaS suppliers need to:

  • Identify whether or not they provide any “critical” or “important” services to such SaaS customers; and
  • Amend the terms of existing SaaS agreements with such SaaS customers, to include the relevant DORA provisions.

SaaS suppliers should ensure that any new obligations Customers try to add to SaaS agreements are limited to the mandatory requirements set out in DORA. Any obligations applicable to “critical” or “important” services, as these are defined by DORA, should not be added unless the SaaS supplier itself (not the SaaS customer) provides “critical” or “important” ICT services.

The EU Cyber Resilience Act (CRA)

The CRA establishes a minimum level of cyber security for all connected products available on the EU market. This new law applies in all EU Member States and will be implemented gradually.

Products covered by the CRA

All products sold in the EU that contain “digital elements” must meet the essential requirements of the CRA. This includes low-cost consumer products as well as B2B software and complex high-end industrial systems. “Products with digital elements” are defined in the CRA as products that can be connected to a device or a network and include both hardware products with networked functions (e.g. smartphones, laptops, smart home products, smart watches, internet connected toys, but also microprocessors, firewalls and smart meters) and pure software products (e.g. accounting software, computer games, mobile apps).

Non-commercial open source software products are exempt from the CRA and therefore do not have to fulfil the requirements of the CRA.

Manufacturers can be fined up to 15 million Euros or 2.5% of their total annual worldwide turnover, whichever is higher, for a breach.

The EU Critical Entities Resilience Directive (CER)

The CER applies to all critical entities that operate (e.g. provide services to individuals) within the EU, across 11 sectors. Member States must identify critical entities operating within their borders and designate a competent authority for enforcement of the CER by the 17th of July 2026.

The CER operates alongside NIS2 to enhance the resilience of critical entities in the EU to address the resilience of critical entities in respect of all hazards, going beyond cyber security to anticipate other natural, man-made, accidental, or intentional risks.

The CER does not differentiate between “essential” and “important” entities, using instead the general terminology of “critical entities” for providers of essential services.

Each EU Member State will determine penalties, which must be effective, proportionate, and dissuasive.

The CER does not apply to a SaaS supplier until they are identified as a critical entity by a Member State.

UK Product Security and Telecommunications Infrastructure (PSTI) Act – 29th April 2024

The PSTI is a UK law that governs the security of consumer connectable devices used or made available to UK consumers. The security measures of the PSTI apply to manufacturers, retailers, importers and distributors of connectable products and smart devices. The telecommunications infrastructure measures apply to network operators and infrastructure providers.

The PSTI outlines the types of products that may be “relevant connected products” which include:

  • “internet-connectable products” which means a product that is capable of connecting to the internet; and
  • “network-connectable products” which means a product that is: (i) capable of both sending and receiving data by means of a transmission involving electrical or electromagnetic energy; (ii) is not an internet-connectable product; and (iii) meets the first or second connectability condition.

“UK consumer connectable products”, are defined in clause 54 of the PSTI as a relevant connectable product which either:

  • Captures a product that is, or has been, available to UK consumers and has not been supplied by a relevant person to any customer (whether in the UK or not) at any time before being made so available (i.e. is not used at the point at which it is made available to customers) (Condition A); or
  • Is, or has been made available, to customers in the UK who are not consumers which has not been supplied by a relevant person to any customer (whether in the UK or not) at any time before being made so available (i.e. is not used at the point at which it is made available to customers) and where products identical to it meet Condition A (Condition B).

A product may therefore meet the definition of a UK consumer connectable product even if it is solely aimed at business customers. For example: if a smart camera is advertised to business users but not to consumers in the UK because the distributor is selling the camera only to businesses. However, if products identical to the smart camera (e.g. a smart camera of the same make and model) have been advertised (i.e. made available) to consumers in the UK by another distributor, the product would be considered a UK consumer connectable product, when made available by the distributor.

Actions to Take Now

There are a lot of new EU and UK laws now in force, coming into force in stages or into force in the next 18 months that could affect SaaS Suppliers.

After considering the above summary, SaaS suppliers need to consider which of the above laws do, could, or may, apply to their products and services that they supply or the sectors in which they their business operates. This will depend upon numerous different factors for each law, such as:

  • The location of the SaaS supplier;
  • The location of customers, suppliers, data holders;
  • Whether services are provided BTB or BTC;
  • The global turnover of the SaaS supplier;
  • The sector in which the SaaS supplier operates;
  • The types of services being provided by the SaaS supplier;
  • The sector in which the SaaS customer operates;
  • Whether or not IoT services are provided; and
  • The specific EU country in which the SaaS supplier, its customers or the services are being made available.

Each of the above laws will need to be assessed separately to determine if, and how, they apply. SaaS suppliers need to take action now to ensure their compliance with the above laws, as there are no grace periods for non-compliance.

rene Bodle is an IT lawyer specialising in SaaS agreements, GDPR and cloud computing with over 15 years experience in the IT sector. If you require assistance with any SaaS or cloud computing contracts, GDPR or any other IT legal issues please contact me:

irene.bodle@bodlelaw.com

www.bodlelaw.com

To register for my newsletter click here

SaaS Agreements – DORA – ICT Supplier Obligations

SaaS suppliers obligations under the Digital Operational Resilience Act,(“DORA”), (Regulation (EU) 2022/2554 on digital operational resilience for the EU financial sector), are effective from the 17th of January 2025. From this date DORA provisions must be included in contracts entered into between financial services entities subject to DORA and their third party providers of ICT Services. As SaaS suppliers are third party providers of digital and data services on an ongoing basis they will be third party providers of ICT services if their SaaS customers are regulated by DORA. Both the SaaS customer and the SaaS supplier must comply with their applicable mandatory obligations under DORA.

Which entities does DORA apply to?

DORA applies directly to:

  • Any SaaS customers regulated by DORA; and
  • SaaS suppliers who provide “critical” or “important” ICT services to such SaaS customers.

DORA applies indirectly to SaaS suppliers who provide ICT Services to a SaaS customer regulated by DORA, as the SaaS customer must include certain mandatory provisions in their SaaS agreement with the SaaS supplier, in order for the SaaS customer to comply with its DORA obligations.

Does DORA only apply to EU entities?

DORA applies to:

  • Financial services SaaS customers located in the EU;
  • Financial services SaaS customers located outside the EU where the non-EU parent company enters into a contract with a SaaS supplier for provision of ICT services to any group entities within the scope of DORA (i.e. a global or master services agreement).

Penalties for breaches of DORA

Supervisory authorities can impose fines of up to 2% of global annual turnover for breaches of DORA. Local EU authorities can impose personal fines on the senior management and board members of a regulated entity of up to 1 million Euros.

Mandatory contractual terms

Article 30 of DORA sets out the mandatory contractual provisions that must be included in any SaaS agreement with a SaaS suppler who provides ICT services to a DORA regulated SaaS customer.

For all SaaS suppliers

Article 30(2)(a) – (i) of DORA set out the provisions applicable to all SaaS suppliers. These include:

  • An ICT services description;
  • Sub-contracting consents;
  • Services and data location information;
  • Data availability, integrity and data protection obligations;
  • Access to data;
  • Provision of free assistance if an ICT incident occurs;
  • Obligations to fully co-operate with appropriate regulators of the SaaS customer;
  • Specific termination rights;
  • Obligation to participate in the SaaS customer’s ICT security awareness programmes and digital operational resilience training.

For SaaS suppliers providing “critical or “important” ICT services

Article 30(3)(a) – (h) of DORA set out the additional provisions applicable to SaaS suppliers who provide “critical or “important” ICT services. These include :

  • Full service level descriptions;
  • Notice and reporting obligations;
  • Provision of business contingency plans;
  • Granting penetration testing rights;
  • Monitoring of SaaS supplier’s performance;
  • Unrestricted SaaS customer audit rights;
  • Comprehensive documented and tested exit arrangements, including provision of transitional and migration services.

How to assess DORA compliance

If you are a SaaS supplier who provides ICT services to any financial services SaaS customers regulated by DORA, you need to:

  • Check your existing customers to identify any financial services SaaS customers you provide ICT services to, who are regulated by DORA;
  • Identify whether or not your provide any “critical” or “important” services to such SaaS customers;
  • Amend the terms of your existing SaaS agreements with these SaaS customers, where you provide “critical” or “important” ICT services; and
  • When requested by a SaaS supplier to add any DORA amendments to a SaaS agreement, check that your new obligations are restricted to your mandatory requirements as a third party provider of ICT services as set out in Article 30 of DORA.

Irene Bodle is an IT lawyer specialising in SaaS agreements, GDPR and cloud computing with over 15 years experience in the IT sector. If you require assistance with any SaaS or cloud computing contracts, GDPR or any other IT legal issues please contact me:

irene.bodle@bodlelaw.com

www.bodlelaw.com

To register for my newsletter click here

SaaS Agreements – FAQs – What is SaaS and Essential Terms to include in a SaaS Agreement

SaaS is the abbreviation for “software as a service”. You may know this under another name, for example subscription agreement, SaaS contract, software on demand, software subscription agreement, cloud computing or ASP services (application service provider). These names all refer to the same thing – hosted software being made available via the Internet to users.

What is a SaaS Agreement

A SaaS agreement is simply the name used for the agreement between a SaaS supplier and a SaaS customer which sets out the terms under which the SaaS software may be accessed. This will usually include a service level agreement (SLA) and a data processing agreement (DPA).

Differences between a SaaS Agreement and a Standard Software Licence

A SaaS agreement differs from a standard software licence in that:

  • The SaaS customer will not receive a physical or installed copy of the software;
  • No ownership in the SaaS software will be transferred to the SaaS customer;
  • The SaaS customer‘s right to use SaaS software will end upon termination of the SaaS contract.

Essential Terms to Include in a SaaS Agreement

The following legal issues should be included in any SaaS agreement, whether you are a SaaS supplier or a SaaS customer.

Software Licence

Access to the SaaS software should be limited to the term of the SaaS agreement. Once the SaaS agreement expires or terminates the software licence should automatically terminate.

If the SaaS customer is a global entity, you should specify:

  • Which companies or entities may access the SaaS software;
  • In which territories the software may be used; and
  • The number of authorised users;
  • Identify the specific purposes for which the SaaS software may be accessed; and
  • Name any third parties who will be permitted access to the SaaS software i.e. outsourcing providers or clients of the SaaS customer.

Intellectual Property Rights – IPR

The SaaS supplier should retain ownership of all IPR in the SaaS software and services it provides. The SaaS customer should retain ownership of all IPR in its systems, content and data. You should specifically state that the source code remains owned by the SaaS supplier. The SaaS customer should grant the SaaS supplier the right to use its IPRs for the term of the SaaS agreement i.e. to display the SaaS customer’s logos and copyrighted information.

Applicable Law, Jurisdiction & Language

A SaaS supplier should specify which law applies to the SaaS agreement and which courts will deal with any disputes arising from it. In international SaaS agreements make sure that you specify in which language the dispute will be dealt with, and if the SaaS agreement is in more than one language, which language prevails if there is a discrepancy between the two versions.

Return of Data

At the end of the SaaS agreement the SaaS customer’s data should be returned and to compy with the GDPR and other data protection laws all personal data must be returned and deleted. The format in which the data is to be returned and any payment for this service should be agreed in advance. Additionally, the parties can agree that the SaaS supplier will provide assistance in transferring SaaS customer data to a new supplier – in return for payment for this data migration service.

Data Processing Agreement (DPA)

The SaaS supplier is the data processor and the SaaS customer is the data controller. Under data protection law different rules apply to the data controller and the data processor. In compliance with the General Data Protection Regulation (GDPR) The SaaS supplier is obliged to process data in accordance with the SaaS customer’s written instructions and should protect itself against claims from third parties that such processing was illegal. Likewise, the SaaS customer will also need to protect itself against claims from third parties caused by the SaaS supplier not processing data in accordance with its instructions or the terms of the data processing agreement.

Both the SaaS supplier and the SaaS customer’s data protections obligations must be set out in a written data processing agreement (DPA) which forms a schedule to the SaaS agreement. In addition where any international transfers of EU, UK or Swiss personal data are made, Standard Contractual Clauses must be used and the SaaS customer and SaaS supplier must carry out Schrems II Data Transfer Assessments. The SaaS supplier must also provide a list of the sub-processors that it uses to provide the SaaS services and a security policy.

Service Level Agreement (SLA)

This sets out the hosting, support and maintenance services being provided to the SaaS customer by the SaaS supplier. The SLA should specify where the data centre is located, who is operating it, what security, backup and disaster recovery procedures are in place. Support hours and support services for dealing with hosting problems and software problems should be identified and documented and the procedure for dealing with upgrades and maintenance to the software should be specified. The particular details will depend on the amount being paid for the hosting, support and maintenance and the purpose for which the SaaS software is being used.

Summary

Due to the unique nature of SaaS agreements you will need to seek specialist legal advice on the content of a SaaS agreement whether you are a SaaS supplier or a SaaS customer to ensure that your rights are adequately protected and that you are fully complying with all applicable laws.

Help

Irene Bodle is an IT lawyer specialising in SaaS agreements, GDPR and cloud computing with over 15 years experience in the IT sector. If you require assistance with any SaaS or cloud computing contracts, GDPR or any other IT legal issues please contact me:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

SaaS, ASP Agreements – FAQs – Disaster Recovery

Do I need disaster recovery provisions in a SaaS agreement?

Disaster Recovery

Disaster recovery sets out the processes and procedures to be followed in the event of SaaS software, or customer data, no longer being accessible due to a problem with the technology infrastructure at the supplier’s data centre.

For example if there is a power cut, flood or fire at the data centre, the server on which the software is running will no longer function and the customer will no longer have full access to the software and its data. If the customer is using the software for a live website, the website will cease to function correctly, or possibly at all.

Supplier Obligations

The disaster recovery provisions of a SaaS agreement should be set out in the SLA and should as a minimum, include the following supplier obligations in the event of a disaster:

  • customers must be notified of the disaster;
  • any third parties used for disaster recovery should be identified;
  • the estimated time for restoring the servers and access to the software and services should be specified; and
  • details should be given about the supplier’s testing procedures i.e. how often its disaster recovery processes are tested.

Costs

The extent and speed of the disaster recovery offered by the supplier will depend upon the fee charged for this service. Suppliers often include the costs of basic disaster recovery in their licence fees. In addition, or as an alternative, they may offer higher levels of disaster recovery for additional fees. The faster and more individual the disaster recovery process is, the higher the fees.

If the supplier does not provide any disaster recovery services, or the customer is not satisfied with the disaster recovery offered, it should consider setting up its own disaster recovery procedure with a third party, particularly if a disaster would be business critical i.e. for a customer providing online banking services.

Avoiding Disasters

The most common disaster recovery risks are power failure, physical damage to the data centre or data and insolvency.

Power Failure

To minimise the risk of a power failure causing the servers to fail, ensure that the data centre has a continuous power supply (UPS) and power regulators to prevent fluctuations or interruptions in the power supply.

Backups

If the SaaS agreement includes backup of customer data, the regularity, media used for backups and storage should be set out in the SLA.  Backups should not be stored at the same physical location as the servers on which the data is being processed.

Encryption

The media on which customer data is backed up should be encrypted. Particularly, if backups are to be physically sent to the customer, or moved to another data centre in the event of a disaster.

Access to Data

In the event that the data centre or a third party making backups of customer data becomes insolvent, the customer usually has no right to access its data and backups. Provisions should be included in the SLA to give the customer the right to access its data and backups in such circumstances.

Help

For assistance with any disaster recover issues, SLA, SaaS, ASP, software on demand contracts or any other IT legal issues contact me at:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles:

 

SaaS, ASP Agreements – FAQs – Security

What data security provisions need to be included in a SaaS agreement?

Customer’s Security Obligations

These should be set out in the software licence. Access to the software and services should not be permitted to third parties without prior authorisation from the supplier. The customer should provide the following warranties:

  • existence of adequate security measure to ensure access to the software and services does not breach the terms of the SaaS agreement
  • relevant confidentiality provisions relating to the use and access to passwords required for accessing the software and services
  • the obligation to notify the supplier of all security breaches, unauthorised access to the software and services and misuse of passwords
  • provision of indemnities for breaches of the above warranties

Supplier’s Security Obligations

These should be set out in the software licence and in the service level agreement (SLA). The supplier’s obligations will be more extensive than the customer’s obligations due to the nature of a SaaS agreement and the inherent risks of operating over the Internet. The following provisions should be included:

  • details of the firewalls and cryptology used
  • obligation of the supplier to notify the customer of security breaches or data loss
  • details of the data centre security structure
  • restrictions on access to passwords
  • information about virus protection mechanisms

Additionally the supplier should reserve the right to suspend access to the software and services if there is a security breach in order to ensure the integrity or security of the software and services.

Audit Rights

Sometimes customer’s will have a regulatory duty (i.e. under the FSA) to check the supplier’s security structures and systems and that the supplier is complying with its contractual security obligations. If an audit right is granted the following issues should be covered in the SaaS agreement:

  • frequency of the audits
  • payment for the supplier’s time and assistance with audits
  • the supplier’s right to be given copies of audit reports
  • confidentiality provisions relating to access to the supplier’s IPRs, data and infrastructures and disclosure of such to third parties
  • whether or not the supplier has any obligation to make changes to the software and services following an audit

Help

For assistance with any security issues, SaaS, ASP, software on demand contracts or any other IT legal issues contact me at:

irene.bodle@bodlelaw.com
www.bodlelaw.com

To register for my newsletter click here

______________________________________________________

Other related articles: