Insights

Cyber insurance evidence: prepare four controls for your broker

4 November 2026

Build cyber insurance evidence for MFA, recovery tests, endpoint protection and access reviews before your next broker discussion or policy renewal.

ThreatLocker has published commentary arguing that insurers are scrutinising security controls more closely when assessing cyber cover. For Australian small and medium businesses approaching renewal, the practical takeaway is to prepare cyber insurance evidence that shows what is actually protected, rather than simply listing purchased products.

In its article on security controls and cyber insurance, ThreatLocker links stronger controls with insurance eligibility and cost. Treat that as a vendor perspective, not a promise of cheaper premiums. Underwriting requirements, pricing and coverage vary by insurer and policy.

The useful starting point is four evidence packs: multi-factor authentication, backup recovery tests, endpoint protection and access reviews.

Start cyber insurance evidence with the actual questionnaire

Ask your broker for the current proposal or renewal questionnaire before collecting screenshots. The wording matters: a question about all remote access is different from one about email accounts alone.

Create a simple register with these columns:

  • Question: the insurer’s exact wording.
  • Scope: accounts, devices, applications or locations included.
  • Evidence: a dated report, configuration export or test record.
  • Exceptions: anything not covered, with an owner and remediation date.
  • Approval: the technical reviewer and business signatory.

Avoid answering “yes” because a feature is available or licensed. Confirm that it is enabled, enforced and operating across the requested scope. Where a question is ambiguous, ask the broker to obtain written clarification.

Security improvements can reduce operational risk and support underwriting discussions. They do not automatically produce a discount, guarantee cover or determine how a future claim will be assessed.

1. Show where MFA is enforced, not just enrolled

Multi-factor authentication adds a verification step beyond a password. However, a list of people who have registered an authenticator does not prove that every relevant sign-in requires it.

Check business email, remote access, cloud administration, finance applications, backup consoles and third-party support access. Review privileged accounts separately because their compromise can affect many users or systems.

Useful MFA evidence includes:

  • An export of enforcement policies, including included and excluded users.
  • A report showing authentication methods and registration status.
  • Recent sign-in records demonstrating that the policies apply.
  • A register of emergency accounts and other exceptions, with monitoring arrangements.
  • Confirmation that older authentication paths cannot bypass the intended controls.

Where supported, consider phishing-resistant methods such as passkeys or security keys. Ask whether the insurer specifies acceptable authentication methods rather than assuming every form of MFA meets its expectations.

Record any application that cannot support the required controls. Explain the limitation and compensating measures to your broker instead of hiding it behind an organisation-wide statement. Our Microsoft 365 passkeys checklist covers enrolment, recovery and fallback checks.

2. Prove that backups can restore a working service

A successful backup job means data was copied according to that job’s rules. It does not establish that the business can recover a usable application within an acceptable time.

Choose a representative business service and test recovery in an isolated environment. This could involve restoring a finance application with its database, a shared file repository with permissions, or selected Microsoft 365 data where backup is configured.

Capture the following in the test record:

  • The service, backup date and recovery point selected.
  • Who performed the test and when it took place.
  • The steps required, including dependencies and credentials.
  • Actual recovery duration and the age of recovered data.
  • Validation by the person responsible for using the service.
  • Failures, corrective actions and any subsequent retest.

Also document how backups resist deletion or alteration. Check separation of administrative credentials, retention settings, restricted console access and offline or immutable copies where appropriate. Verify these arrangements rather than relying on a product label.

Compare the result with business-approved recovery objectives: how long the service can be unavailable and how much recent data can be lost. A file restore is useful evidence, but it is not a full business recovery exercise. See our guide to usable recovery evidence for a more detailed approach.

3. Reconcile endpoint protection against your device inventory

An endpoint security dashboard may look healthy while missing devices that never enrolled. Start with an inventory of laptops, desktops and servers, then reconcile it against the protection platform.

Record unsupported operating systems, devices that have stopped reporting and any equipment that cannot run the required agent. Include remote workers and relevant hosted servers, not just computers in the office.

Your endpoint evidence pack should show:

  • In-scope device totals compared with protected device totals.
  • Agent health, update status and last contact times.
  • Relevant prevention, detection and tamper-protection settings.
  • Who receives alerts and who is authorised to isolate a device.
  • An approved, safe validation exercise or documented alert-handling test.
  • Security exclusions and the reasons they remain necessary.

Distinguish antivirus, endpoint detection and response, and managed monitoring. Installing a detection tool does not establish that someone investigates its alerts after hours.

Ask the insurer what it means by “monitored” or “managed” protection. Then ensure the answer matches your actual service arrangements. Review broad folder and process exclusions using our Defender exclusions audit checklist.

4. Make access reviews a recorded business decision

An access review should establish whether people still need their permissions, not merely confirm that their accounts exist.

Export user and administrator lists from important systems. Include external support accounts, shared accounts, service identities and application permissions where relevant. Have the responsible manager assess access against current duties.

Prioritise finance systems, email administration, backups, remote support and customer information. Check recent departures and role changes against completed removal or adjustment records.

Keep evidence of:

  • The systems and identities reviewed.
  • The reviewer and completion date.
  • Permissions retained, reduced or removed.
  • Tickets or audit records proving changes were completed.
  • Unresolved exceptions, accountable owners and review dates.

Use separate administrative identities where appropriate and avoid routine work with elevated privileges. For supplier access, confirm who approves it, how it is authenticated and how it is revoked. A signed review without completed changes leaves the underlying risk unresolved.

Turn findings into a useful broker discussion

Keep cyber insurance evidence in a controlled repository with dated versions. Provide what the broker or insurer requests through an agreed secure channel; do not send passwords, recovery keys or unnecessary personal information.

Prepare a short summary of verified controls, known gaps and planned improvements. Ask the broker:

  • Which controls are prerequisites, and which may influence underwriting terms?
  • What evidence and testing frequency does this policy require?
  • What notification obligations apply if controls change during the policy period?
  • What exclusions, sublimits, excesses and waiting periods apply?
  • What incident notification and approval steps must be followed before appointing responders or incurring costs?

Technical evidence supports accurate disclosure, but it does not replace policy advice. Ask your broker to explain how the wording applies to your operations, including outsourced services.

Keep the evidence current after renewal

Assign an owner to each control and refresh records when systems, suppliers or access arrangements change. Agree a review schedule with your IT team, and check whether the policy requires particular testing or reporting intervals.

The goal is not a polished folder once a year. It is a reliable connection between what your business declares and what its systems actually do.

Tech Engine can help review your cyber security, identify control gaps and organise technical evidence for broker discussions. Call 1300 088 324 or email sales@techengine.au to arrange a review.

Want this applied to your business?

Request an AI Blueprint and we will map the processes worth automating first.

Request an AI Blueprint