Cyber liability covers a business's first-party breach response costs and third-party liability arising from a cyber event. Carriers, MGAs, and TPAs writing cyber need a platform that handles claims-made forms, sublimits, and rapid breach-response workflow.
Cyber liability insurance covers a business's losses from a cyber event — both first-party costs (breach response, forensic investigation, notification, credit monitoring, business interruption from a cyber event, ransomware extortion, data restoration) and third-party liability (privacy claims, regulatory defense, network security liability, payment-card liability).
This page is a line-of-business reference for cyber carriers, MGAs, TPAs, and program administrators evaluating a policy administration platform for stand-alone cyber and packaged cyber endorsements.
A cyber policy is structured as multiple insuring agreements with their own sublimits. First-party insuring agreements typically include breach response, forensic, notification, business interruption, dependent business interruption, ransomware/extortion, and data restoration. Third-party insuring agreements include privacy liability, network security liability, regulatory defense, media liability, and PCI fines.
The platform has to track separate sublimits, retentions, waiting periods, and triggers for each insuring agreement.
Cyber underwriting is driven by the insured's cyber hygiene: MFA, backups, EDR, patching cadence, vendor management, and prior incidents. The application captures dozens of structured fields that feed the rating and eligibility engines.
Mercury's configurable underwriting workflow supports rich application schemas, third-party security-rating integrations through the API-first architecture, and rule-driven decline / referral / discount logic on cyber-hygiene attributes.
Most cyber forms are claims-made and reported with a retroactive date and an extended-reporting-period option. Some include occurrence-based first-party sections layered on a claims-made third-party section.
Mercury's configurable forms library supports claims-made retroactive-date validation, ERP endorsements, and version control of carrier-proprietary cyber forms across the policy lifecycle.
Cyber claims start with a hotline call. The first 72 hours involve forensic firms, breach coaches, notification vendors, and credit-monitoring vendors — all on panel rosters with pre-negotiated rates.
Mercury's claims administration supports configurable panel-vendor rosters, rapid intake workflow, and integrated document imaging for forensic and legal artifacts through the policy and claim lifecycle.
Does Mercury support cyber policies with multiple per-coverage sublimits?
Yes. Mercury's product configuration supports per-insuring-agreement sublimits, retentions, waiting periods, and triggers, with field-level validation through the policy lifecycle.
Can Mercury enforce retroactive dates and ERP on claims-made cyber forms?
Yes. Mercury's configurable forms library supports claims-made retroactive-date validation and extended-reporting-period endorsements with date-driven rules.
Does Mercury support panel-vendor rosters for cyber breach response?
Yes. Mercury's claims administration supports configurable panel-vendor rosters, rapid-intake workflow, and panel-rate enforcement on breach-response vendors.
