What Makes an Australian Business Insurable

Clay illustration: a finance leader asked a hard question across a boardroom table, and the quiet steadiness of being able to put the evidence on the table instead of guessing.

A business is insurable when the controls an insurer prices are actually in place, when somebody can produce evidence of them today, and when what it told its insurer matches what it runs. That is a statement about an environment and a paper trail. It is not a prediction about a policy. inSUPPORT builds and maintains the environment and the paper trail. The cover is arranged through licensed insurance partners and underwritten by the insurer, and it is subject to the insurer's assessment.

If the board has asked you whether the cyber insurance would respond, you already know the awkward part. You hold a policy. You cannot personally verify the environment sitting behind it, and as far as you know nobody has checked it since the questions were answered.

Part of why that question is so hard to answer is that four words get used as though they mean the same thing. Insured, insurable, compliant and secure. They describe four different things, only one of them is a fact about a document, and the gap between the first two is exactly what your board is asking about.

So this is the plain version. What insurable describes, how it differs from the three words it gets confused with, and what the plan behind it actually contains. This piece defines the technical word. The policy word belongs to the licensed parties, and it stays with them.

TL;DR: What insurable actually means

  • ✅ Insurable describes your environment and its records: the controls exist, the evidence is current, and the form matches what you run.
  • ✅ Insured is a fact about a document. Insurable is a fact about the environment behind it. You can be the first without the second.
  • ✅ Compliant on its own tells you nothing. A real answer names the framework, scope, level, assessor and date.
  • ✅ The plan has four parts. The fourth is a register of the exceptions you live with.

Contents

What Insurable Actually Describes

Insurable describes a state, and it has three parts. The controls an insurer prices are actually configured. Somebody can show each one now, from records that already exist. And the answers given on the proposal or renewal form describe the environment that is actually running. Hold all three and a business is insurable in the only sense anyone outside an insurance licence can speak to.

The third part is the one that catches people out, because it has nothing to do with how strong the security is. Before the contract starts, you have to tell the insurer everything you know that is relevant to whether it accepts the risk and on what terms, plus anything a reasonable person in the circumstances could be expected to know is relevant. That is the duty of disclosure, and the Insurance Contracts Act 1984 (Cth) puts it on the insured of a commercial policy, which is what a business holds. The duty attaches to what you said. So the one input a business fully controls is the accuracy of its own description of itself.

That is also why cyber insurance readiness is a technical state and not a product. It is a condition of your network, your identity platform, your backups and your records, held steady and written down. Our earlier piece on what an underwriter weighs before covering an Australian business covers why those particular controls end up on the form.

The three tests, in plain words

Each one is a question with a factual answer. None of them needs a licence to ask, and none of them is answered by an adjective.

  • Is the control on? Not policy, not plan. The setting, in the console, applied to the accounts and devices it is supposed to cover.
  • Can you show it today? A configuration export, a live screen, a test result with a date on it. Something that existed before anybody asked.
  • Does the paperwork match? The form the insurer holds, read line by line against the environment as it stands this week.

It is a present tense, not a trophy

Nothing about this is permanent, and the grammar matters more than it sounds. A business is insurable the way a car is roadworthy, which is to say on a date, against a standard, on the evidence available. It is not a thing you become and then are.

Which is why there is no certificate here and no single number that settles it. If somebody offers you one, what they are selling is a measurement of something specific, taken at a moment, by a method worth asking about. That can be genuinely useful. It is a different claim from the one the word makes.

Insured, Insurable, Compliant and Secure

Four words do four different jobs here, and they are easy to swap because all four sound like good news. Each one has a different subject, a different kind of evidence behind it and a different party who can confirm it. Sorting them out takes about a minute and it changes what you ask for.

Insured is a fact about a document. You hold a policy, it has a schedule, and the schedule says what it says. Insurable is a fact about an environment and its records. Compliant is a measurement against a named framework, in a named scope, at a named level, by somebody, on a date. Secure is the loosest of the four, because it names no framework, no scope and no date. It describes an intention. It is not a finding.

The pairing that matters is the first two. A business can be insured and not insurable, and that combination is what the board's question is really about. A business can also be insurable and uninsured. That is a purchasing decision, and it belongs with the licensed parties who arrange cover.

Why compliant on its own tells you nothing

Of the four, compliant is the one most likely to arrive in writing and the one least likely to mean anything. On its own it is a word with the subject removed. Compliant with what, across which systems, to what level, assessed by whom, and when.

So treat the bare word as an unfinished sentence and ask for the rest of it. A real answer names the framework, states what was in scope and what was excluded, gives the level where the framework has one, says who did the assessing, and carries a date. That is five pieces of information, all of which already exist if the work was actually done. If they take a fortnight to assemble, you have learned something too.

  • Compliant with what: the framework, named.
  • In which scope: the systems included, and the ones left out on purpose.
  • At what level, where the framework has levels.
  • Assessed by whom, internally or independently.
  • When, as a date rather than a season.

Where the licensed line sits

This article describes controls and records, not policies, and that boundary is a legal one. The Australian Securities and Investments Commission (ASIC) draws it in the same place in its guidance on financial product advice: handing somebody facts is generally not advice, while recommending a product, or giving an opinion meant to sway a decision about one, is. inSUPPORT is not an insurer, broker or underwriter and holds no Australian Financial Services Licence, so it works on the factual side and the licensed partners work on the other. Our piece on how an insurer can check what you told them stays on the same side.

What the Plan Behind It Actually Contains

If insurable is the state, the plan is the thing that holds it there, and it is worth knowing what you are buying when somebody sells you one. A plan is not a report. A report describes a moment, and the moment moves on without it. A plan has four named parts, and the fourth is the one nobody expects.

First, a scoped assessment: what was measured, against which compliance frameworks, on what date, by whom, and what was deliberately left out. Second, the agreed control set, meaning the gaps that were closed and the ones that were not. Third, the evidence itself, produced as a by-product of running the environment, so it already exists when somebody asks for it. Fourth, a written register of the exceptions you live with.

The Insurance Council of Australia is open about why any of this gets examined. Writing a cyber policy requires an insurer to reach into a client's data and IT processes, and potentially to test their defences, in order to analyse and price the risk. Your environment is part of what is being priced, which is the reason the plan is a commercial document and not a technical hobby. So ask which parts of it sit inside the fee and which get quoted on top. At inSUPPORT the remediation an audit finds sits inside the support fee, and insurance, backup and the security awareness platform are quoted as separate line items.

The register of exceptions is part of the plan, not a hole in it

This is the part most people are surprised to hear belongs in the document. Every real environment carries things that cannot be changed yet. A line-of-business application that breaks under a current patch level. A supplier portal that will not do multi-factor authentication. A piece of plant running an operating system nobody supports and nobody can replace this financial year.

Leaving those out does not make them go away, it makes them invisible, and an invisible exception is the one that contradicts your paperwork later. Written down, each one gets an owner, a reason and a review date, and it stops being a surprise to everybody including you. That conversation happens before any work starts rather than after, which is the difference between a plan you agreed to and a plan you were handed.

What a plan has that a report does not

Those four parts are the contents. Three further things turn them into a plan, and none of them is length. A date it was true on, so anyone reading it later knows what they are looking at. A named owner for every line, including the uncomfortable ones. And a next review, because a state described in the present tense needs somebody to keep checking the tense is still right.

A document with those three is governable. A board can track it, a finance team can budget against it, and the next renewal starts from it instead of from memory. A document without them is a snapshot, and the honest thing to do with a snapshot is date it and admit what it is. If the board meeting is closer than the renewal, our piece on what a finance leader can actually verify is the shorter path.

Questions finance leaders ask about being insurable

What does it mean for a business to be insurable, and who decides it?

Being insurable describes the state of your environment and your records. It says nothing about the status of your policy. The controls an insurer prices are in place, the evidence of them is current, and what you told the insurer matches what you run. That much is checkable, and improving it is ordinary technical work. The cover itself is a separate question: it is arranged through licensed insurance partners, underwritten by the insurer, and subject to the insurer's assessment. Being insurable is the part you can work on.

Is this something we can work out ourselves, or do we need somebody to assess it?

You can get a long way on your own, and it is worth doing first. Get the policy schedule, the wording and the last submitted form into one dated folder, then put a named person against every control the form claimed. That part is reading and asking, and it will tell you how much of your position is documented at all. Where an assessment earns its money is the technical half: whether each control is genuinely configured the way the form says, and whether anybody can show it from records that already exist. That needs somebody who can read a console, and it usually produces information nobody in the business had.

How often does a plan like this need re-dating?

There is no universal interval, and anybody offering you one is guessing at your rate of change rather than measuring it. What is more useful than a number is a list of triggers. A renewal. An acquisition, or a new site absorbed. A new cloud service or a new line-of-business application. A change of provider. Any one of those can move the environment far enough that the last dated position no longer describes it, and the next review is written into the plan precisely so somebody owns noticing. Being insurable has a shelf life. The date on the plan is how you tell whether yours has run out. Between triggers, the honest answer is whatever interval you will actually keep.

Nobody has ever checked our environment against what the insurer was told. Where do we start?

Start with the audit. Every other step reads against what it finds. A Cyber Strength Audit documents the environment you are actually running and assesses it against the compliance frameworks that apply to your industry, including the relevant Essential 8 controls from the Australian Signals Directorate. It tests what is reachable from outside and from inside, then finishes with a costed list of what to close. You get a plain English risk picture, a documented trail you can hand to a board or an insurer, and the exceptions written down rather than left implied. What you do with it afterwards is your call.

Start with what you can actually show

If nobody has read your environment against what your insurer was told, that is the gap worth closing first, and it is a technical job with a beginning and an end. A Cyber Strength Audit documents what you run, measures it against the frameworks your industry uses, and hands you the evidence and a costed path. Go on to managed support and the remediation it finds sits inside the support fee.

Book a Cyber Strength Audit →

Citations

  • "Insurance Contracts Act 1984 (Cth), compilation of 8 October 2026", Section 21 sets out the insured's duty of disclosure for contracts that are not consumer insurance contracts, which is why accuracy, and not the strength of the controls, is what a business most directly governs. Consumer insurance contracts carry a different duty, to take reasonable care not to make a misrepresentation. Read at the source on 16 November 2026 (Compilation No. 33). legislation.gov.au
  • "ASIC Regulatory Guide 36, Licensing: Financial product advice and dealing", Paragraph 36.23 distinguishes factual information from financial product advice, which is the boundary this article stays on the factual side of when it describes controls rather than policies. Issued June 2016. download.asic.gov.au
  • "Insurance Council of Australia, Cyber risk", The industry body states that writing a cyber insurance policy requires an insurer to access a client's data and IT processes and potentially test their cyber defences to analyse and price the risk. 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