Cyber insurance claimsDocumentation decides whether your insurer pays

Cyber insurance does not pay out automatically. In an emergency, it is not the attack itself that decides whether your insurer pays, but the quality of what you do in the first hours afterwards. Anyone who reports too late, touches systems prematurely or cannot present traceable documentation risks partial reimbursement – or rejection.

ForensicsChain of custodyinsurer-readyavailable 24/7

The basics

What stands between your loss and the payout

An insurer pays on the basis of what has been proven: time of the attack, attack path, affected systems and data, measures taken – traceable and technically precise. If this basis is missing, things get difficult – even for organisations that were convinced they were adequately insured. It happens again and again.

We close this gap: we secure evidence before anything is changed, reconstruct the incident and deliver reports your insurer can work with.

The first hours: inform your insurer immediately and instruct us at the same time. But do not touch any systems before the evidence has been secured.

In practice

Why insurance claims fail in practice

The problem is not the severity of the attack – but what happens afterwards. We see the same four patterns again and again.

01

Systems are touched too early

Every system change before forensic preservation destroys evidence. Without it, the attack path cannot be reconstructed and the damage cannot be fully quantified.

02

Deadlines are missed

Many policies require the claim to be notified within a few hours or days, often 24 to 72 hours. Anyone who first debates internally or waits risks their claim.

03

Documentation has gaps

The insurer needs a complete forensic investigation: time, attack vector, affected systems, compromised data, measures taken.

04

Security measures cannot be proven

Policies make cover conditional on requirements such as MFA, regular backups and patch management. Anyone who implemented them but did not document them is left with their word against the insurer’s.

Statutory deadlines run in parallel: in addition to the deadlines in your policy, the reporting obligations under the GDPR and the NISG 2026 often apply as well – see NIS2 & NISG 2026.

Our services

What we deliver when a claim arises

Michael Meixner – CISSP, court-certified and sworn expert witness and incident response manager – and his team act from the very first minute in a structured, discreet way and with one clear goal: to protect your insurance claim.

Independent: we are independent of insurers. Our reports follow internationally recognised standards – NIST, SANS, ISO/IEC 27035.

  • Immediate evidence preservationDisk images, memory, network logs, cloud logs, event logs – with a complete chain of custody that stands up in court and with insurers.
  • Complete incident analysisFrom the first compromise to the last step of the attack: a technically sound basis for calculating the loss.
  • Insurer-ready reportsStatement of loss, attack vector analysis, chronology of measures and recovery recommendations; in German or English.
  • Support within the deadlinesWe work along the deadlines in your policy – no lost hours, no explanations after the fact.
  • Direct coordination with the insurerOn request, we speak directly with your insurer’s incident response provider and answer technical questions.

Prevention

Clarify in advance whether your policy will respond

Most organisations only think of their cyber insurance once the damage has been done. Yet whether the policy will respond is decided beforehand. On request, we check whether your incident response plan actually meets the requirements of your policy – the result is not a theoretical audit, but a concrete, workable plan for an emergency.

Support across Austria – 24/7, remotely or on site: Vienna, Graz, Linz, Salzburg, Innsbruck, Klagenfurt, St. Pölten, Wels.

  1. 01

    Read the policy

    Which deadlines, obligations and conditions are in your policy?

  2. 02

    Check the plan against it

    Does your incident response plan meet these requirements – and does your team know who informs whom, and when?

  3. 03

    Create proof

    MFA, backups, patch management: where are measures implemented but not documented? A cybersecurity assessment shows you.

  4. 04

    Name your DFIR partner

    Include us in your plan in advance. That saves time in an emergency and gives your insurer additional assurance.

FAQ

Frequently asked questions about cyber insurance claims

Both at the same time, as soon as you detect the incident. Inform your insurer immediately and instruct us at the same time. But do not touch any systems before the evidence has been secured.

Frequently, yes – IT forensics and evidence preservation are typically included in cyber policies as reimbursable costs; your policy is decisive. On request, we prepare a cost estimate for your insurer’s confirmation of cover.

Get in touch immediately anyway. The earlier we are involved, the more can be saved – forensically and in terms of your insurance claim. We also work with systems that have already been changed and can often reconstruct more than expected.

We are independent and work for you, not for a particular insurer. Our reports follow internationally recognised standards – NIST, SANS, ISO/IEC 27035.

No – we respond in an emergency even without an existing agreement. We do, however, recommend including us in advance as the DFIR partner in your incident response plan.

Contact

Contact us – before an emergency happens.

In a cyber attack, every minute counts – our team starts the analysis immediately. Whether an acute cyber attack, preventive advice or a forensic expert report: we are available for a free initial consultation.

Emergency 24/7+43 1 226 40 33Emailhello@dfir-austria.at

Businesses – 24/7

  • Free initial assessment of your incident (max. 30 min)
  • Response within 180 minutes
  • Confidential and discreet
  • NDA on request – available immediately

Private clients – daily 09:00–20:00

For matters relating to IT security and digital incidents.