Comparison Overview

Berkshire Hathaway

VS

Liberty Mutual Insurance

Berkshire Hathaway

US
Last Update: 2025-11-27

None

NAICS: 524
NAICS Definition: Insurance Carriers and Related Activities
Employees: 6,832
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Liberty Mutual Insurance

175 Berkeley Street, Boston, MA, US, 02116
Last Update: 2025-11-20

At Liberty Mutual, we believe progress happens when people feel secure. For more than 110 years we have helped people and businesses embrace today and confidently pursue tomorrow by providing protection for the unexpected and delivering it with care. A Fortune 100 company with more than 40,000 employees in 28 countries and economies, we are the ninth largest global property and casualty insurer and generate more than $50 billion in annual consolidated revenue. We operate through three strategic business units: US Retail Markets, providing auto, home, renters and other personal and small commercial lines property and casualty insurance to individuals and small businesses countrywide; Global Risk Solutions, delivering a full range of comprehensive commercial and specialty insurance, reinsurance and surety solutions to mid-size and large businesses worldwide; and Liberty Mutual Investments, deploying more than $100 billion of long-term capital globally across its integrated platform to drive economic growth, power innovation and secure Liberty Mutual’s promises. For more information, visit www.libertymutualinsurance.com.

NAICS: 524
NAICS Definition: Insurance Carriers and Related Activities
Employees: 37,367
Subsidiaries: 18
12-month incidents
0
Known data breaches
1
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Berkshire Hathaway
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/liberty-mutual-insurance.jpeg
Liberty Mutual Insurance
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Berkshire Hathaway
100%
Compliance Rate
0/4 Standards Verified
Liberty Mutual Insurance
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for Berkshire Hathaway in 2025.

Incidents vs Insurance Industry Average (This Year)

No incidents recorded for Liberty Mutual Insurance in 2025.

Incident History — Berkshire Hathaway (X = Date, Y = Severity)

Berkshire Hathaway cyber incidents detection timeline including parent company and subsidiaries

Incident History — Liberty Mutual Insurance (X = Date, Y = Severity)

Liberty Mutual Insurance cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Berkshire Hathaway
Incidents

No Incident

https://images.rankiteo.com/companyimages/liberty-mutual-insurance.jpeg
Liberty Mutual Insurance
Incidents

Date Detected: 11/2020
Type:Breach
Attack Vector: Fraudulent auto insurance applications
Blog: Blog

Date Detected: 06/2018
Type:Cyber Attack
Motivation: Financial Gain
Blog: Blog

FAQ

Berkshire Hathaway company demonstrates a stronger AI Cybersecurity Score compared to Liberty Mutual Insurance company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Liberty Mutual Insurance company has historically faced a number of disclosed cyber incidents, whereas Berkshire Hathaway company has not reported any.

In the current year, Liberty Mutual Insurance company and Berkshire Hathaway company have not reported any cyber incidents.

Neither Liberty Mutual Insurance company nor Berkshire Hathaway company has reported experiencing a ransomware attack publicly.

Liberty Mutual Insurance company has disclosed at least one data breach, while Berkshire Hathaway company has not reported such incidents publicly.

Liberty Mutual Insurance company has reported targeted cyberattacks, while Berkshire Hathaway company has not reported such incidents publicly.

Neither Berkshire Hathaway company nor Liberty Mutual Insurance company has reported experiencing or disclosing vulnerabilities publicly.

Neither Berkshire Hathaway nor Liberty Mutual Insurance holds any compliance certifications.

Neither company holds any compliance certifications.

Liberty Mutual Insurance company has more subsidiaries worldwide compared to Berkshire Hathaway company.

Liberty Mutual Insurance company employs more people globally than Berkshire Hathaway company, reflecting its scale as a Insurance.

Neither Berkshire Hathaway nor Liberty Mutual Insurance holds SOC 2 Type 1 certification.

Neither Berkshire Hathaway nor Liberty Mutual Insurance holds SOC 2 Type 2 certification.

Neither Berkshire Hathaway nor Liberty Mutual Insurance holds ISO 27001 certification.

Neither Berkshire Hathaway nor Liberty Mutual Insurance holds PCI DSS certification.

Neither Berkshire Hathaway nor Liberty Mutual Insurance holds HIPAA certification.

Neither Berkshire Hathaway nor Liberty Mutual Insurance holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H