Skip to main content

Breakdown by First and Third Party

See how Hyver separates breach-related costs into company losses and third-party payments.

Updated over 5 months ago

Overview

This article explains how to read the Breakdown by First and Third Party in Hyver’s Cost of Breach. It gives you a clearer view of where your organization would incur financial losses — separating direct company impacts from third-party liabilities. This distinction helps you understand your full financial exposure and where accountability lies.


What This Breakdown Shows

The Breakdown by First & Third Party tab organizes breach-related costs into two categories:


1. Company Losses (First-Party)

These are direct, internal costs your organization would absorb. Examples may include:

  • Business continuity interruptions

  • Lost revenue

  • Productivity loss

  • Intellectual property damage

  • Brand and reputation fallout


2. Third-Party Payments

These are external costs paid to others, such as:

  • Regulatory fines

  • Class-action settlements

  • Credit monitoring for affected customers

  • Legal expenses

Each row in the table represents a different type of expense, categorized by who is impacted.


Using the Info Tooltips

Next to each expense, you'll see an Information icon (ⓘ). Hover over it to reveal:

  • A description of what the expense includes:

  • The data source used for calculating it (e.g., regulatory benchmarks, industry reports, CYE’s own breach data)

These tooltips give you more context into where each estimate comes from and how it's justified.


Important notes

  • Both types of expenses are factored into the Total Cost of Breach

  • The split helps stakeholders understand legal obligations versus operational impact

  • These figures reflect Hyver’s best estimate based on the data provided in your CoB questionnaire


Wrap-up / Next Steps

This view helps you go beyond “how much?” and start asking “who pays — and for what?” Use it to prepare for conversations with legal, finance, and executive leadership.

Did this answer your question?