Letter of intent or heads of terms
Usually not binding on the service terms; the register records it so the terms that were promised early are on the list.
How the register reads it
| Also called | LOI, heads of terms, term sheet |
|---|---|
| Family | Confidentiality and pre-contract |
| Normally carries | None of the usual schedules. |
| ICT service arrangement | No: the DORA and CPS 230 terms and the security schedule are not expected of it. |
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
18 across the six customersCCPA 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
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 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
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.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 27001 A.6.6 Confidentiality or non-disclosure agreementsIdentify, document, review and sign NDAs that reflect the organization's protection needs.
Where it usually falls short: NDAs not refreshed when data classification changes
ISO/IEC 27001:2022 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
ISO 27701 A.3.18 Confidentiality or non-disclosure agreementsIndividuals operating under the organization's control with access to PII shall be subject to a confidentiality obligation, the agreement, whether part of a contract or separate, specifying the length of time the obligation lasts; when the organization is a PII processor, the confidentiality agreement in whatever form between the organization, its employees and its agents shall...
Where it usually falls short: Confidentiality obligation that ends at termination when the PII obligation does not
ISO/IEC 27701:2025 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