Why Cyber Insurance Claims Get Denied
Coalition found 64% of closed cyber claims in 2025 resolved with no out-of-pocket cost. Most claims pay. Here is what separates the ones that do not, and the five habits that close the gap.

Your vendor's security posture is part of yours. The 2026 Verizon DBIR found a third party involved in 48% of breaches, up from 30% a year earlier. Here is what to ask, what the answers mean, and what Massachusetts law expects.
When a vendor has access to your systems (your data, your APIs, your customer records), their security posture is your security posture. This isn't theoretical risk management. The 2026 Verizon Data Breach Investigations Report found that a third party was involved in 48% of breaches, up from 30% the year before. Two editions earlier, the 2024 Verizon Data Breach Investigations Report found that 15% of breaches involved a third-party component, up 68% from the prior year. The breaches didn't start inside those organizations. They started inside a vendor.
Most businesses, especially those under $50M in revenue, don't have a dedicated security team evaluating every tool and service provider. That's normal, but it doesn't mean vendor security is something you can ignore until you're bigger. The opposite is true: smaller organizations have less capacity to recover from a breach, which makes the supply chain attack surface disproportionately dangerous.
This article breaks down what vendor security posture actually means, what to ask, how to interpret the answers, and what the red flags look like in practice.
The short version: a vendor's security posture is how well its people, tools and policies protect the data and access you give it, and how quickly it reacts when something changes. Check it in proportion to what the vendor can touch, and check it more than once.
A vendor's security posture is the sum of their policies, practices, and controls for protecting data and systems. It includes how they handle authentication, how they encrypt data at rest and in transit, how they manage access internally, how they respond to incidents, and whether anyone is actually verifying that those practices hold up over time.
The term gets thrown around in sales conversations as if it's binary: either a vendor is "secure" or they aren't. In practice it's a spectrum, and the questions that matter are specific to what that vendor touches in your environment. A marketing analytics tool with read-only access to your website traffic has a different risk profile than a payroll processor with your employees' Social Security numbers and bank accounts.
The formal definition comes from the federal security glossary. NIST's glossary, drawing on CNSSI 4009, defines security posture as "the security status of an enterprise's networks, information, and systems based on information security resources (e.g., people, hardware, software, policies) and capabilities in place to manage the defense of the enterprise and to react as the situation changes." Two parts of that sentence matter when you apply it to a vendor. The first is resources: the people, tools and written policies the vendor really has. The second is the ability to react, which is why a vendor's security posture is something you check over time rather than once at signing.
You will also hear it called cybersecurity posture, security stance or, in NIST's own glossary, security status. They describe the same thing. Physical safeguards belong in it too. If a vendor keeps your paper files or servers on its own premises, locked rooms, visitor logs and badge access are part of its security posture.
Illustrative example: here is a security posture example from everyday vendor work. Picture two payroll vendors. The first enforces multi-factor authentication for every administrator, reviews staff access every quarter, shares a SOC 2 Type II report with two documented exceptions and their fixes, and commits in its contract to tell you within 72 hours of finding a breach. The second says it uses "bank-level security" and points you to a page on its website. Both might be careful companies, but you can only check the first one's security posture.
The first step is knowing what each vendor actually has access to. In a 2025 Ponemon Institute study of 1,942 IT and security practitioners, 50 percent said their organizations did not have a comprehensive inventory of all third parties with access to their networks. That gap is where risk lives.
You don't need a 300-question security assessment to evaluate a vendor. You need honest answers to a handful of specific questions. Here's what to ask and what the answers mean.
SOC 2 Type II means an independent auditor examined the vendor's security controls over a period of time (usually 6-12 months) and verified they were operating effectively. Type I is a point-in-time snapshot. Type II is ongoing evidence, and the distinction matters: a vendor who passed a Type I audit last March and hasn't been reviewed since is telling you what their security looked like on a single day over a year ago.
A passed audit and a hard-to-break system are different things, which is the gap between compliance and security.
If a vendor has a current SOC 2 Type II, ask to see the report. Specifically, look at the "exceptions" section. Every SOC 2 report has one. Zero exceptions is unusual and worth asking about. Multiple exceptions with documented remediation plans are normal. Multiple exceptions with no remediation timeline is a flag.
If a vendor doesn't have SOC 2 at all, that's not automatically disqualifying; the audit is expensive and many smaller vendors genuinely can't afford it yet. But it means you need to ask the remaining questions more carefully and assess their answers with less independent verification.
If you sit on the other side of this question, as a smaller vendor deciding whether to pursue the audit, Brian Gagne's guide on whether a small business needs SOC 2 explains when a security questionnaire is enough to show your security posture and when a CPA firm's examination is worth the cost.
This question has several layers. Where is the data stored geographically? Is it encrypted at rest? Is it encrypted in transit? Who inside the vendor's organization can access it, and under what conditions? Is it segregated from other customers' data, or is it commingled in a shared database?
The answer you want is specific. "We use AES-256 encryption at rest, TLS 1.2+ in transit, access is role-based with quarterly access reviews, and customer data is logically segregated per tenant." The answer you don't want is vague. "We take security very seriously and use industry-standard encryption." That sentence means nothing. It's marketing language, not a security posture.
When a vendor discovers a breach that affects your data, how quickly will they tell you? Some regulations mandate notification timelines (GDPR requires a controller to notify its regulator within 72 hours, and many U.S. state laws specify 30-60 days), but contractual obligations can be tighter than regulatory minimums.
Ask specifically: what is the notification timeline in your contract? Is the breach notification clause in their standard terms of service, or buried in a separate data processing agreement you haven't signed? If the vendor can't point you to a specific clause with a specific timeline, treat that as a gap.
Massachusetts puts a duty on the vendor as well. Under M.G.L. c. 93H, section 3(a), a business that maintains or stores personal information it does not own must notify the owner "as soon as practicable and without unreasonable delay" once it knows or has reason to know of a breach, and must cooperate with the owner afterward. Your contract can be more specific than the statute: a number of hours, a named contact, and what the vendor must report. Our guide to Massachusetts data breach notification requirements covers your own duties once the vendor calls.
Your vendor probably uses other vendors. Your CRM might use a third-party email delivery service. Your payroll provider might use a separate benefits administration platform. Each of those subprocessors has access to some portion of your data, and their security posture matters too.
Ask for a current list of subprocessors. Any vendor handling sensitive data should maintain one. If they can't produce it, they either don't track their own supply chain or don't want you to see it, and neither answer is reassuring.
Ask too how they tell you when the list changes, since every new subprocessor changes the security posture you signed up for. A good data processing agreement gives you notice before a new subprocessor gets your data, and a chance to object. The sub-processor problem goes deeper on why the list you saw at signing rarely stays the list.
You don't need a CISSP to identify warning signs. These are behavioral and organizational signals that correlate with weak security posture:
If you don't have a CISO or a dedicated security function, you can still evaluate vendor risk with a structured approach.
Use a simple vendor questionnaire. The Shared Assessments SIG Lite is a standardized questionnaire designed for exactly this purpose. It's shorter than a full SIG assessment, covers the essential domains, and gives you a framework so you're not guessing what to ask. Several free vendor risk assessment templates exist from organizations like NIST and SANS as well.
The SIG itself is licensed through Shared Assessments rather than free. If you want a no-cost federal starting point for judging supplier security posture, NIST's Quick-Start Guide for Cybersecurity Supply Chain Risk Management (SP 1305) walks through identifying your technology suppliers, ranking how critical each one is, and writing requirements for them into contracts.
Check public breach databases. The Have I Been Pwned database and the HHS breach portal (for healthcare-adjacent vendors) are free, public, and searchable. A vendor appearing in these databases isn't automatically disqualified, but it gives you a concrete question to ask: "What changed after this incident?"
Tier your vendors by access level. Not every vendor needs the same level of scrutiny. A vendor with access to your production database needs deep evaluation. A vendor whose SaaS tool stores your marketing calendar does not. Create three tiers based on data sensitivity and access scope. Focus your evaluation energy on the top tier.
Review contracts for security clauses. Look for data processing agreements, breach notification terms, liability limitations related to security incidents, and right-to-audit clauses. If a vendor's contract has no mention of security obligations, that's the biggest red flag of all: it means they haven't been asked often enough for it to become standard in their agreements.
The coordination cost of managing multiple vendors compounds here. Each additional vendor is another security relationship to evaluate, monitor, and maintain. Consolidation reduces risk as well as saving effort.
A security posture assessment is a structured review of how well an organization protects its systems and data, measured against a standard. For a vendor, a security posture assessment is the same review aimed at what that vendor can reach in your environment. It usually combines three sources of evidence: what the vendor tells you (a questionnaire and interviews), what an independent party has verified (a SOC 2 report, an ISO 27001 certificate, a penetration test summary), and what anyone can observe from outside (exposed services, expired certificates, past breach disclosures).
NIST published a guide for exactly this in July 2026. Its Due Diligence Assessment Quick-Start Guide (SP 1326) builds supplier assessments on five components: foreign ownership, control or influence; provenance; resilience; foundational cyber practices; and supply chain tiers. A small business does not need all five for its marketing tools. For the payroll processor or the IT provider with administrator rights, all five are fair questions about its security posture.
A workable security posture assessment for a top-tier vendor covers these points:
Much of the evidence arrives as long PDFs: SOC 2 reports, master agreements and data processing addenda. Qurtoo's walkthrough on prompting AI to pull red flags out of vendor documents shows how to get a first pass faster. A person still reads the exceptions section and the breach clause before anything is signed. For vendors that touch mixed data, client files alongside your own, the vendor security questions for mixed data environments go further.
Security ratings services score a company's security posture from information that anyone on the internet can observe. SecurityScorecard is one of the best known. It describes itself as a supply chain detection and response company that monitors and rates more than 12 million organizations, and its ratings explainer says it grades companies from A to F across ten groups of risk factors, using a "non-intrusive, outside-in view."
An outside score is a useful early signal about security posture. It can show that a vendor runs software with known vulnerabilities, lets certificates expire or has leaked credentials circulating. It cannot see inside: whether staff use multi-factor authentication, how access is reviewed, or whether backups would restore. Treat a rating as one input to a vendor's security posture, next to the questions above, and ask the vendor about any low grade before you draw a conclusion.
If your business holds personal information about Massachusetts residents, checking a vendor's security posture is a legal duty as well as good practice. 201 CMR 17.00, section 17.03(2)(f), requires your written information security program to "oversee service providers" by "taking reasonable steps to select and retain third-party service providers that are capable of maintaining appropriate security measures to protect such personal information consistent with 201 CMR 17.00 and any applicable federal regulations," and by "requiring such third-party service providers by contract to implement and maintain such appropriate security measures for personal information." The regulation counts any business that receives, stores, maintains, processes or otherwise has access to that personal information as a service provider.
Two parts of that text shape how you check a vendor's security posture. "Select and retain" means the check happens before signing and continues for as long as the vendor has the data. "By contract" means a verbal assurance does not meet the rule. Our guide to Massachusetts WISP requirements under 201 CMR 17 shows where vendor oversight sits in the written program, and contract flow-down of security obligations covers how those duties pass on to your vendors' own vendors.
Some businesses carry a federal version of the same duty. The FTC's Safeguards Rule, which reaches financial businesses such as tax preparers, mortgage brokers and auto dealers that arrange financing, adds a third step at 16 CFR 314.4(f)(3): "periodically assessing your service providers based on the risk they present and the continued adequacy of their safeguards." Employers that sponsor a 401(k) or health plan have the Department of Labor's cybersecurity program best practices, which the agency confirmed in 2024 apply to all ERISA plans.
Before AI, supply chain attacks were labor-intensive. An attacker needed to identify a vulnerable vendor, compromise their systems, understand the vendor's relationship to downstream targets, and then exploit that access, all manually. The SolarWinds attack in 2020 was devastating precisely because it was sophisticated and patient. Attackers spent months inside SolarWinds' build environment before distributing compromised updates to 18,000 organizations.
Now with AI, the economics of supply chain attacks have shifted. Attackers use automated scanning tools, increasingly augmented with machine learning, to identify vulnerable vendors at scale. Instead of manually probing one vendor at a time, automated systems can evaluate thousands of vendors' external attack surfaces simultaneously, identifying unpatched systems, misconfigured services, and exposed credentials.
The ENISA Threat Landscape for Supply Chain Attacks documented this shift: attackers are increasingly targeting the supplier rather than the customer because one successful vendor compromise can yield access to hundreds or thousands of downstream organizations. AI accelerates the reconnaissance phase (the part where attackers decide who to target), which means vulnerable vendors get found faster.
Verizon's newest data points the same way. In its May 2026 release, Verizon reported that exploiting software flaws, at 31% of breaches, passed stolen credentials as the most common way in for the first time in the report's 19 editions, and that AI is shrinking the defense window "from months to mere hours."
For businesses evaluating their vendor relationships, this means the window between a vendor developing a vulnerability and an attacker discovering it has compressed. Annual security reviews of vendors were already insufficient. In a landscape where automated scanning runs continuously, your vendor evaluation needs to account for how quickly a vendor detects, responds to, and communicates about threats, not just whether their controls looked good during last year's audit.
There is a newer question to add to every security posture review: does the vendor's AI connect to your systems? A scheduling tool that reads your inbox, or a support assistant that writes into your CRM, holds access the way a person would. Ask what that AI can read, change and send on your behalf, and who approves it. LTFI's guide to AI agent permissions explains how to scope that access and check it for drift.
The SolarWinds lesson for SMBs is that being a customer of the target is enough, so your attack surface covers every system that has a trusted connection to yours as well as your own.
Start with an inventory. List every vendor that has access to your systems, your data, or your customers' data. For each one, note what they can access and whether you've ever evaluated their security posture. Many businesses find that a good share of their vendor relationships have never been assessed at all.
Then tier that list by risk. Apply the questions above to your top-tier vendors first. You don't need to do this all in a week. One vendor per week, starting with whoever has the most sensitive access, builds a defensible program over a quarter.
If a vendor can't answer your questions (or won't), that's the most important data point of all. The willingness to be transparent about security practices is itself a signal about how seriously a vendor takes the trust you're extending to them.
Your security posture doesn't stop at your own walls. It extends to every system, every vendor, and every subprocessor that connects to yours. Managing that boundary is part of the cost of doing business with other businesses.
Vendor security posture is the sum of a vendor's policies, practices, and controls for protecting data and systems. It matters because when a vendor has access to your systems, their vulnerabilities become your vulnerabilities. The 2026 Verizon DBIR found that a third party was involved in 48% of breaches, up from 30% a year earlier. You don't need to be the target to be affected.
No. SOC 2 is expensive, and many smaller vendors haven't completed it. The absence of SOC 2 isn't disqualifying, but it means you need to evaluate their security practices through direct questions rather than relying on an independent audit. Tier your vendors by access level: those handling sensitive data or connecting to production systems should either have SOC 2 Type II or provide very specific, verifiable answers about their security controls.
Annual reviews are the minimum. For top-tier vendors (those with access to sensitive data or critical systems), quarterly check-ins on any changes to their security practices, subprocessor lists, or incident history are worth the time. Between reviews, monitor for public breach disclosures and changes to their terms of service or data processing agreements.
Type I evaluates whether a vendor's security controls are properly designed at a single point in time. Type II evaluates whether those controls actually operated effectively over a sustained period (usually 6-12 months). Type II is substantially more meaningful because it verifies that security practices are consistent, not just documented. Always ask for Type II if available.
Yes. The most important signals are behavioral, not technical: Does the vendor answer security questions willingly? Can they produce a subprocessor list? Do they have a breach notification clause in their contract? Do they support multi-factor authentication? These questions require no technical expertise and filter effectively. For deeper evaluation, standardized questionnaires like the SIG Lite provide structure without requiring you to design the assessment from scratch.
Document the specific gaps you identified and share them with the vendor. Give them a reasonable timeline to address the issues, 30-90 days depending on severity. If the gaps involve fundamental controls (no encryption, no breach notification policy, no access controls), begin evaluating alternatives immediately while working with the current vendor on remediation. Switching vendors has its own risks and costs, so replacement should be a parallel track, not a first reaction.
Security posture is the overall security status of an organization's networks, information and systems: the people, hardware, software and policies it has, plus its ability to defend itself and react as the situation changes. That wording follows NIST's glossary definition. For a vendor, it means how well those resources protect the data and access you give them.
Cybersecurity posture means the same thing as security posture. Some writers use it to stress the digital side (networks, cloud accounts, devices), while security posture can also include physical safeguards such as locked rooms and badge access. Either way, it describes how ready an organization is to prevent, detect and respond to an attack.
Common alternatives are cybersecurity posture, security stance and security status. NIST's glossary treats security status as a synonym of security posture. In vendor contracts and questionnaires you will also see "security program" or "information security controls" used for the same idea.
A payroll vendor that enforces multi-factor authentication for every administrator, reviews staff access quarterly, shares a current SOC 2 Type II report and commits to a 72-hour breach notice in its contract has a strong, checkable security posture. A vendor that only says it uses "bank-level security" has given you nothing to check.
A security posture assessment is a structured review of how well an organization protects its systems and data against a standard. For a vendor it combines a questionnaire, independent evidence such as a SOC 2 report, and what can be observed from outside. NIST's SP 1326 guide (July 2026) gives a five-part model for supplier due diligence.
SecurityScorecard is a security ratings company. It describes itself as a supply chain detection and response company, rates more than 12 million organizations, and grades each one from A to F across ten groups of risk factors scoring each organization's security posture from data it can see outside. Businesses use those ratings to screen vendors, though a rating cannot see a vendor's internal controls.
Put each security posture commitment in the signed agreement or its data processing addendum, not in a sales deck or a website page. Name the controls (multi-factor authentication, encryption, access reviews), a breach notice deadline in hours or days, a current subprocessor list with notice of changes, your right to request audit reports, and data return and deletion at exit. Massachusetts 201 CMR 17.03(2)(f) already requires the security clause for vendors holding residents' personal information.
Start with the Department of Labor's twelve cybersecurity program best practices for plan service providers. Ask whether the vendor's security posture includes a documented security program reviewed at least yearly, an annual third-party audit of its controls, access reviews at least every three months, phishing-resistant multi-factor authentication where possible, encryption of data stored and in transit, and a tested incident response plan. Then ask how it will notify you of a cybersecurity event.
Coalition found 64% of closed cyber claims in 2025 resolved with no out-of-pocket cost. Most claims pay. Here is what separates the ones that do not, and the five habits that close the gap.
Coalition put average global cyber claim severity at $116,000 for 2025, well under most policy limits. That means cyber insurance exclusions and sublimits, not the limit, decide what you collect.
Marsh recorded cyber rates down 4% globally in Q3 2026, the thirteenth straight quarterly decline, while underwriting evidence standards tightened. What a cyber insurance renewal application asks now, and the folder to have ready.
Work With Us
Kief Studio builds, protects, automates, and supports full-stack systems for businesses up to $50M ARR.
Newsletter
Strategy, psychology, AI adoption, and the patterns that actually compound. No spam, easy to leave.
Subscribe