What is Software-As-A-Service (SaaS)?

·

Glossary: Software-as-a-Service

Software as a service (SaaS) is a way of delivering software in which the provider runs an application on its own cloud infrastructure and customers use it over a network, through a web browser or a program interface, without managing the servers, operating systems or storage beneath it.

This entry gives the standard definition of SaaS, compares it with platform and infrastructure services and sets out how widely businesses use it. It then covers what UK and EU regulators expect of an insurer that relies on SaaS, with the data protection and accounting rules that apply.

What is SaaS? The NIST definition

The US National Institute of Standards and Technology (NIST) set out its definition of cloud computing in Special Publication 800-145, published in September 2011. It describes cloud computing as a model for enabling on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service provider interaction, made up of five essential characteristics, three service models and four deployment models.1

NIST defines SaaS as the capability "to use the provider's applications running on a cloud infrastructure". The applications are reached from various client devices through a thin client interface, such as a web browser, or through a program interface, and NIST gives web-based email as an example.1 The customer "does not manage or control the underlying cloud infrastructure", including the network, servers, operating systems, storage or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.1

The five essential characteristics are on-demand self-service, broad network access, resource pooling, rapid elasticity and measured service. Under measured service, cloud systems meter resource use, such as storage, processing, bandwidth and active user accounts, and NIST notes that this is typically done on a pay-per-use or charge-per-use basis.1 The four deployment models are private, community, public and hybrid cloud. A public cloud is provisioned for open use by the general public and exists on the premises of the cloud provider; a private cloud is provisioned for the exclusive use of a single organisation and may exist on or off premises.1

UK public bodies use the same terms. The Financial Conduct Authority (FCA) treats "cloud" as a broad term that includes private, public and hybrid cloud as well as infrastructure as a service (IaaS), platform as a service (PaaS) and SaaS.2 For its 2023 business survey, the Office for National Statistics (ONS) defined cloud-based computing systems and applications as computing resources available on demand via the internet.3

SaaS vs PaaS vs IaaS: who manages what

Software as a service (SaaS)Platform as a service (PaaS)Infrastructure as a service (IaaS)
What the customer is givenUse of the provider's applications running on a cloud infrastructureThe ability to deploy applications it has created or acquired onto the cloud infrastructure, using programming languages, libraries, services and tools the provider supportsProcessing, storage, networks and other fundamental computing resources, on which it can deploy and run any software, including operating systems
What the customer controlsAt most, limited user-specific application configuration settingsIts deployed applications and possibly configuration settings for the application-hosting environmentOperating systems, storage and deployed applications, and possibly limited control of select networking components such as host firewalls
What the customer does not manage or controlThe network, servers, operating systems, storage and even individual application capabilitiesThe network, servers, operating systems and storageThe underlying cloud infrastructure
The three NIST cloud service models compared: what the customer is given and what it controls1

The National Cyber Security Centre (NCSC) describes the split as a shared responsibility model. An organisation that builds services in its own data centres is entirely responsible for their security; one that uses cloud services delegates management of parts of the service, and some of the security responsibility, to the provider, in amounts that vary with the service.4 The NCSC states that SaaS allows a customer to delegate the most responsibility to the provider, but that the customer is always responsible for ensuring the service can meet its security needs, for securely configuring the services it uses and for deciding which data it stores in them.4 Its separate guidance on using SaaS securely is written for customers setting up a new tenancy of a SaaS application or reviewing one already in use.5

The Prudential Regulation Authority (PRA) describes the same model in its supervisory statement SS2/21. The firm is responsible for what is in the cloud and the provider for the provision of the cloud; firms remain responsible for identifying and classifying data and for configuring and monitoring their data in the cloud; and other responsibilities are shared depending on whether the service is IaaS, PaaS or SaaS.6 The PRA expects firms to define, document and understand their own and the provider's responsibilities.6

Multi-tenancy, separation and data location

Resource pooling, one of NIST's essential characteristics, means the provider's resources "are pooled to serve multiple consumers using a multi-tenant model", with physical and virtual resources assigned and reassigned according to demand. The customer generally has no control or knowledge over the exact location of the resources but may be able to specify location at a higher level, such as a country, state or data centre.1

The NCSC publishes 14 cloud security principles, which it states apply to both cloud platforms and SaaS. Principle 3, separation between customers, says that "a malicious or compromised customer of the service should not be able to access or affect the service or data of another", which requires effective security boundaries in the way the service runs code, stores data and manages the network.7

The FCA's guidance asks a firm to agree a data residency policy with the provider at the start of the relationship, setting out the jurisdictions in which its data can be stored, processed and managed, and to consider how data will be segregated if it uses a public cloud. It also asks firms to ensure data is not stored in jurisdictions that may inhibit effective access to data for UK regulators.2

How many businesses use SaaS

Paid cloud services in EU enterprises, 2025

52.74%
of EU enterprises used paid cloud computing services
96.44%
of those bought at least one SaaS service
7.42
percentage points: the rise in paid cloud use since 2023
Source: Eurostat, Cloud computing: statistics on the use by enterprises, data extracted January 2026. Enterprises with 10 or more employees or self-employed persons. Financial and insurance activities are not covered.

In the EU survey on ICT usage and e-commerce in enterprises, 52.74% of EU enterprises used paid cloud computing services in 2025, an increase of 7.42 percentage points on 2023.8 Of the enterprises using paid cloud, 96.44% bought at least one SaaS service, which Eurostat counts as e-mail, office software, finance or accounting software, enterprise resource planning (ERP), customer relationship management (CRM) or security software bought as a cloud service; 77.25% also bought IaaS and 26.08% PaaS.8

Cloud serviceShare of enterprises using paid cloudService model
E-mail85.15%SaaS
Office software71.69%SaaS
Storage of files71.53%IaaS
Security software applications65.49%SaaS
Finance or accounting software58.16%SaaS
Hosting the enterprise's database45.52%IaaS
Enterprise resource planning (ERP)30.12%SaaS
Computing power to run the enterprise's own software28.18%IaaS
Customer relationship management (CRM)27.91%SaaS
A hosted environment for application development, testing or deployment26.08%PaaS
What EU enterprises buying paid cloud services used them for, 2025, as a share of those enterprises, with the service model Eurostat assigns. Enterprises with 10 or more employees or self-employed persons; the sectors surveyed do not include financial and insurance activities8

EU enterprises using paid cloud computing services, by size, 2025

84.67%
of large enterprises (250 or more employees)
66.78%
of medium enterprises (50 to 249 employees)
49.3%
of small enterprises (10 to 49 employees)
Source: Eurostat, Cloud computing: statistics on the use by enterprises, data extracted January 2026. Financial and insurance activities are not covered.

Eurostat reported that buying SaaS was equally popular among enterprises regardless of size, while large enterprises bought IaaS and PaaS more often: 52.86% of large enterprises using paid cloud bought PaaS, against 34.5% of medium and 22.59% of small enterprises.8 Among enterprises using paid cloud, the share using finance or accounting applications rose by 6.52 percentage points between 2023 and 2025.8

In the UK, the ONS Management and Expectations Survey found that 69% of firms had adopted cloud-based computing systems and applications in 2023, against 61% for specialised software and 9% for artificial intelligence; of the firms using artificial intelligence, 91% also used cloud-based computing systems and applications.3 The survey sampled approximately 55,000 businesses between November 2023 and March 2024 and covers firms with at least 10 employees in production and services industries, excluding agriculture, forestry and fishing and financial and insurance activities.3 Neither survey therefore measures insurers' own use, and the two are not directly comparable: the ONS asked about cloud-based systems in general, Eurostat about paid cloud services.38

Is SaaS outsourcing? The UK regulatory position

The FCA's guidance FG16/5 states that where a third party delivers services on behalf of a regulated firm, including a cloud provider, this is considered outsourcing, and that the exact form of the service does not in itself alter the firm's regulatory obligations.2 Regulated firms "retain full responsibility and accountability" for discharging their regulatory responsibilities and cannot delegate any part of that responsibility to a third party.2 The guidance is not binding. It does not apply to banks, building societies, IFPRU investment firms or the payment and e-money institutions covered by the European Banking Authority's outsourcing guidelines, and the FCA states that it remains relevant to all other firms it authorises.29

Which requirements apply depends partly on whether an outsourced function is critical or important, or the outsourcing is material. As FG16/5 sets out, the FCA Handbook defines material outsourcing as outsourcing services of such importance that weakness or failure of the services would cast serious doubt upon the firm's continuing satisfaction of the threshold conditions or compliance with the Principles for Businesses.2

The PRA's SS2/21 applies to insurers and reinsurers within the scope of Solvency II, including the Society of Lloyd's and managing agents, as well as to banks, building societies and PRA-designated investment firms. Among its stated aims is to "facilitate greater resilience and adoption of the cloud and other new technologies". It was first published on 29 March 2021 and took effect on 31 March 2022; the current version has applied since 31 December 2024, and a further version takes effect on 18 March 2027.10 The PRA's Notifications rule requires all PRA-regulated firms to notify it when entering, or significantly changing, a material outsourcing arrangement, and the PRA expects the notification before the arrangement is entered into. It also expects firms to bring material non-outsourcing third party arrangements to its attention in a similar way.6

Operational resilience rules apply alongside. The FCA's rules in PS21/3, which apply to insurers among others, came into force on 31 March 2022, and firms had to be able to remain within their impact tolerances no later than 31 March 2025.11 The FCA states that the requirement to set and remain within impact tolerances remains the firm's responsibility whether or not it uses external parties to provide important business services.11

InstrumentIssued byStatusDateWhat it covers
FG16/5FCAGuidance, not bindingJuly 2016, updated September 2019Treats cloud services, including SaaS, as outsourcing where a third party delivers services on the firm's behalf; lists areas to consider from legal risk to exit2
PS21/3, operational resilienceFCARules and guidanceIn force 31 March 2022; within impact tolerances by 31 March 2025Firm stays responsible for remaining within impact tolerances when a third party supports an important business service11
SS2/21PRASupervisory statement setting out expectationsFirst published 29 March 2021; current version effective 31 December 2024Governance, due diligence, contracts, data security, access and audit, sub-outsourcing, business continuity and exit10
Notifications 2.3(1)(e), PRA RulebookPRARuleIn forceNotify the PRA when entering or significantly changing a material outsourcing arrangement6
PS26/2, material third party reportingFCA, in single regimes with the PRA and the Bank of EnglandRules and guidancePublished 18 March 2026; apply from 18 March 2027Notify the FCA of new or significantly changed material third party arrangements and submit a register of them each year; Solvency II firms are in scope12
PS16/24, critical third partiesBank of England, PRA and FCARules for third parties designated by HM TreasuryPublished 12 November 2024; rules effective 1 January 2025; designations under SI 2026/777 effective 13 July 2026Apply to a critical third party only from the date its designation comes into force1314
UK rules and guidance that apply when an insurer uses SaaS, with their status and dates

The material third party reporting rules require in-scope firms to notify the FCA of any new, or significantly changed, material third party arrangement and to keep a register of those arrangements, submitted to the FCA each year.12 Under the critical third parties regime, HM Treasury may designate a third party service provider only if, in its opinion, a failure in, or disruption to, its services to firms could threaten the stability of, or confidence in, the UK financial system. When the regulators published the regime in November 2024, HM Treasury had not designated any critical third parties.13 In the Critical Third Parties (Designation) Regulations 2026 (SI 2026/777), HM Treasury designated four cloud and technology providers as critical third parties with effect from 13 July 2026.14

The outsourcing life cycle regulators expect

FG16/5 is intended to help firms oversee the whole life cycle of an outsourcing arrangement, from the decision to outsource and the selection of a provider, through ongoing monitoring, to exit.2 SS2/21 sets out the PRA's expectations for each stage in more detail.6

The outsourcing life cycle as UK regulators describe it

1
Make and record the decision
A documented business case for using a provider for critical or important functions or material outsourcing, a risk assessment and an assessment of materiality early enough to notify the regulator.
2
Carry out due diligence
On the provider's business model, financial situation, capability, resources, ICT controls and security, and any sub-outsourced providers involved.
3
Agree a written contract
Covering access, audit and information rights, data security, sub-outsourcing, incident handling, termination rights and exit.
4
Tell the regulator
PRA-regulated firms must notify the PRA when entering into or significantly changing a material outsourcing arrangement, and the PRA expects notice before the arrangement is entered into.
5
Oversee the provider
Allocate responsibility for managing the provider, keep staff able to oversee and test the service, manage changes and test business continuity arrangements.
6
Plan and test the exit
A documented exit strategy that covers both a stressed exit, such as the provider's failure, and a planned exit for commercial or strategic reasons.
Source: FCA, FG16/5 (July 2016, updated September 2019); PRA, SS2/21 (November 2024 version).

For material outsourcing, the PRA expects due diligence to consider a provider's business model, complexity, financial situation, ownership structure and scale; its capability, expertise and reputation; its financial, human and technology resources; its ICT controls and security; and any sub-outsourced providers that will be involved in delivering important business services. It adds that a "general" track record of previous performance may not be sufficient evidence by itself.6

For material cloud outsourcing, the PRA expects firms to assess the resilience the service and data need and choose one or more cloud resiliency options, which may include multiple data centres across geographical regions, multiple active data centres in different availability zones within one region, a hybrid cloud, multiple or back-up vendors, and retaining the ability to bring data or applications back on-premises.6

Data protection and international transfers

Where a SaaS provider processes personal data on a firm's behalf, the UK GDPR treats the firm as the controller and the provider as a processor. Article 28 requires the controller to use only processors providing sufficient guarantees to implement appropriate technical and organisational measures. A processor may not engage another processor without the controller's prior specific or general written authorisation, and where it does, the same data protection obligations must be imposed on that sub-processor, and where that other processor fails to fulfil its data protection obligations, the original processor remains fully liable to the controller.15 Article 32 requires both the controller and the processor to implement security appropriate to the risk, including, as appropriate, pseudonymisation and encryption and the ability to restore access to personal data in a timely manner after an incident.16 FG16/5 reminds firms that data protection requirements are separate from FCA Handbook requirements, are overseen by the Information Commissioner's Office (since 30 September 2026, the Information Commission) and must each be met separately.217

A SaaS provider may store or process data outside the UK. Since 5 February 2026, Article 44A of the UK GDPR, inserted by the Data (Use and Access) Act 2025, has allowed a controller or processor to transfer personal data to a third country or an international organisation only if the transfer is approved by regulations under Article 45A, is made subject to appropriate safeguards under Article 46, or relies on a derogation for specific situations under Article 49, and is carried out in compliance with the rest of the regulation. A transfer relying on safeguards or a derogation may not breach a restriction in regulations under Article 49A.18 Article 83(5) sets fines of up to £17,500,000 or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher, for infringements that include breaches of the transfer provisions.19

UK and EU rules compared

For EU insurers, the European Insurance and Occupational Pensions Authority (EIOPA) published Guidelines on outsourcing to cloud service providers on 6 February 2020.20 They applied from 1 January 2021 to cloud outsourcing arrangements entered into or amended on or after that date (EIOPA's publication page gives 1 July 2021), and asked undertakings to review existing arrangements for critical or important functions by 31 December 2022.2120 EIOPA withdrew the guidelines with effect from 17 January 2025, stating that the Digital Operational Resilience Act (DORA) fully encompasses their objectives and provisions.22

DORA, Regulation (EU) 2022/2554, applies from 17 January 2025 and is directly applicable in all member states.23 A financial entity that uses ICT services to run its business remains fully responsible for complying with DORA and financial services law. Before contracting, it must assess whether the service supports a critical or important function, identify and assess the risks, including ICT concentration risk, and undertake due diligence on the provider.23

TopicUKEU
Main instrumentsPRA SS2/21, FCA FG16/5 and operational resilience rules, including the FCA's in PS21/310211DORA, Regulation (EU) 2022/2554; EIOPA's cloud guidelines until 17 January 20252322
Legal formSupervisory statement and non-binding guidance, alongside rules102An EU regulation, binding in its entirety and directly applicable23
Applies fromSS2/21 took effect on 31 March 20221017 January 202523
Register of arrangementsRegister of material third party arrangements, submitted to the FCA each year, from 18 March 202712Register of information on all contractual arrangements for ICT services, with a report at least yearly on new arrangements23
Telling the supervisor before contractingThe PRA expects notification before a material outsourcing arrangement is entered into6Inform the competent authority in a timely manner of any planned arrangement for ICT services supporting critical or important functions23
ExitThe PRA expects a documented and tested exit strategy for each material outsourcing arrangement, covering stressed and non-stressed exits6Exit strategies for ICT services supporting critical or important functions, with exit plans that are documented, tested and reviewed periodically23
Providers that serve the whole sectorCritical third parties regime, with designation by HM Treasury13An oversight framework for critical ICT third-party providers24
How the UK and EU regimes treat an insurer's use of SaaS and other third party technology

How SaaS is accounted for under IFRS

The IFRS Interpretations Committee considered a SaaS arrangement in an agenda decision published in April 2021. In the arrangement described, the customer's contractual right to receive access to the supplier's application software over the contract term did not provide a software asset, so the access was a service received over the term.25 The Committee observed that the customer often would not recognise an intangible asset for the cost of configuring or customising the software, because it does not control the software being configured or customised and that work does not create a separate resource it controls.25

SaaS in insurance systems

Insurance core systems, such as policy administration, claims and billing, can be delivered under any of these models; NIST states that its service and deployment models form a simple taxonomy that is not intended to prescribe or constrain any particular method of deployment or service delivery.1 Its definition allows a SaaS application to be reached through a program interface as well as a browser,1 which is the role an API plays when one system exchanges data with another; the definition does not specify how the application itself is built, whether as a single program or as microservices. FG16/5 asks firms to consider how easily a provider's services will interface with their internal systems or other third-party systems, and how service providers will work together, for example which one takes the lead systems integration role.2

A SaaS application can itself run on another provider's cloud infrastructure. SS2/21 notes that a firm may contract directly with a cloud provider that also provides services to software vendors the firm uses, and that the firm may then use its direct relationship to assess that provider's resilience for all the services it relies on.6 Moving from an installed system to SaaS can involve data migration, and the PRA gives a major migration programme as an example where it might be appropriate to notify it before a final provider has been selected.6

Show References Hide References
  1. National Institute of Standards and Technology. SP 800-145: The NIST Definition of Cloud Computing. September 2011.
  2. Financial Conduct Authority. FG16/5: Guidance for firms outsourcing to the 'cloud' and other third-party IT services. July 2016, updated September 2019.
  3. Office for National Statistics. Management practices and the adoption of technology and artificial intelligence in UK firms: 2023. Released 24 March 2025.
  4. National Cyber Security Centre. Cloud security shared responsibility model. Published 10 May 2022, reviewed 7 June 2023.
  5. National Cyber Security Centre. Using Software as a Service (SaaS) securely. Published 7 June 2023.
  6. Prudential Regulation Authority. SS2/21: Outsourcing and third party risk management. November 2024 version, effective from 31 December 2024.
  7. National Cyber Security Centre. The cloud security principles. Reviewed 7 June 2023.
  8. Eurostat. Cloud computing: statistics on the use by enterprises. Statistics Explained, data extracted January 2026.
  9. Financial Conduct Authority. FG16/5: Guidance for firms outsourcing to the 'cloud' and other third party IT services. First published 6 July 2016, last updated 18 March 2026.
  10. Prudential Regulation Authority. SS2/21: Outsourcing and third party risk management (publication page and versions). First published 29 March 2021.
  11. Financial Conduct Authority. PS21/3: Building operational resilience. March 2021.
  12. Financial Conduct Authority. PS26/2: Operational incident and third party reporting. 18 March 2026.
  13. Bank of England, Prudential Regulation Authority and Financial Conduct Authority. PS16/24: Operational resilience: Critical third parties to the UK financial sector. 12 November 2024.
  14. The Critical Third Parties (Designation) Regulations 2026. SI 2026/777. legislation.gov.uk, made 8 July 2026.
  15. UK GDPR. Article 28: Processor. legislation.gov.uk.
  16. UK GDPR. Article 32: Security of processing. legislation.gov.uk.
  17. UK GDPR. Article 4: Definitions. legislation.gov.uk.
  18. UK GDPR. Article 44A: General principles for transfers. legislation.gov.uk.
  19. UK GDPR. Article 83: General conditions for imposing administrative fines. legislation.gov.uk.
  20. European Insurance and Occupational Pensions Authority. Guidelines on outsourcing to cloud service providers (publication page). Read 10 November 2026.
  21. European Insurance and Occupational Pensions Authority. Guidelines on outsourcing to cloud service providers (EIOPA-BoS-20-002). Published 6 February 2020.
  22. European Insurance and Occupational Pensions Authority. EIOPA revokes previous guidelines to avoid duplications and overlaps with DORA. News, 19 December 2024.
  23. Regulation (EU) 2022/2554. Digital operational resilience for the financial sector (DORA). EUR-Lex. Read 10 November 2026.
  24. European Insurance and Occupational Pensions Authority. Digital Operational Resilience Act (DORA). Read 10 November 2026.
  25. IFRS Interpretations Committee. Configuration or Customisation Costs in a Cloud Computing Arrangement (IAS 38 Intangible Assets). IFRIC Update March 2021, agenda decision published April 2021.

Frequently Asked Questions

What is the difference between SaaS and on-premises software?

With on-premises software, the firm installs and runs the application on infrastructure it controls and looks after the operating system, servers and updates itself. With SaaS, the provider runs all of that. The NCSC's shared responsibility guidance advises customers to make their cloud provider responsible for applying security updates to all software their organisation did not write, and notes that the cloud provider will almost always be responsible for maintaining the availability and physical protections of its servers. It also points out that penetration testing, configuration checks and red team exercises will usually focus on the parts of a cloud service the customer has taken direct responsibility for.

The NCSC's guidance on using SaaS securely sets out actions for the customer, including managing user onboarding and offboarding, robustly authenticating users, protecting administration of the application, using trusted devices to access it, checking for malicious content, monitoring for security incidents and planning incident response and disaster recovery. It notes that some providers offer a trial and testing environment where configuration options can be tested without affecting the production tenancy.

Can an insurer use public cloud SaaS for a critical system?

UK regulators do not rule it out. The FCA's FG16/5 states that it sees no fundamental reason why cloud services, including public cloud services, cannot be implemented, with appropriate consideration, in a manner that complies with its rules. The PRA's SS2/21 says there is no hierarchy or one-size-fits-all combination of cloud resiliency options: the right choice depends on proportionality, on the materiality of the arrangement for important business services and on the relative costs and benefits, taking into account, for insurers, policyholder protection. Its example is a bank: if a significant firm wants to move its core banking platform to the cloud, the PRA may expect one or more of the most resilient options, while a less resilient but robust combination could suit a non-significant firm.

FG16/5 also deals with access and assurance. It quotes Article 274 of the Solvency II Regulation, which requires an insurer to have effective access to all information on outsourced functions, including on-site inspections of the provider's business premises. The FCA regards business premises as a broad term that does not necessarily include data centres, and accepts that providers may limit access to some sites for legitimate security reasons. It expects no restriction on the number of requests a firm, its auditor or the regulator can make for data, and says the regulator will not sign a non-disclosure agreement with the provider. Assurance from international standards such as the ISO 27000 series is, in its words, unlikely to be sufficient on its own for critical or important functions.

How are SaaS implementation costs treated in the accounts?

Under IFRS, the IFRS Interpretations Committee's April 2021 agenda decision distinguishes configuration, which sets flags or switches or defines values or parameters so the existing code works in a specified way, from customisation, which modifies the code or writes additional code. Where no intangible asset is recognised, the customer applies paragraphs 68 to 70 of IAS 38 and expenses the cost when it receives the service, which paragraph 69A defines as when the supplier performs it under the contract. If the software supplier performs the work and the service is distinct, the cost is expensed as the work is done; if it is not distinct from the right to access the software, it is expensed as access is provided over the contract term.

If a third party performs the configuration or customisation, the customer expenses the cost when that third party does the work, and a payment made in advance is recognised as a prepayment asset. An intangible asset can still arise in some circumstances, for example additional code from which the customer can obtain the economic benefits and restrict others' access, provided the code is identifiable and meets the recognition criteria in IAS 38. The Committee also pointed to paragraphs 117 to 124 of IAS 1, which require a customer to disclose its accounting policy for these costs when that is relevant to understanding its financial statements. The agenda decision followed a tentative decision published in the December 2020 IFRIC Update and applies to entities reporting under IFRS Accounting Standards.

What should a SaaS contract include for an insurer?

For EU insurers, Article 30 of DORA sets minimum contents for every contract for ICT services. The contract must give a clear and complete description of all the functions and services provided, and state the regions or countries where services are provided and data is processed, including the storage location, with advance notice from the provider of any change. It must provide for access to, recovery and return of personal and non-personal data in an easily accessible format if the provider becomes insolvent, enters resolution or discontinues its business, or the contract ends. It must also set out service levels, the provider's duty to help in an ICT incident at no extra cost or at a cost set in advance, its duty to cooperate fully with the authorities, and the conditions for its participation in the firm's security awareness and resilience training.

In the UK, where the provider processes personal data, Article 28 of the UK GDPR requires a contract that sets out the subject matter, duration, nature and purpose of the processing, the type of personal data and the categories of data subjects. It must stipulate that the processor acts only on the controller's documented instructions, including on transfers abroad, that its staff are bound by confidentiality, and that at the end of the service it deletes or returns all the personal data, at the controller's choice. Where a provider in a material outsourcing arrangement is unable or unwilling to agree terms that let the firm meet its regulatory obligations and expectations, the PRA's SS2/21 expects the firm to make the PRA aware of this.

What happens to an insurer's data if a SaaS provider fails or the contract ends?

The PRA's SS2/21 treats the stressed exit part of an exit plan, such as after the insolvency or liquidation of a provider, as a last resort risk mitigation strategy for disruption that other business continuity measures cannot manage. The PRA does not prescribe a form of exit; it focuses on the outcome, the continued provision of important business services, and expects firms to identify viable forms of exit, which may include bringing the data, function or service back in-house or on-premises, or transferring it to an alternative or back-up provider.

The FCA's FG16/5 expects firms to know how they would remove data from the provider's systems on exit and to have arrangements that give the regulator access to data in the event of insolvency or other disruption. Where resolution powers may be used, it says the provider and any subcontractor should agree that entry into resolution, or a resulting change in control, is not a termination event, and should agree not to delete, revoke, alter or change any data and to keep providing services to the firm for an appropriate transitional period after the resolution.

We'd rather show you than tell you.

We'll start by getting to know your business. Then we'll show you exactly how Genasys handles it.

Insurance People

Zero Fluff

Tailored to You