Request a quote
Emergency SectorsCareers About us Blog Get in touch
Close-up of two monitors showing log lines and coloured terminal output

Cyber insurance for small business: the IT controls the insurer asks about

Cyber insurance for small business starts with a proposal form, and almost all of it is about your IT. The person who signs it is usually a director or the finance lead; the person who knows the answers is whoever runs your systems. This piece covers what gets asked, how to read a question that starts with “all”, and what to keep on file so your answers still stand when you make a claim.

6 min read Written by the ITproposal team
Short answer

A cyber insurance proposal form is a short audit of your IT: MFA, backups, patching, EDR, admin rights, email security, an incident plan and staff awareness.

The costly answers are not the false ones but the optimistic ones: “yes” because that is the policy, while the practice has an exception that a post-incident investigation will find.

Keep dated evidence for each answer when you fill it in, and read what the policy expects of you in an incident before you have one.

What cyber insurance for small business asks of your IT

The proposal form for cyber insurance is, at heart, a risk assessment. The insurer wants to know two things: how likely an attack is to succeed against you, and how quickly you are running again if one does. That is why nearly every question covers the same handful of controls, whichever insurer you approach.

Two things make it harder than it looks. The questions are framed as yes or no, while the honest answer in most organisations is “yes, except”. And the person signing is rarely the person who knows how things actually stand.

So treat the form as a short audit rather than paperwork, with whoever manages your IT in the room. An hour together costs less than an answer that later turns out to be wrong.

The eight topics that come up almost every time

  • MFA. On email, on remote access (VPN, remote desktop, web portals) and on admin accounts. Watch the word “all”: one old service account or a shared mailbox without a second factor makes that answer untrue.
  • Backups. Separated from the network, offline or immutable, with credentials that differ from everything else. The follow-up is usually whether you test restores, and when you last did. A backup that the same admin account can delete as your servers is not separated as far as an attacker is concerned.
  • Patching. How quickly critical updates are installed on laptops, servers and network equipment. Firewalls and VPN appliances are the ones that tend to fall through the gaps.
  • EDR. Endpoint detection and response on every device and server, and the follow-up that matters: who looks at the alerts, including at night and at weekends? That last part is exactly what managed security covers.
  • Admin rights. Do users work without local admin rights, do administrators use a separate account for admin work, and how many of those accounts exist?
  • Email security. Filtering of attachments and links, SPF, DKIM and DMARC on your domain, and sometimes a banner on external mail.
  • Incident response plan. A written plan with names and phone numbers that still works if the systems it lives on are encrypted, and whether you have rehearsed it.
  • Awareness. Training and phishing simulations, how often, and whether new starters go through them when they join.

In the UK, several of these overlap with Cyber Essentials, the NCSC-backed scheme, so if you hold it, much of the groundwork is already documented. Some forms also ask about systems that no longer receive updates, about an asset inventory and about who has remote access from outside, such as suppliers with a support tool.

Why an inaccurate answer is expensive at claim time

When you take out commercial insurance in the UK, the Insurance Act 2015 gives you a duty of fair presentation: you tell the insurer what you know, or ought to know, that matters to its decision. What follows from an inaccurate answer depends on the law, the policy and the circumstances, and that judgement belongs with your broker or a lawyer.

What is technical is this: after an incident there is usually an investigation into how the attacker got in, and it exposes exactly the things the form asked about. If they came in through a VPN account without a second factor while you ticked “yes” to MFA on all remote access, it will be in the report in black and white.

The costly answers are not the false ones but the optimistic ones. “Yes” because that is the policy, while the practice has an exception. MFA is on, except for the scanner’s account. Patches go out within two weeks, except on the firewall that is still on the list.

So be precise rather than positive. If the honest answer is “yes, with this exception”, write the exception down and submit it. An exception the insurer knew about is a different conversation from one it reads in an investigation report.

How to read a question before you answer it

  • Scope. “All users”, “all endpoints”, “all remote access”. Count what falls under it, including service accounts, shared accounts, supplier accounts and the laptop the managing director keeps at home.
  • Timing. Is the question about today or about the start date of cover? A control that will be finished next month is not a yes today. Say it is planned, and give the date.
  • Definitions. “Offline”, “segregated”, “immutable” and “monitored 24/7” do not mean the same to everyone. Ask through your broker if it is unclear, and keep the answer.
  • Ownership. Every question needs one name: someone who can show the answer is true. No name usually means no evidence either.

Start well before the renewal date. Whatever is not right by then can still be fixed rather than explained.

How to keep the evidence ready

An answer is only worth something if you can show it. When you fill in the form, build a folder with the document that supports each answer, dated on the day you completed it.

  • MFA: an export of the sign-in policies and the second-factor status for each account, with the exceptions and the reason for each.
  • Backups: the settings that show the copy is separated or immutable, and the record of the last restore test: what, when and how long it took.
  • Patching: a patch status report for laptops and servers, plus the firmware versions of firewall and VPN.
  • EDR: the number of managed devices next to the number with an active agent. If the two do not match, you know where to look.
  • Admin rights: the list of accounts with admin rights, with an owner for each.
  • Email: the DNS records for SPF, DKIM and DMARC and a recent DMARC report.
  • Incident plan and awareness: the plan with the date of the last exercise, and attendance at training and simulations.

Do not do this once. The same form comes back at renewal, and a folder that is updated every year is also the first thing you reach for when something goes wrong.

What is expected of you during an incident

The policy sets out what you must do when it happens, and it is worth reading before an incident rather than during one. A few points appear in many policies.

  • Report quickly, to the number or service named in the policy. Put that number in your incident plan, on paper as well, because your email may not be working.
  • Check before you bring in outside firms. Many insurers work with their own specialists for investigation and recovery, or want to agree in advance. Read what your policy says about it.
  • Preserve evidence. Do not wipe and reinstall straight away: isolate the affected systems, keep the logs and make notes with times. The investigation can only find what is still there.
  • Do not pay or negotiate a ransom without talking to the insurer.

Your legal obligations carry on regardless. If personal data is involved, a reportable breach goes to the ICO within 72 hours, and that clock does not wait for the insurer.

Where our work stops

What we do. The controls the form asks about: setting up MFA, separating backups and testing restores, patching, rolling out EDR and following up the alerts, cleaning up admin rights and securing email. And the technical facts: for each question, what is actually in place, with the export, report or list that shows it, exceptions included.

What we do not do. We are not an insurer and not a broker. We do not advise on which policy to choose, what is covered or what a clause means; that is for your broker or the insurer. And we do not complete or sign the proposal form on your behalf: the answers are a statement from your organisation to the insurer, and they should come from someone entitled to make it. We make sure what you write matches what is there.

Frequently asked

Questions we get about this

The ones that come up most often as renewal approaches.

What IT security do insurers require for cyber insurance?

Forms differ between insurers, but the same topics come up almost every time: MFA on email, remote access and admin accounts, a separated or offline backup with tested restores, a patching policy, EDR on devices and servers, limited admin rights, email security, an incident response plan and staff awareness training. The requirements for your policy are in that insurer’s form and wording.

Do you need MFA to get cyber insurance?

MFA appears on almost every proposal form, particularly for email, remote access and admin accounts. Whether it is a condition of your policy is up to the insurer. When you answer, check the scope of the question: if it says “all”, one account without a second factor makes the answer inaccurate.

What happens if the cyber insurance questionnaire is filled in wrongly?

Under the duty of fair presentation you must tell the insurer what matters to its decision, and an inaccurate answer can have consequences when you claim. How serious they are depends on the law, the policy and the circumstances; that is a question for your broker or a lawyer. The technical advice is simple: give precise answers, list the exceptions and keep dated evidence.

What should a small business do after a cyber attack if it is insured?

Report it as soon as possible to the service named in your policy and check before bringing in outside firms. Isolate the affected systems, but do not wipe or reinstall before there has been an investigation, and keep the logs. Your legal duties, such as reporting a personal data breach to the ICO within 72 hours, carry on in the meantime.

Can ITproposal fill in the insurer’s questionnaire for us?

No. We are not an insurer or a broker, we do not advise on policy or cover, and we do not complete the form on your behalf. What we do is put in place the controls the form asks about and supply the technical facts for each question, with the evidence, so that the answers you give are accurate.

Related services

Further reading

The controls the form asks about most, and the moment they matter.

Shall we hold the form up against your environment?

Send us the questions you have had from your insurer or broker. We will tell you, question by question, what is actually in place, where the exceptions are and what it takes to close them.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call