Blog

Don't Guess "Yes": How a Wrong Answer on the Application Becomes a Denied Claim

A cyber-insurance application can feel like a quiz. The broker needs it back by Friday, the questions are full of terms you half-recognize, and every "no" seems likely to raise the premium. The temptation is to answer with confidence and sort out the details later.

That's the one habit I'd ask every owner to drop. Not because the forms are a trap, but because of what the forms actually say about themselves.

The application becomes part of the policy

Read the fine print on a few applications and you'll find language like this. Coalition states on its application that if a policy is issued, the application attaches to and becomes part of the policy. Cowbell's form says much the same. In other words, your answers aren't just how you got a quote. They're part of the contract.

Tokio Marine HCC's NetGuard Plus application is even more direct about multi-factor authentication (MFA, the second step beyond a password). A "yes" on MFA is a representation that it's already in force and will stay in force for the whole policy period.

A representation is a statement of fact the insurer relies on when deciding to cover you. If it turns out to be untrue, the insurer may have grounds to dispute or limit a claim. How that plays out depends on the policy wording and the law where you are, and that's a question for your broker and attorney, not for a blog. But the practical lesson doesn't need a lawyer: don't sign anything you haven't checked.

The question every form asks

In our review of 13 public carrier applications (November 2026), all 13 asked some version of: have you had an incident, and do you know of anything that could become a claim? Most look back about three years.

Several forms, including Coalition's, warn that if you know about a problem when you apply, a later claim arising from it won't be covered. That's standard insurance logic: you can't insure a house that's already on fire. It also means the question deserves a real answer. A phishing incident last spring that "turned out fine," or a vendor breach that touched your data, may be worth discussing with your broker before you answer.

Where honest companies get caught

When I ran IT at a company of about 200 people, I learned that wrong answers rarely come from dishonesty. They come from reasonable people answering a slightly different question than the one asked. A few examples of what that looks like:

  • "Do you require MFA for remote access?" Answered yes because employees use MFA on the VPN, while the IT vendor's remote-support tool doesn't require it.
  • "Are backups kept offline or isolated?" Answered yes because backups go "to the cloud," when the cloud copy is reachable with the same administrator password as the office network.
  • "Do you conduct annual security training?" Answered yes because there's a training platform, but nobody has checked completion since last year.
  • "Do you have EDR on all endpoints?" Answered yes because there's security software on the laptops, while two servers were excluded years ago.

Each of those is a "yes" given in good faith, and each would be hard to defend after an incident.

A slower, better habit

The fix is boring, and it works:

Answer only what you can show. For every "yes," you should be able to point to evidence: a screenshot of a setting, a report from a tool, a letter from your provider, a training completion record, a dated restore test.

Treat "I'm not sure" as "not yet." If you can't confirm a control, mark it as a gap and talk to your broker. A carrier would generally rather hear "MFA is on for email and in progress for remote access, completing next month" than discover the truth later.

Fix what you find. Many gaps the application exposes are a few hours of work for your IT provider. Close them before signing when you can.

Keep a dated record. Controls drift. People leave, providers change, settings get switched off during a troubleshooting session and never switched back on. A record that shows what was true on what date protects you, your broker and your carrier.

Why "living" evidence matters

What protects you isn't a one-time yes. It's a dated record that shows what was checked, when, and that it's still being checked. A broker can rely on it, a big customer can rely on it, and you can sign the application knowing what's behind each answer.

You don't need special software to start. A shared folder with screenshots and dates, updated quarterly, is a perfectly good beginning.

Talk to your broker early

Your broker is on your side and has seen these forms many times. If a question is unclear, ask what the carrier means. If you have a gap, ask how to present it honestly. Bringing the gaps to the conversation early is almost always better than having them discovered later.

What to do Monday morning

  1. Get the actual application your broker is circulating for this renewal, not last year's copy.
  2. Highlight every "yes." Next to each one, write the evidence you'd show: a screenshot, a setting, a vendor letter, a training report or a restore-test date.
  3. Where there's no evidence yet, change the answer to "no" or "in progress," or fix the gap before signing.
  4. Review the "known incidents" question carefully, and discuss anything borderline with your broker.
  5. Start an evidence folder with today's date on it, and add to it every quarter.

All essays