Berkshire Hathaway
Last Update: 2025-11-27
Between 800 and 849
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
Comparison Overview
Berkshire Hathaway
VS
GREAT EASTERN
GREAT EASTERN
Last Update: 2025-11-27
Between 750 and 799
Established in 1908, Great Eastern places customers at the heart of everything we do. Our legacy extends beyond our products and services to our culture, which is defined by our core values and how we work. As champions of Integrity, Initiative and Involvement, our core values act as a compass, guiding and inspiring us to embrace the behaviours associated with each value, upholding our promise to our customers - to continue doing our best for them in a sustainable manner. We embrace inclusivity, giving all employees an equal opportunity to shine and play their role in exploring possibilities to deliver innovative insurance solutions. Since 2018, Great Eastern has been a signatory to the United Nations (UN) Principles of Sustainable Insurance. Our sustainability approach around environmental, social, and governance (ESG) considerations play a key role in every business decision we make. We are committed to being a sustainability-driven company to achieve a low-carbon economy by managing the environmental footprint of our operations and incorporating ESG considerations in our investment portfolios; improving people’s lives by actively helping customers live healthier, better and longer; and drive responsible business practices through material ESG risk management. Please note that our career opportunities are only posted on our Career Website (https://gecareers.taleo.net/careersection/ex_singapore/jobsearch.ftl?lang=en&portal=8116760849) and on our authorised job platforms, such as, LinkedIn, JobStreet and eFinancialCareers. We do not initiate any unsolicited calls and all official emails from Great Eastern will be sent from email addresses ending with “@greateasternlife.com or @greateasterngeneral.com”. Should you receive any communications outside from these channels, please do not provide any personal information and do reach out to us at [email protected] for us to assist you and confirm the legitimacy of the content.
NAICS: 524
NAICS Definition: Insurance Carriers and Related Activities
Employees: 13,454
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1
Compliance Badges Comparison
Security & Compliance Standards Overview
Berkshire Hathaway
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
GREAT EASTERN
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Compliance Summary
Berkshire Hathaway
100%
Compliance Rate
0/4 Standards Verified
GREAT EASTERN
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 GREAT EASTERN in 2025.
Incident History — Berkshire Hathaway (X = Date, Y = Severity)
Berkshire Hathaway cyber incidents detection timeline including parent company and subsidiaries
Incident History — GREAT EASTERN (X = Date, Y = Severity)
GREAT EASTERN cyber incidents detection timeline including parent company and subsidiaries
Notable Incidents
Last 3 Security & Risk Events by Company
Berkshire Hathaway
Incidents
No Incident
GREAT EASTERN
Incidents
FAQ
Berkshire Hathaway company demonstrates a stronger AI Cybersecurity Score compared to GREAT EASTERN company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
GREAT EASTERN company has historically faced a number of disclosed cyber incidents, whereas Berkshire Hathaway company has not reported any.
In the current year, GREAT EASTERN company and Berkshire Hathaway company have not reported any cyber incidents.
Neither GREAT EASTERN company nor Berkshire Hathaway company has reported experiencing a ransomware attack publicly.
Neither GREAT EASTERN company nor Berkshire Hathaway company has reported experiencing a data breach publicly.
Neither GREAT EASTERN company nor Berkshire Hathaway company has reported experiencing targeted cyberattacks publicly.
Neither Berkshire Hathaway company nor GREAT EASTERN company has reported experiencing or disclosing vulnerabilities publicly.
Neither Berkshire Hathaway nor GREAT EASTERN holds any compliance certifications.
Neither company holds any compliance certifications.
Neither Berkshire Hathaway company nor GREAT EASTERN company has publicly disclosed detailed information about the number of their subsidiaries.
GREAT EASTERN company employs more people globally than Berkshire Hathaway company, reflecting its scale as a Insurance.
Neither Berkshire Hathaway nor GREAT EASTERN holds SOC 2 Type 1 certification.
Neither Berkshire Hathaway nor GREAT EASTERN holds SOC 2 Type 2 certification.
Neither Berkshire Hathaway nor GREAT EASTERN holds ISO 27001 certification.
Neither Berkshire Hathaway nor GREAT EASTERN holds PCI DSS certification.
Neither Berkshire Hathaway nor GREAT EASTERN holds HIPAA certification.
Neither Berkshire Hathaway nor GREAT EASTERN 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
References
- https://github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516f
- https://github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bc
- https://github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41e
- https://github.com/angular/angular/releases/tag/19.2.16
- https://github.com/angular/angular/releases/tag/20.3.14
- https://github.com/angular/angular/releases/tag/21.0.1
- https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37
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
