Why ‘No Cyber Claims’ Doesn’t Mean Your Client Has No Cyber Incidents

Why 'No Cyber Claims' Doesn't Mean Your Client Has No Cyber Incidents

A client tells you at renewal that they’ve never had a cyber incident. No claims, no problems, nothing to report. You take the answer at face value, because most brokers do.

A new survey suggests that answer is worth pressing on. Sekuro and Women in Digital surveyed 2,003 Australians and found 42% had been exposed to cybercrime in the past five years, including 27% who became victims. Of those victims, 44% didn’t report the incident through any channel at all, and 84% of Australians believe AI will make cybercrime worse over the years ahead.

That’s a survey of individual consumers, not a study of insured businesses, so it doesn’t tell you that 44% of your commercial clients are sitting on unreported breaches. What it does tell you is that shame, fear and simple uncertainty about where to report keep real incidents out of official data, and there’s no clear reason that pattern stops at the office door.

“No prior cyber claims” can mean exactly what it says. It can also mean an incident happened but caused no insured loss, that IT handled something internally without telling anyone above them, that a supplier was the one actually breached, or that nobody recognised what happened as reportable in the first place. A renewal fact-find that only asks about claims is asking the wrong question, because claims history and incident history are not the same record.

The notification rules layered on top don’t make this simpler. A data breach under the Privacy Act is unauthorised access, disclosure or loss of personal information, and not every cyber incident meets that bar, so an entity covered by the Act only has to notify the OAIC and affected individuals where it’s assessed as an eligible data breach. APRA-regulated entities carry a separate, tighter clock: under CPS 234, a material information security incident has to be reported to APRA within 72 hours, with breach reporting itself having moved onto APRA Connect as of 21 May 2026. None of those clocks match the notice period sitting in a client’s cyber policy, and a client can be required to tell their insurer before they’ve even worked out whether an incident counts as an eligible data breach under the Privacy Act.

A few questions get past the “any claims?” checkbox. Has the business had a phishing or credential-theft attempt that didn’t turn into a loss? Has a supplier told them about an incident that touched their data? Did IT handle something internally without anyone senior finding out? And who inside the business actually decides whether an event gets escalated to you, to the insurer, or to a regulator?

Turning near misses into better submissions

None of this is about catching a client out. A documented near miss, weak multi-factor authentication, a compromised credential, a gap in vendor access, is exactly the kind of detail that strengthens a submission rather than complicating it, and underwriters respond better to a clear account of what happened and what changed afterward than to a proposal form that simply says no prior incidents. Placement support inside Better Broker uses underwriting experience built over two decades to help present that history clearly, and to work out which markets suit a client’s actual risk maturity rather than their claims history alone. Compliance support helps keep the insurer’s notice clock separate from privacy and regulatory reporting duties, so a client isn’t left guessing which one applies first, and when something is escalated, administrative and claims support keeps communication with the insurer moving through to settlement.

More on how the network supports cyber placements and claims.