08 Nov 2026 By CISO Consulting team 40 views 4 min read

Cyber Insurance Questionnaire vs NCA ECC: What You Can Evidence

Underwriters ask about MFA, backups, patching, EDR and incident response, and many of these map to NCA ECC controls you already document. This article shows how to match each question, rate your evidence and fix the gaps before going to market.

A risk manager and a CISO reviewing a printed questionnaire and control evidence folders at a meeting table in a Riyadh office.
In this article
  1. Why the questionnaire and ECC overlap
  2. Step 1: Match each question to a control area
  3. Step 2: Rate each answer as evidenced, partial or missing
  4. What evidence usually looks like
  5. Step 3: Watch for the common partial answers
  6. Step 4: Rank the gaps by underwriting impact
  7. Step 5: Assemble the evidence pack and the answers
  8. Where Cyber Insurance Readiness Assessment fits

A cyber insurance submission asks short questions that need long answers: do you enforce multi-factor authentication, are backups tested, how quickly do you patch. For an organization already working toward NCA ECC, much of the underlying work exists. What is often missing is a clear link between the question and the evidence. This article explains how to approach cyber insurance questionnaire NCA ECC evidence in a practical way, so you can rate each answer before an underwriter does.

Why the questionnaire and ECC overlap

The National Cybersecurity Authority (NCA) issues the Essential Cybersecurity Controls (ECC), which cover governance, defense, resilience and third-party security. Underwriters do not use ECC as their yardstick, but the topics they probe sit inside it: identity and access, backup and recovery, vulnerability and patch management, endpoint protection, logging and monitoring, and incident management.

This means a control you have documented for ECC can often support an insurance answer. It also means a gap you carry in your ECC work will usually surface in the questionnaire, with a premium or exclusion attached.

Step 1: Match each question to a control area

Take the questionnaire and, for each question, name the ECC control area that covers it. You do not need control numbers to start; the domain and subdomain are enough. A typical mapping looks like this:

  • Multi-factor authentication: identity and access management, including remote access and privileged accounts.
  • Backups: backup and recovery management, including offline or immutable copies and restoration testing.
  • Patching: vulnerability management and patch management for servers, endpoints and internet-facing systems.
  • EDR: protection of endpoints and servers against malware, with monitoring and response capability.
  • Incident response: cybersecurity incident and threat management, including plans, roles and testing.
  • Logging and monitoring: event log and security monitoring management.
  • Third parties: cybersecurity for suppliers and outsourced services.

If a question has no obvious home in ECC, note it separately. Some insurers ask about areas such as business interruption dependencies or social engineering controls that need their own evidence.

Step 2: Rate each answer as evidenced, partial or missing

Use three ratings and apply them strictly.

  • Evidenced: a control exists, it covers the scope the question implies, and you can produce an artifact today. Examples are a policy, a configuration export, a report or a test record.
  • Partial: the control exists but covers only part of the estate, is undocumented, or has no recent proof that it works.
  • Missing: the control does not exist, or you cannot show that it does.

The test is whether you could hand the artifact to an underwriter or broker without preparing an explanation. A statement from the IT team that "we do this" is not evidence.

What evidence usually looks like

  • MFA: the policy, plus configuration screenshots or exports showing enforcement for email, remote access and administrator accounts, and a list of exceptions.
  • Backups: the backup policy, job success reports, evidence of separation from the production network, and a dated restoration test.
  • Patching: the patch policy, scan reports, and a record of how critical items were remediated against your stated timelines.
  • EDR: a coverage report showing the share of endpoints and servers with the agent active, and how alerts are monitored and who responds.
  • Incident response: the approved plan, contact lists, and the record of the last exercise with its findings.

Step 3: Watch for the common partial answers

Partial is where most organizations land, and where answers become risky. A questionnaire answered "yes" to MFA while service accounts, legacy applications or a subsidiary are exempt can create a misrepresentation problem at claim time. Be precise about scope and state exceptions plainly.

Typical partials include:

  • MFA enforced for staff but not for administrators or third-party access.
  • Backups running, but never restored in a test.
  • EDR deployed on laptops but not on servers.
  • An incident response plan that exists but has never been exercised and does not mention insurer notification.
  • Patching policies with timelines that are not met in practice.

Step 4: Rank the gaps by underwriting impact

Not every gap matters equally. Fix in this order:

  1. Gaps that an insurer may treat as a condition of cover or a basis for exclusion, such as no MFA on remote access or no tested backups.
  2. Gaps that affect pricing and retention, such as incomplete endpoint coverage or slow patching of exposed systems.
  3. Documentation gaps, where the control works but you cannot prove it. These are usually the fastest to close.

Quick wins are common. Producing a restoration test record, extending an agent to remaining servers or writing down an exception list can change an answer from partial to evidenced within days.

Step 5: Assemble the evidence pack and the answers

Build one folder per control: the question, the ECC control area, the rating, the artifact and its date, and the person who owns it. Keep the wording of each answer consistent with the artifact. Your broker can then use it in the submission, and the same pack supports later renewals and ECC assessments.

Start early. Three to four months before renewal, or before approaching the market for the first time, leaves time to remediate and show the result rather than a plan.

Where Cyber Insurance Readiness Assessment fits

If you would like an independent view, our Cyber Insurance Readiness Assessment assesses your controls the way underwriters do, closes the gaps that drive premiums and exclusions, and prepares the evidence before you go to market. The assessment takes 3–4 weeks.

The work follows four stages: profile your business, systems and current or planned cover; assess, with underwriting controls tested, not just asked; close, through quick wins and prioritized fixes; and prepare the evidence pack and answers for the market. You receive a readiness report and score, an evidence pack, and a remediation plan ranked by underwriting impact. It draws on NCA ECC, alongside SAMA CSF and ISO 27001.

We are not an insurer or a broker. We work alongside your broker to improve your position.

Tags: cyber insurance NCA ECC underwriting questionnaire evidence Saudi Arabia GRC
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment