19 Oct 2026 By CISO Consulting team 28 views 8 min read

Which ISO 27001 Controls Cut Cyber Insurance Premiums Most

Underwriters do not weigh all ISO 27001:2022 Annex A controls equally when pricing cyber insurance. Eight specific controls—from backup testing to tabletop exercises—correlate with measurable premium reductions because they reduce claims frequency in actuarial models.

A close-up of an insurance policy document with a checklist of technical controls and premium calculation figures visible on a desk.
In this article
  1. Why Underwriters Weight Controls Differently
  2. The Eight High-Impact Annex A Controls
  3. 1. A.8.13: Backup Testing and Restoration Verification
  4. 2. A.8.11 and A.8.12: Privileged-Access Logging and Monitoring
  5. 3. A.8.8: Patch Management with Documented SLAs
  6. 4. A.5.24 and A.5.26: Incident-Response Plan with Retainer Agreements
  7. 5. A.5.17 and A.5.18: Multi-Factor Authentication on All Administrative Accounts
  8. 6. A.8.24: Encryption at Rest for Sensitive Data
  9. 7. A.5.19 and A.5.20: Third-Party Risk Assessments with Evidence of Remediation
  10. 8. A.5.28: Tabletop Exercises Conducted Annually with Executive Participation
  11. How to Prepare the Evidence Before You Go to Market
  12. Closing the Gaps That Drive Premiums

# Which ISO 27001:2022 Annex A Controls Reduce Cyber Insurance Premiums by More Than 15%: The Eight Evidence Packages Underwriters Weight Highest

When Saudi CFOs and CISOs prepare cyber insurance renewals or first-time applications, they often assume that holding ISO 27001:2022 certification alone will secure favorable terms. It does not. Underwriters do not treat all Annex A controls as equal contributors to ISO 27001 cyber insurance premium reduction. Actuarial models correlate specific controls with lower claims frequency, and those controls receive disproportionate weight in pricing algorithms and coverage decisions. Understanding which eight controls matter most—and what evidence format insurers accept for each—determines whether your institution pays market rate or secures a material discount.

This article identifies the eight Annex A 2022 controls that underwriters weight highest, explains why each reduces claims frequency in actuarial data, and specifies the evidence package format that moves premium and sub-limits.

Why Underwriters Weight Controls Differently

Cyber insurance underwriting is not a compliance exercise. It is a prediction of claims frequency and severity over the policy term. Underwriters build pricing models by correlating policyholder controls with historical claims data. Controls that demonstrably reduce the likelihood of ransomware, business interruption or privacy breach claims receive higher weighting in premium calculations. Controls that are common but show weak correlation with claims outcomes—such as annual awareness training without phishing simulation, or policy documents without enforcement logs—carry minimal weight.

ISO 27001:2022 certification signals that an organization has implemented a management system, but the certificate does not tell the underwriter which technical and operational controls are mature, tested and enforced. Underwriters therefore request evidence for specific Annex A controls during the application process. The quality, recency and format of that evidence determine whether the institution qualifies for lower premiums, higher sub-limits for business interruption or cyber extortion, and fewer exclusions.

For Saudi regulated institutions subject to the Saudi Central Bank Cyber Security Framework or the National Cybersecurity Authority Essential Cybersecurity Controls, the overlap between regulatory requirements and underwriter priorities is substantial but not complete. Some controls required by SAMA or NCA carry less weight in insurance pricing; conversely, some controls that reduce premiums are not mandated by local regulation. The eight controls below sit at the intersection of regulatory compliance, operational maturity and underwriting impact.

The Eight High-Impact Annex A Controls

1. A.8.13: Backup Testing and Restoration Verification

Why it matters: Ransomware claims account for the largest share of cyber insurance payouts globally. Underwriters know that organizations with tested, verified backups settle ransomware incidents without paying extortion demands, reducing both indemnity and incident-response costs. Backup existence is table stakes; backup restoration testing under realistic conditions is the differentiator.

Evidence format insurers accept:

  • Monthly or quarterly restoration test logs showing date, scope, duration and success criteria.
  • Evidence that backups are air-gapped or immutable (configuration screenshots or vendor attestations).
  • Documented restoration time objectives and evidence of meeting them in the most recent test.

Underwriters look for restoration tests conducted within the past 90 days. Annual tests do not satisfy the requirement.

2. A.8.11 and A.8.12: Privileged-Access Logging and Monitoring

Why it matters: Insider misuse and compromised administrator accounts are common precursors to data exfiltration and lateral movement. Underwriters correlate comprehensive privileged-access logging—covering database administrators, cloud console access, domain controllers and service accounts—with early detection and containment, which reduces business interruption sub-limit exposure.

Evidence format insurers accept:

  • SIEM or log-management platform screenshots showing privileged-session capture and alerting rules.
  • Sample alert from the past 30 days triggered by anomalous privileged activity, with investigation notes.
  • List of privileged accounts, logging coverage percentage and retention period (minimum 90 days).

Underwriters discount premium when logging covers at least 95 percent of privileged accounts and alerts are investigated within defined SLAs.

3. A.8.8: Patch Management with Documented SLAs

Why it matters: Exploitation of known vulnerabilities remains a leading attack vector. Underwriters care less about patch policy documents and more about evidence that critical patches are applied within a defined, short window. Organizations that can prove they patch internet-facing systems within 14 days of vendor release experience fewer successful intrusions.

Evidence format insurers accept:

  • Vulnerability-scan report from the past 30 days showing critical and high findings, with remediation dates.
  • Patch-management dashboard screenshot showing SLA compliance percentage for the past quarter.
  • Exception log for any critical patches not applied within SLA, with compensating controls and business justification.

Underwriters apply premium discounts when SLA compliance for critical patches exceeds 90 percent and exceptions are formally documented.

4. A.5.24 and A.5.26: Incident-Response Plan with Retainer Agreements

Why it matters: Speed of response directly affects claims severity. Underwriters know that organizations with pre-negotiated retainers for forensic investigators, legal counsel and crisis communications contain incidents faster and incur lower business interruption and reputational harm costs. A plan without retainers is less valuable in underwriting models.

Evidence format insurers accept:

  • Copy of signed retainer agreements with forensic, legal and PR firms, showing effective dates.
  • Incident-response plan document with contact details, escalation tree and evidence of annual review.
  • Tabletop exercise report from the past 12 months showing participation by executive leadership and external retainer firms.

Underwriters weight retainers heavily because they reduce the time between detection and containment, the single largest driver of business interruption claims.

5. A.5.17 and A.5.18: Multi-Factor Authentication on All Administrative Accounts

Why it matters: Credential compromise is the most common initial access vector. Underwriters correlate MFA enforcement on administrative accounts—including cloud consoles, VPN, email and privileged workstations—with a measurable reduction in successful phishing and brute-force attacks. Organizations without MFA on admin accounts face premium surcharges or outright coverage exclusions.

Evidence format insurers accept:

  • Identity-provider or directory-service screenshot showing MFA enforcement policy and coverage percentage.
  • List of administrative accounts, MFA method (hardware token, authenticator app, SMS) and exceptions.
  • Conditional-access policy configuration showing MFA required for admin roles and high-risk sign-ins.

Underwriters require 100 percent MFA coverage on administrative accounts. Any exception must be documented with compensating controls and a remediation date.

6. A.8.24: Encryption at Rest for Sensitive Data

Why it matters: Data breach notification costs and regulatory fines are significantly lower when exfiltrated data is encrypted. Underwriters reduce privacy and regulatory sub-limits when encryption at rest is enforced on databases, file shares and endpoints containing personal or payment data. Encryption in transit alone does not satisfy the requirement.

Evidence format insurers accept:

  • Data-classification inventory showing sensitive data locations and encryption status.
  • Database or storage-platform screenshots showing encryption enabled and key-management configuration.
  • Endpoint-management console report showing full-disk encryption deployment percentage and compliance.

Underwriters look for encryption on at least 95 percent of systems storing sensitive data, with centralized key management and audit trails.

7. A.5.19 and A.5.20: Third-Party Risk Assessments with Evidence of Remediation

Why it matters: Supply-chain compromises and vendor-related breaches are rising. Underwriters know that organizations conducting formal third-party risk assessments—and requiring remediation of critical findings before onboarding—experience fewer incidents originating from vendors. Questionnaires without follow-up carry minimal weight.

Evidence format insurers accept:

  • Vendor risk register showing assessment date, risk score and remediation status for critical vendors.
  • Sample vendor assessment report with identified risks and evidence of remediation or contract clauses requiring controls.
  • List of vendors with access to sensitive data or critical systems, and percentage assessed in the past 12 months.

Underwriters weight this control when assessments are conducted annually, cover at least 80 percent of critical vendors, and include evidence that high-risk findings were closed before production access.

8. A.5.28: Tabletop Exercises Conducted Annually with Executive Participation

Why it matters: Incident-response plans are only as good as the organization's ability to execute them under pressure. Underwriters correlate annual tabletop exercises—especially those involving CFO, CEO or board members—with faster decision-making during real incidents, which reduces business interruption and reputational harm. Exercises limited to IT staff do not satisfy the requirement.

Evidence format insurers accept:

  • Tabletop exercise report from the past 12 months showing scenario, participants (with titles), decisions made and lessons learned.
  • Evidence that findings from the exercise were incorporated into the incident-response plan or led to control improvements.
  • Attendance sheet or meeting minutes showing executive and legal participation.

Underwriters apply premium discounts when exercises are conducted at least annually, involve executive leadership, and result in documented plan improvements.

How to Prepare the Evidence Before You Go to Market

Underwriters evaluate evidence quality as carefully as control maturity. Screenshots must be recent, legible and show configuration details. Logs must include timestamps and cover the period requested. Policies and plans must show review dates and approval signatures. Generic or outdated evidence raises questions about control effectiveness and can result in higher premiums or coverage exclusions.

Saudi institutions preparing for cyber insurance renewals or first-time applications should begin evidence collection three to four months before the policy effective date. This timeline allows for remediation of gaps, execution of tabletop exercises, and preparation of evidence packages in the format underwriters expect.

Closing the Gaps That Drive Premiums

Identifying which controls matter most is only the first step. Closing the gaps between current state and underwriter expectations requires a structured assessment that mirrors the underwriting process itself. The 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 follows a four-stage process: profile your business, systems and current or planned cover; assess underwriting controls tested, not just asked; close quick wins and prioritized fixes; and prepare the evidence pack and answers for the market. Deliverables include a readiness report and score, an evidence pack, and a remediation plan ranked by underwriting impact. The assessment takes three to four weeks and covers controls mapped to the SAMA Cyber Security Framework, NCA Essential Cybersecurity Controls and ISO 27001.

The firm is not an insurer or a broker and works alongside your broker to improve your position. Ideally, the assessment should start three to four months before renewal or before approaching the market for the first time.

When you know which controls underwriters weight highest, and you prepare the evidence in the format they accept, you move from market rate to measurable premium reduction. The difference is not certification—it is proof.

Tags: cyber insurance ISO 27001 underwriting premium reduction Annex A controls insurance readiness
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