Service level agreement
Service levels are usually a schedule to another agreement; availability and recovery commitments here are what a resilience regime reads.
How the register reads it
| Also called | SLA, service level schedule |
|---|---|
| Family | Services, SOWs, outsourcing and managed services |
| Normally carries | Auto-renewal. |
| ICT service arrangement | Yes: DORA Art. 28 to 30 and CPS 230 para 53 read it, and a security schedule is expected by the regimes that ask for one. |
What each customer's regimes expect of it
six customers, personal data namedOn a register, the regimes are pulled on by the customer's sector and country; the terms are the checklist boxes the row is read against. Clause text from The Art of Service standards library at compliance.theartofservice.com, read against the published text of each standard and cited to its clause: our close statement of each clause, not the instrument verbatim. Where the UK text is covered only as a summary, the EU GDPR article of the same number is quoted and the page says so.
The clauses, quoted
35 across the six customersCCPA 1798.100(d) Put an agreement in place with every recipient of personal informationA business that sells or shares data with a third party, or hands data to service providers or contractors for business purposes, must have an agreement that limits the data to specified purposes, binds the recipient to the Act and to the same level of protection, lets the business take reasonable steps to check compliant use, requires the recipient to say if it can no longer c...
Where it usually falls short: Advertising and analytics partners on click-through terms with no CCPA clauses
CCPA/CPRA and its regulations in The Art of Service standards library
CCPA 1798.100(e) Maintain reasonable security for personal informationA business that collects personal information must run security procedures and practices suited to the nature of the data, so that it is not accessed, destroyed, used, altered or disclosed without authority or unlawfully, as section 1798.81.5 requires. A breach of nonencrypted or nonredacted data caused by a failure of this duty exposes the business to consumer suits for statut...
Where it usually falls short: Personal information held unencrypted in backups, exports or test environments
CCPA/CPRA and its regulations in The Art of Service standards library
CCPA CCR 7051 Service provider and contractor contract termsThe contract must bar selling or sharing, name the specific business purposes (not by reference to the contract as a whole), bar use outside those purposes and outside the direct relationship, require compliance with the Act and the same level of protection (for example help with audits, risk assessments, ADMT duties and security under 1798.81.5), give the business rights to ch...
Where it usually falls short: Purposes described as the services under the agreement
CCPA/CPRA and its regulations in The Art of Service standards library
CPS 230 para 32 Notify APRA within 72 hours of a material operational risk incidentClock: as soon as possible, and at the latest 72 hours from the time the entity becomes aware. Trigger: an operational risk incident the entity has determined is likely to cause a material financial impact, or to materially affect its ability to keep its critical operations running. An information security incident already notified to APRA under CPS 234 need not be notified aga...
Where it usually falls short: Clock started from incident closure rather than from awareness
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 41 Notify APRA within 24 hours of a disruption outside toleranceClock: as soon as possible and no later than 24 hours after a critical operation is disrupted beyond its tolerance. The notification to APRA must describe the nature of the disruption, what action has been taken, the likely effect on business operations and the expected timeframe for getting back to normal operations.
Where it usually falls short: Notification waits until the disruption is resolved
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 49 Minimum material service provider classifications unless justifiedUnless it can justify otherwise, the entity must at least treat providers of these services as material: for an ADI, mortgage brokerage, credit assessment, and funding and liquidity management; for an insurer, insurance brokerage, reinsurance, underwriting and claims management; for an RSE licensee, custodial services, fund administration, investment management, and arrangement...
Where it usually falls short: Core technology services interpreted narrowly, leaving cloud providers out
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 53 Formal legally binding agreement for each material arrangement and its minimum termsFor every material arrangement the entity must hold a formal, legally binding agreement that at least: (a) defines the services and their service levels; (b) sets each party's rights, duties and expectations, including asset ownership, data ownership and control, dispute resolution, audit access, indemnity and liability; (c) lets the entity satisfy its legal and compliance obli...
Where it usually falls short: Agreement lacks subcontractor notification or force majeure carve-outs
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 54 APRA access, on-site visit and non-impediment clausesThe formal agreement must also provide that (a) APRA can access documentation, data and other information about the service; (b) APRA may visit the provider on site; and (c) the provider undertakes not to obstruct APRA in performing its prudential regulator duties. Para 57 can exempt the arrangement (Attachment category provider on standardised terms or no formal agreement), an...
Where it usually falls short: Cloud or SaaS terms accepted without APRA access rights and no exemption analysis
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 230 para 60 Notify APRA of critical-operation agreements (20 business days) and before material offshoringClocks: (a) as soon as possible and within 20 business days of signing, or materially changing, an agreement for a service the entity relies on to carry out a critical operation; and (b) before entering into any material offshoring arrangement, or when a significant change to such an arrangement is proposed, including where personnel or data used for the service will sit offsho...
Where it usually falls short: Offshoring notified after go-live
APRA CPS 230 Operational Risk Management in The Art of Service standards library
CPS 234 para 16 Assess the security capability of related and third partiesWhere a related party or third party manages any of the entity's information assets, the entity assesses that party's information security capability, to a depth that matches the possible consequences of an incident touching those assets. A footnote makes this apply to every such party, not only those supplying outsourced material business activities covered by CPS 231 or SPS 2...
Where it usually falls short: Assessment limited to material outsourcing arrangements, missing SaaS and other parties that hold data
APRA CPS 234 Information Security in The Art of Service standards library
CPS 234 para 22 Evaluate the design of third-party controlsWhere a related or third party manages the entity's information assets, the entity evaluates how that party's security controls protecting those assets are designed. A footnote confirms this reaches every such party, not only CPS 231 or SPS 231 material outsourcing.
Where it usually falls short: Accepting a certificate or report without reading its scope or exceptions
APRA CPS 234 Information Security in The Art of Service standards library
CPS 234 para 34 Internal audit assessment of third-party assuranceInternal audit has to assess the security control assurance a related or third party provides where both hold: (a) an incident affecting the assets could have a material financial or non-financial effect on the entity itself or on the interests of its depositors, policyholders, beneficiaries or other customers (the materiality limb); and (b) internal audit plans to rely on that...
Where it usually falls short: Internal audit accepts third-party reports without any evaluation
APRA CPS 234 Information Security in The Art of Service standards library
CPS 234 para 35 Notify APRA of material incidents within 72 hoursThe entity must tell APRA promptly, and at the latest within 72 hours of becoming aware, of any information security incident that either (a) had, or could have had, a material financial or non-financial effect on the entity itself or on the interests of its depositors, policyholders, beneficiaries or other customers (the impact limb), or (b) has already been notified to anothe...
Where it usually falls short: Clock started at confirmation of the incident instead of awareness
APRA CPS 234 Information Security in The Art of Service standards library
DORA Art. 19 Reporting of major ICT-related incidentsFinancial entities report major ICT-related incidents to their single designated competent authority (significant credit institutions report to the national authority, which passes the report to the ECB), using the Article 20 templates, with an alternative channel where a technical problem blocks the initial notification; Member States may also require copies to NIS2 authoritie...
Where it usually falls short: Awareness time not captured, so the 24-hour limit cannot be shown
DORA (Regulation (EU) 2022/2554) in The Art of Service standards library
DORA Art. 28 ICT third-party risk: general principlesFinancial entities manage ICT third-party risk as part of ICT risk inside the ICT risk management framework, remain fully responsible for their obligations when they use ICT services, and apply proportionality according to the nature and importance of ICT dependencies and the criticality of each service. They keep a register of information on all ICT service arrangements at ent...
Where it usually falls short: Register omits intra-group or low-value ICT arrangements
DORA (Regulation (EU) 2022/2554) in The Art of Service standards library
DORA Art. 30 Key contractual provisionsContracts set out the rights and obligations of both parties in one written document, available on paper or another durable, downloadable format, including the service levels. Every ICT services contract covers at least: the functions and services and whether and how subcontracting is permitted; service and data processing locations, with advance notice of changes; data protect...
Where it usually falls short: Contract silent on data location changes or data return on termination
DORA (Regulation (EU) 2022/2554) in The Art of Service standards library
GDPR Art. 28 ProcessorUse only processors providing sufficient guarantees to implement appropriate technical and organisational measures such that the processing meets the Regulation's requirements and protects the rights of the data subject. A processor must not engage another processor without the controller's prior specific or general written authorisation, and under a general authorisation must ...
Where it usually falls short: The processor's own standard terms accepted, which commonly omit the audit right, the deletion choice and the instruction infringement notice
GDPR (Regulation (EU) 2016/679) in The Art of Service standards library
GDPR Art. 33 Notification of a personal data breach to the supervisory authorityOn becoming aware of a personal data breach, notify it to the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons; a notification made later than 72 hours must be accompanied by the reasons for the delay. A processor ...
Where it usually falls short: The awareness clock started at the end of the investigation rather than at the point of reasonable certainty that a breach had occurred
GDPR (Regulation (EU) 2016/679) in The Art of Service standards library
HIPAA 164.308(a)(6)(ii) Response and Reporting (Required)Identify and respond to suspected or known incidents, mitigate harmful effects, and document incidents and their outcomes. NIST recommends linkage to HIPAA Breach Notification Rule timelines.
Where it usually falls short: Incident closure without root cause
HIPAA Security Rule in The Art of Service standards library
HIPAA 164.314(a)(2)(i) Business Associate Contract Required ProvisionsThe contract between a covered entity and a business associate must provide that the business associate will comply with the applicable Security Rule requirements, ensure subcontractors comply, report security incidents including breaches, and authorize termination by the covered entity if the business associate violates a material term.
Where it usually falls short: Incident reporting SLA missing or longer than reasonable
HIPAA Security Rule in The Art of Service standards library
ISO 27001 A.5.19 Information security in supplier relationshipsDefine and apply processes to manage the security risk suppliers introduce.
Where it usually falls short: Treating all suppliers as low risk
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.20 Addressing information security within supplier agreementsEstablish and agree the relevant security requirements in each supplier contract.
Where it usually falls short: missing explicit security clauses
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.21 Managing information security in the ICT supply chainExtend security requirements down the ICT products and services supply chain.
Where it usually falls short: Treating supplier security as one-off check
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.24 Information security incident management planning and preparationDefine incident roles, processes and readiness before an incident happens.
Where it usually falls short: roles are defined but not formally assigned or approved
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.31 Legal, statutory, regulatory and contractual requirementsIdentify, document and keep current the legal and contractual obligations relevant to security, and your approach to meeting them.
Where it usually falls short: outdated legal register
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27001 A.5.34 Privacy and protection of personal identifiable information (PII)Identify and meet privacy and PII-protection requirements from law, regulation and contract.
Where it usually falls short: Missing documented consent for all data subjects
ISO/IEC 27001:2022 in The Art of Service standards library
ISO 27701 A.2.4.3 Return, transfer or disposal of PIIThe organization must provide the ability to return, transfer or dispose of personal data securely and must make its policy available to the customer, managing the capability securely whether the outcome is return to the customer, transfer to another organization or controller, deletion, destruction, de-identification or archiving, providing the assurance the customer needs tha...
Where it usually falls short: Erasure certified for primary systems while backups retain the data for the full backup cycle, which the customer is not told
ISO/IEC 27701:2025 in The Art of Service standards library
ISO 27701 A.3.10 Addressing information security within supplier agreementsAgreements with suppliers shall specify whether PII is processed and the minimum technical and organizational measures the supplier must meet for the organization to meet its information security and PII protection obligations, shall clearly allocate responsibilities between the organization, its partners, suppliers and applicable third parties taking account of the type of PII...
Where it usually falls short: Supplier contracts silent on PII while the supplier processes it
ISO/IEC 27701:2025 in The Art of Service standards library
ISO 27701 A.3.12 Response to information security incidentsFor a PII controller, an incident that involves PII shall trigger a review to determine whether a breach involving PII requiring a response has occurred, an event alone not necessarily triggering it; when a breach has occurred the response shall include the relevant notifications and records, jurisdictions defining when the supervisory authority and PII principals must be notif...
Where it usually falls short: Incidents closed as security events with no PII breach determination
ISO/IEC 27701:2025 in The Art of Service standards library
NIS2 Art. 21(2)(d) Supply chain security, covering the relationship with each direct supplier and service providerThe Directive scopes this deliberately at direct suppliers and service providers, which makes the first artefact an inventory of who those parties are and which of them touch the network and information systems behind the service. From there the entity has to manage the security-related aspects of each relationship: what the supplier may access, what security obligations bind i...
Where it usually falls short: Inventory built from the procurement system, so shadow and free-tier services are missing
NIS2 Directive (Directive (EU) 2022/2555) in The Art of Service standards library
NIS2 Art. 21(3) Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessmentsDeciding what supply chain measures are appropriate is not left to general judgement. The entity has to take into account the vulnerabilities specific to each direct supplier and service provider, and the overall quality of those parties' products and cybersecurity practices including their secure development procedures. Separately, it must take into account the results of the ...
Where it usually falls short: Supplier assessment reduced to a questionnaire score with no view of that supplier's actual weaknesses
NIS2 Directive (Directive (EU) 2022/2555) in The Art of Service standards library
NIS2 Art. 23(1) Notify significant incidents to the CSIRT or competent authority, and warn affected service recipientsThe core reporting duty attaches to any incident with a significant impact on the provision of the entity's services. Article 23(3) fixes the threshold: an incident is significant if it has caused or is capable of causing severe operational disruption of the services or financial loss for the entity, or if it has affected or is capable of affecting other natural or legal person...
Where it usually falls short: Threshold applied only to realised impact, so contained incidents capable of severe disruption go unreported
NIS2 Directive (Directive (EU) 2022/2555) in The Art of Service standards library
NIS2 Art. 23(4)(a) Submit an early warning within 24 hours of becoming aware of a significant incidentThe first stage of the layered reporting regime falls due without undue delay and in any event within 24 hours of becoming aware of the significant incident. The early warning is deliberately light: where applicable it indicates whether the incident is suspected of being caused by unlawful or malicious acts, and whether it could have cross-border impact. It is not a full assess...
Where it usually falls short: Awareness treated as the moment of executive briefing rather than of qualified detection
NIS2 Directive (Directive (EU) 2022/2555) in The Art of Service standards library
NIS2 Art. 23(4)(b) Submit an incident notification within 72 hours, with an initial assessment and indicators of compromiseWithin 72 hours of becoming aware, the entity updates the early warning and provides an initial assessment of the significant incident covering its severity and impact, together with indicators of compromise where those are available. The 72 hours runs from awareness, not from the early warning, so the two clocks start together. Trust service providers are held to a shorter dea...
Where it usually falls short: 72 hours counted from the early warning rather than from awareness
NIS2 Directive (Directive (EU) 2022/2555) in The Art of Service standards library
UK GDPR Arts. 24 to 43 Controller and Processor (Articles 24-43)Per UK GDPR Articles 24-43: controller + processor + DPO + RoPA + DPIA + Privacy by Design + Records + breach notification.
Where it usually falls short: DPO + DPIA + ICO partial
UK GDPR (summary of the articles held) in The Art of Service standards library
Read every agreement on your list
Paste the list of customer agreements and each one comes back with the regimes its customer pulls on, the terms ticked or open, the clock, the audit right and the renewal. Eight agreements free, no account.
Check my contract list