Many supplier contracts say the supplier "must maintain cyber insurance", yet that one line rarely says which cover, what limit, for how long or how anyone will check, so the protection is often weaker than it looks. When a supplier holding your data or running your service suffers an incident, its insurance can fund the response, the notifications and the claims that follow, but only if the right cover exists, is large enough, still applies after the contract ends and has not been voided by inaccurate answers to the insurer. This guide explains how to set cyber insurance requirements for suppliers: which suppliers need them, which parts of cover to ask for, how to size limits, what evidence to collect and how to word the clause. It is written for third-party risk, procurement, legal and security teams. Your own organisation's policy is covered in the Cyber Insurance Guide.
Key takeaways
- Insurance is a financial backstop, not a security control. The NCSC is plain that cyber insurance "will not prevent a cyber breach/attack", so it supplements supplier security requirements and never replaces them.
- Specify the cover parts, not just "cyber insurance". Ask for the sections that match the supplier's role: privacy and network security liability, regulatory cover, breach response costs and, for technology suppliers, professional indemnity or technology errors and omissions.
- Size limits to your exposure, not to a template figure. A limit that suits a stationery supplier is meaningless for a payroll bureau holding every employee's bank details.
- Time matters as much as amount. Most cyber policies are written on a claims-made basis, so require continuous cover during the contract and for a period after it ends.
- Evidence must be checked every year. A certificate collected at onboarding says nothing about whether the policy is still in force at the next renewal.
Why require suppliers to carry cyber insurance
When a supplier causes or suffers an incident that affects you, three kinds of cost arise: the supplier's own response and recovery, your response and recovery, and claims from people whose data or service was affected. A contract can allocate those costs through indemnities and liability caps, but an indemnity is only worth what the supplier can pay. For a small or mid-sized supplier, a serious breach can exceed its cash reserves, and insurance is often the only source of money behind the indemnity.
Insurance requirements also act as a signal. Cyber insurers ask detailed security questions at each renewal, and the NCSC notes that "If you're claiming that security measures are in place when they're not, the insurer may not be obliged to pay any claims." A supplier that can obtain cover has passed at least one external review, though insurer minimums are not a substitute for your own assessment; the NCSC also advises organisations not to limit themselves "to meeting the minimum cyber security requirements specified by an insurer."
Insurance does not cover everything. The NCSC warns that standard policies may not cover business email compromise fraud, and the US NAIC notes that "Most commercial property and general liability policies do not cover cyber risks." A supplier that points to its general liability certificate as proof of cyber cover usually has none.
Which suppliers need a requirement
Requiring cyber insurance from every supplier adds cost to small vendors and paperwork for you without much benefit. Tie the requirement to the supplier's risk tier, which your third-party risk process should already set. See the Third-Party Risk Management Guide.
| Supplier role | Why insurance matters | Typical requirement |
|---|---|---|
| Processes or stores personal or confidential data (payroll, CRM, marketing agency, data processor) | Breach notification, regulatory and compensation claims | Privacy and network security liability, regulatory cover, breach response costs |
| Holds privileged access to your systems (managed service provider, IT support, remote maintenance) | A compromise of the supplier can become your incident | Network security liability plus professional indemnity or technology errors and omissions |
| Provides software or a hosted service you depend on | Outage or defect causes your business interruption | Technology errors and omissions, network security liability |
| Delivers a critical service with no data or system access (logistics, facilities) | Their own outage stops your service | Usually a continuity requirement rather than insurance; see the Supplier Continuity Guide |
| Low-risk, no data, no access, easily replaced | Little exposure to transfer | No cyber insurance requirement |
Which parts of cover to ask for
Cyber policies are, in the NAIC's words, "highly customized for clients", so the name on the certificate tells you little. Ask for the sections that match the loss you are worried about. The US FTC groups cover into first-party (the policyholder's own losses) and third-party (claims brought by others). For a supplier requirement, the third-party sections usually matter most to you, because they respond when you or affected individuals claim against the supplier.
| Cover section | Type | What it responds to | Ask for it when |
|---|---|---|---|
| Privacy liability | Third-party | Claims arising from loss or disclosure of personal or confidential data | The supplier holds personal data |
| Network security liability | Third-party | Claims arising from a security failure, such as malware spreading to a customer or a breach of the supplier's systems | The supplier connects to your systems or hosts your data |
| Regulatory defence and penalties | Third-party | Regulator investigation costs and fines where insurable by law | The supplier processes regulated data |
| Breach response costs | First-party | Forensics, legal advice, notification, call centre and credit monitoring | You need the supplier to fund notification of individuals |
| Business interruption and data restoration | First-party | Supplier's own lost income and recovery costs | You need the supplier to stay solvent and recover quickly |
| Cyber extortion | First-party | Response to ransomware and extortion, subject to law and sanctions | The supplier runs systems critical to you |
| Professional indemnity or technology errors and omissions | Third-party | Claims that the supplier's service or software failed or was negligent, including non-breach failures | The supplier provides IT, software or hosted services |
Check the exclusions that most often defeat supplier claims: social engineering and funds transfer fraud, failure to maintain security controls declared at underwriting, war and state-backed attack wording, contractual liability assumed beyond what the law would impose, and prior known incidents. You will rarely see the full wording, so ask the supplier to confirm in writing that none of these removes cover for the services in your contract. See the Cyber Insurance Guide for how these exclusions work.
Sizing limits
There is no correct standard figure. Set limits by estimating what an incident at this supplier would cost you and affected parties, then deciding how much of that the supplier should fund. A simple, defensible method:
- Estimate data exposure: count the records and data types the supplier holds and use your own incident cost assumptions for notification, support and claims per record.
- Estimate service exposure: use the business impact analysis to estimate your loss per day if the supplier's service fails, multiplied by a realistic outage length.
- Compare with the liability cap: the insurance limit should be at least the supplier's liability cap for data protection and security breaches. A cap with no insurance behind it is a promise the supplier may not be able to keep.
- Check per-claim and aggregate limits: an aggregate limit is shared across all the supplier's customers in the policy year. If one incident hits many customers, your share may be small. Ask for the aggregate and whether defence costs erode it.
- Check sublimits and retentions: regulatory fines, extortion and breach response are often sublimited well below the headline figure, and the supplier pays the retention (excess) first.
- Be realistic for small suppliers: demanding a limit the market will not sell to a small supplier just removes good suppliers from your list. Accept a lower limit with tighter security conditions, or carry the residual risk in your own programme. See Cyber Insurance vs Self-Insurance.
A UK reference point shows why sizing matters. IASME's Cyber Essentials scheme includes cyber liability insurance for eligible UK organisations under GBP 20 million turnover that opt in, with a total limit of indemnity of GBP 25,000, an excess of GBP 1,000 and an exclusion for money stolen electronically; higher limits of GBP 100,000 or GBP 250,000 can be bought. That is useful baseline cover for the small business itself, but a supplier holding thousands of your customers' records would usually need much more to meet a meaningful indemnity.
Evidence: what to collect and check
Certificates of insurance are evidence that a policy existed on the date issued. They summarise cover; they do not change the policy, and the policy wording decides any claim. Treat them as a starting point.
| Evidence | What to check | When |
|---|---|---|
| Certificate or evidence of insurance from the insurer or broker | Insured entity name matches the contracting entity; cover sections; limits; policy period; insurer name | Onboarding and every renewal |
| Written confirmation of key terms | Claims-made or occurrence basis, retroactive date, territorial scope, sublimits for regulatory and breach response | Onboarding and when terms change |
| Insurer financial strength | Rating from a recognised agency at or above the level your policy sets | Onboarding and renewal |
| Notice of cancellation or material change | Supplier obligation to tell you within a set number of days | Contract clause, monitored continuously |
| Policy wording extract (high-risk suppliers only) | Exclusions that would apply to the contracted service | Onboarding |
Store evidence in the third-party risk record with the expiry date, and set a reminder 30 days before it. A missing renewal certificate should trigger follow-up exactly as an expired security attestation would. See the IT Service-Level and Operational Supplier Assurance guide for running ongoing evidence reviews.
Contract wording
The live Third-Party Security Contract Clauses Template carries a one-line insurance placeholder. For suppliers in the higher tiers, expand it into a full clause covering the elements below, and have legal align it with the liability and indemnity sections of the master agreement.
- Cover required: name the sections (for example privacy liability, network security liability, regulatory defence, breach response costs and technology errors and omissions) rather than "cyber insurance".
- Minimum limits: state per-claim and aggregate limits, and minimum sublimits for regulatory and breach response cover where these matter.
- Duration and tail: maintain cover for the term and for a set period after termination, or buy an extended reporting period, with a retroactive date no later than the contract start date.
- Insurer quality: placed with insurers authorised in the relevant jurisdiction and meeting a minimum financial strength rating.
- Evidence: provide a certificate on signature, at each renewal and on request.
- Notice: notify you of cancellation, non-renewal, reduction of limits or a material change in cover within a fixed number of days.
- Accuracy of disclosures: the supplier warrants that its declarations to insurers are accurate and will notify you if an insurer declines or reserves its position on a claim connected with your services.
- No limitation of liability: the insurance requirement does not cap the supplier's liability, and failure to insure does not reduce it.
- Subcontractors: material subcontractors handling your data or systems hold equivalent cover.
- Remedy: failure to maintain cover is a material breach, allowing you to suspend data flows or terminate.
Insurance practice varies by market: some requests common in other lines of insurance, such as naming you as an additional insured or a waiver of subrogation, may not be available on cyber policies. Ask the supplier's broker what can actually be endorsed before writing it into a non-negotiable clause.
Where identity fits
Insurers ask suppliers about multi-factor authentication, privileged access and backups, and the answers become conditions of cover. If a supplier's managed service accounts, API keys or remote access paths into your environment are weaker than it told its insurer, a claim connected with your services may be challenged. For suppliers with access to your systems, add the identity controls you rely on (phishing-resistant MFA on remote access, managed and rotated service account credentials, logged privileged sessions) to the security schedule, and ask for the same evidence their insurer asked for. See the Identity Controls for Cyber Insurance Questionnaires Guide.
Implementing supplier insurance requirements
- Set the standard: agree with legal, risk and procurement a short table of cover sections and minimum limits per supplier tier, and add it to the supplier security policy. See the Supplier Security Policy Template.
- Pilot on new contracts: apply the standard to new high-tier suppliers for one quarter and record how many could meet it, the time to obtain evidence and the exceptions requested.
- Adjust before scaling: lower limits or change cover sections where the market cannot supply them, and define an exception route with a named risk owner.
- Apply at renewal: add the clause to existing contracts as they renew, starting with suppliers holding the most sensitive data or privileged access.
- Automate tracking: record evidence and expiry dates in the third-party risk platform, with reminders and escalation.
- Use it in incidents: add a step to the incident response plan to notify the supplier, check its insurance position and preserve your claim rights when a supplier incident affects you. See Cyber Insurance Claims.
Roll back by tier rather than abandoning the requirement: if a tier's standard drives away essential suppliers, lower that tier's limits and strengthen its security conditions instead.
Decision guidance
- Large supplier with a strong balance sheet: its insurance matters less than its liability cap and indemnity terms; focus negotiation there and accept evidence of cover without wording reviews.
- Small supplier with high-risk data: insurance may be the only real funding behind the indemnity, so require it, but consider reducing the data it holds, since that lowers both the exposure and the limit needed.
- Small buyer organisation: a simple requirement (named cover sections, one limit, annual certificate) applied to the few suppliers holding your data is better than a complex standard nobody tracks.
- Large buyer organisation: tier the standard, automate evidence collection and report exceptions to the risk committee.
Detection and measurement
Monitor for lapses, not only for missing evidence at onboarding. Signals include certificates past expiry, an insurer changing at renewal, a reduced limit, and a supplier disclosing an incident or a declined claim.
| Metric | What good looks like |
|---|---|
| High-tier suppliers with current evidence of required cover | 100 percent, none past expiry by more than 30 days |
| Contracts in scope containing the full insurance clause | Rising each quarter as renewals occur |
| Open exceptions to the insurance standard with a named risk owner | All exceptions owned and reviewed annually |
| High-tier suppliers whose limit is below their liability cap for data breaches | Zero, or each accepted as an exception |
| Supplier incidents where insurance position was confirmed within the incident window | All supplier incidents affecting you |
Common failure patterns
- The general liability certificate: a supplier sends a standard liability certificate with no cyber sections, and nobody checks the cover listed.
- Wrong entity: the certificate names a parent or sister company, not the entity that signed the contract.
- Collected once: evidence obtained at onboarding expires and is never renewed, so the supplier has been uninsured for years without anyone noticing.
- No tail: the contract ends, the supplier cancels its claims-made policy, and a breach discovered six months later has no cover.
- Shared aggregate: a supplier serving hundreds of customers has a limit that one multi-customer incident would exhaust many times over.
- Assuming counterparties are insured: even large organisations may not carry cyber cover. Reuters reported in September 2025 that Jaguar Land Rover had not finalised a cyber insurance policy when its attack halted production; see the Jaguar Land Rover cyberattack. Verify, never assume.
Framework mapping
| Framework | Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.SC-05 | Supply chain requirements integrated into contracts and agreements |
| NIST CSF 2.0 | GV.SC-06, GV.SC-07 | Due diligence before entering relationships; supplier risk managed over the relationship |
| NIST CSF 2.0 | GV.RM-04 | Risk response options, including transfer, set and communicated |
| NIST SP 800-53 Rev. 5 | SA-4, SA-9, SR-6 | Acquisition process requirements, external system services, supplier assessments and reviews |
| ISO/IEC 27001:2022 Annex A | 5.19, 5.20, 5.22 | Supplier relationships, security in supplier agreements, monitoring and review of supplier services |
| UK GDPR and EU GDPR | Articles 28 and 82 | Processor contract terms; right to compensation from controllers and processors, which drives the liability that cover should fund |
Practitioner checklist
- Set insurance requirements by supplier tier, and require none for low-risk suppliers.
- Name the cover sections required, not just "cyber insurance".
- Size limits from data and service exposure, at least matching the data breach liability cap.
- Ask for per-claim, aggregate and key sublimits, and whether defence costs erode them.
- Require cover for the contract term plus a tail period, with a suitable retroactive date.
- Check that the insured entity on the certificate matches the contracting entity.
- Collect evidence at onboarding and every renewal, with expiry reminders.
- Require notice of cancellation, non-renewal or reduced limits.
- Confirm with the supplier's broker which endorsements are available before making them mandatory.
- Add a supplier insurance check to the incident response plan.
Standards and references
- NCSC: Cyber insurance guidance
- US Federal Trade Commission: Cyber insurance
- NAIC: Cybersecurity insurance topic
- IASME: Cyber Essentials cyber liability insurance
- NIST: Cybersecurity Framework 2.0
- NIST: SP 800-53 Rev. 5 Security and Privacy Controls
- NIST: SP 800-161 Rev. 1 Cybersecurity Supply Chain Risk Management Practices
Related NHI Mgmt Group resources: Third-Party Security Contract Clauses Template · Cyber Insurance Guide · Identity Controls for Cyber Insurance Questionnaires Guide · Supplier Security Policy Template