Getting Your Controls Ready for a Cyber Insurance Renewal

Clay illustration: a small team calmly working through a list well ahead of a due date, one person ticking off a finished job while another hands over a folder, the opposite of a last-week scramble.

Three jobs, in this order. Document where the environment actually stands, close the gaps that can be closed, then keep that position true until next time. That is the work behind an honest answer to a cyber insurance renewal questionnaire. Across the 1,500 or more cyber audits inSUPPORT has run for Australian businesses, the form is almost never the hard part. The hard part is the distance between the environment and the record of it. Whose job it is to close that distance is a line in your support agreement.

It is an uncomfortable spot. Your board has asked a cyber insurance question nobody inside the business can answer. This year's questionnaire arrived longer and more technical. Half the answers turn on controls your IT provider operates and nobody has independently checked. You are still the one who signs.

Most of the answers are factual. Who holds administrator rights is a list. When the last patch cycle closed is a report. Your provider can read both this afternoon. What your provider cannot do is decide what an insurer makes of it. Answering the pack itself, question by question, is covered in how to answer a renewal questionnaire honestly.

What decides how much of this gets done before the deadline is commercial. Closing what the audit finds costs money, and whether that lands on you or on your provider is already settled. The week the form is due is a hard time to find out which way it was settled.

TL;DR: The work behind an honest answer

  • ✅ Three jobs, in order: document the position, close what can be closed, keep it true.
  • ✅ Most of what the form asks is a matter of record. An account list, a patch report, a restore date.
  • ✅ Start by recording where you actually are, says the Australian Signals Directorate (ASD) in its current transition guidance.
  • ✅ Ask who pays to close what the audit finds. One team for the IT, the compliance work and the evidence an insurer asks for is the structure that answers it.
  • ✅ The insurers underwrite, and cover is subject to the insurer's assessment.

Contents

Document the Position, With Dates on It

The first job is a record of the environment, written down and dated. Insurers price what they can look at. The Insurance Council of Australia says so directly: writing a cyber policy means getting into a client's data and IT processes, and potentially testing the defences, so the risk can be analysed and priced. What you hand over is what gets examined. A record your provider cannot produce on the day is not a record.

It is also a planning act, which the form itself never asks about. ASD's current guidance for organisations moving off the Essential Eight starts in the same place. Write down where you are now, it says, before you plan anything. The last assessment you had done. The controls you actually run. The gaps you have already accepted and the fixes you have already scheduled. That is what ASD calls a transition baseline. It is a renewal pack in different clothes. ASD writes it for large organisations, critical infrastructure and government, and points smaller businesses to its own small-business material. A business of thirty to three hundred people can take the shape of it and leave the obligation. The habit is the useful part.

The scope of the look is not mysterious either. An assessment of this kind reads identity and access, patching and currency, backup and recovery, email and endpoint, configuration drift, and what is reachable from outside the network. What actually happens in a Cyber Strength Audit walks through each of those. What a renewal needs out of it is narrower than the technical detail: a current position, the gaps named with their scope, and a costed path to closing them.

  • Write the scope down first: which tenancies, which sites, which subsidiaries, which suppliers hold access.
  • Ask your provider for exports, and put a date on every one, because currency is half of what makes a record usable.
  • Name the gaps you already know about. A board can govern a gap that is on a list. It cannot govern one that was never written down.

Who Pays When the Audit Finds Something

The second job changes the answers, and it carries a bill. A gap list does not improve an environment. Closing items does. So settle the money before the renewal, and before you sign anything. Who pays when the audit finds something? Get that answer in writing.

It is a structural question about billing. Where a provider bills for the audit and then bills again for the remediation, every gap it reports is a new project. For the provider, not for you. inSUPPORT priced it the other way round. Support runs on a flat monthly per-user fee, from $68 for business hours, $100 on the retail tier and $135 for round-the-clock support. The remediation the audit turns up sits inside that fee. Insurance, backup and the security-awareness platform are separate, clearly-quoted line items. You see the whole bill. Which items sit where is set out line by line in what the monthly fee covers and what gets quoted separately.

Then price the list against the date on the form. Some findings close in days: an exception register that does not exist yet, a logging alert routed to a shared mailbox with no named owner, a firewall rule left over from a project that finished two years ago. Others are programmes. Segmenting a flat network, putting privileged access behind a managed path, bringing a mixed Windows and Mac estate under one device-management standard. That split matters for the form, because it tells your finance team which half of the list can close before the due date and which half goes on the form as a dated plan with a named owner. ASD makes the same point about where to spend the effort. Do not chase a superseded Essential Eight target, its transition guidance says, unless a regulator or another obligation still requires it, or the work still addresses a material risk. Spend the weeks before a cyber insurance renewal on what is live, and write the rest down.

  • Get the inclusions in writing, then ask which line items turned up on your own quotes last financial year. The second answer tests the first.
  • Split the list into days and programmes before you commit to anything in front of a board or on a form.
  • For every item that will not close before the form goes back, record the compensating control, the owner and the review date.

Keeping It True Until the Next Renewal

The third job quietly gets dropped, and it is why a renewal can feel like an archaeology dig. Environments drift. People change, devices change, suppliers change, and a setting that was right in March is a finding in November. The record ages at the same rate. Where keeping it current is nobody's job, your finance team answers the next cyber insurance renewal from memory all over again.

ASD treats that decay as a live risk. The work you have already paid for can be reused, its transition guidance says, as long as it still describes the environment you are running now. Old assessment reports, configuration exports, test results, your exception register, your remediation plan. It names reusing stale evidence as one of seven transition pitfalls, because evidence is only useful while it still describes how the control actually runs. The gaps you are carrying get the same treatment. An exception that has expired, a compensating control that has degraded, a risk somebody accepted against last year's threat picture: none of those should be leaned on until they have been looked at again. On the limits of its own framework, ASD is just as blunt. The Essential Eight is a minimum set of preventative measures, and it will not mitigate all cyber threats.

So what a business ends up holding is a documented position it keeps current. Not a certificate. ASD says as much in its maturity model: nobody has to have their Essential Eight work certified by an outside party. A regulator, a government policy or a customer contract can still require an independent assessment. As checked on 16 November 2026, ASD's transition guidance was published and last reviewed on 15 October 2026. It says Essential Eight maturity level ratings do not automatically convert into ratings under the new series, the ASD Essentials. Framework guidance is moving, so read cyber.gov.au again before quoting a level at a later renewal.

Which leaves the question of who holds all of it between renewals. ASD's guidance for organisations engaging a managed service provider is direct about that. State your cyber security expectations upfront. Ask a candidate provider for evidence of its ability to meet those security requirements while administering your network. And require in the contract that the provider implement cyber security guidance such as the Essential Eight in its own house. That last one is worth putting to any provider, this one included. inSUPPORT answers it by running the support, the compliance work and the evidence an insurer asks for as one engagement, which is what keeps the record current between renewals. The policy itself is a commercial contract, arranged through licensed insurance partners and underwritten by the insurer, and cover is subject to the insurer's assessment. The plan is the part a business can own, and the part it can show.

What CFOs ask before committing to the work

Can the controls realistically be ready before the questionnaire is due?

Partly, and the sequence matters more than the hours. Start with the read, because gathering the evidence takes longer than writing the answers and the exports have to come out of live systems. Then close what can be closed before the date. That is where the quick wins sit. Whatever is still open goes on the form as a dated plan, with a named owner and the compensating control holding the line until it lands. How long that second half runs depends on what the audit finds in your environment, so a plan with dates on it is a stronger answer than a promise without them.

Does the provider that runs our environment have a conflict in auditing it?

It can, and you check it in the contract. Where the audit is billed and the remediation is billed again, a provider that finds a gap is rewarded with a second project. Where remediation sits inside the monthly support fee, a finding is work the provider has already been paid to do. Ask which model you are on and ask to be shown the clause that says so. If you want a read from outside the relationship altogether, a standalone audit is the ordinary way to get one, and its output should be usable whoever ends up doing the work.

What does this work produce that we can actually use at the renewal?

Four things. A written position covering each control in scope, with the dates attached. The exports sitting behind each answer, so your team fills the pack in from records. A register of the gaps you are carrying, each with its compensating control, its owner and its review date. And a costed path for the rest. ASD's transition guidance says the exceptions you are carrying get reviewed too, which is why that register belongs in the pack alongside the clean answers.

Where do we start if the renewal is already on the calendar?

With a current read of the environment, before anyone writes on the form. A Cyber Strength Audit documents where the environment stands against the compliance frameworks that apply to your industry, including the relevant Essential 8 controls. It names the gaps with their scope and prices the path to closing each one. It also shows which gaps can close before the renewal and which go on the form as a dated plan. Your finance team still owns the turnover, records and claims-history questions, and the policy wording belongs with the licensed adviser who arranged the cover.

See where the environment actually stands

Book a Cyber Strength Audit before the renewal questionnaire is due and you get the factual half of the answer in writing. What is configured, where the gaps are, what each one costs to close, and which of them would genuinely hurt the business. If you go on to managed support from there, the remediation it found sits inside the support fee.

Book a Cyber Strength Audit →

Citations

  • "Transitioning from the Essential Eight, Australian Signals Directorate", ASD's guidance for organisations moving from the Essential Eight to the ASD Essentials for enterprise IT. It sets out the transition baseline, which records an organisation's current position including the most recent assessment results, existing controls, exception and risk registers and remediation plans; states that organisations no longer select a target maturity level and that Essential Eight maturity level ratings do not automatically convert into the new ratings; instructs organisations not to initiate work solely to achieve a superseded Essential Eight target unless a regulator or other obligation requires it or it still addresses material risk; and lists reusing stale evidence among seven transition pitfalls. Written for large organisations, critical infrastructure and government. Published and last reviewed 15 October 2026. cyber.gov.au
  • "Essential Eight maturity model, Australian Signals Directorate", ASD's model for assessing how fully the eight mitigation strategies have been implemented. It states that there is no requirement for an organisation to have its Essential Eight implementation certified by an independent party, though an implementation may need to be assessed by one where a government directive or policy, a regulatory authority or a contract requires it, and that the Essential Eight is a minimum set of preventative measures that will not mitigate all cyber threats. Published 30 June 2017, last reviewed 27 November 2023. Read 16 November 2026. cyber.gov.au
  • "How to manage your security when engaging a managed service provider, Australian Signals Directorate", ASD's guidance for organisations that outsource IT. It covers stating cyber security expectations before engagement, asking a candidate provider for evidence of its ability to meet those requirements while administering the network, and writing into the contract that the provider implements cyber security guidance such as the Essential Eight itself. Published 21 December 2018, last reviewed 5 April 2023. Read 16 November 2026. cyber.gov.au
  • "Cyber risk, Insurance Council of Australia", The general insurance industry body's page on cyber risk. It states that insurers writing a cyber policy need to access their client's data and IT processes, and potentially test their cyber defences, in order to analyse and price the risk, and endorses the Essential Eight Maturity Model as a good first step for businesses and particularly for small and medium enterprises. Read 16 November 2026. insurancecouncil.com.au
Kane Nawrocki, Founder and CEO of inSUPPORT

About the author: Kane Nawrocki is the founder and CEO of inSUPPORT. He has spent more than 25 years in IT and built inSUPPORT to give Australian businesses managed IT, security and compliance as one model, with the remediation an audit finds included in the support fee rather than billed back as a surprise project.

Content reviewed by Probably Genius for accuracy and relevance.

Want to discuss this topic more?
CLICK HERE