Comparison Overview

Meta

VS

Epic

Meta

1 Hacker Way, Menlo Park, CA, US, 94025
Last Update: 2025-11-21
Between 700 and 749

Meta's mission is to build the future of human connection and the technology that makes it possible. Our technologies help people connect, find communities, and grow businesses. When Facebook launched in 2004, it changed the way people connect. Apps like Messenger, Instagram and WhatsApp further empowered billions around the world. Now, Meta is moving beyond 2D screens toward immersive experiences like augmented and virtual reality to help build the next evolution in social technology. To help create a safe and respectful online space, we encourage constructive conversations on this page. Please note the following: • Start with an open mind. Whether you agree or disagree, engage with empathy. • Comments violating our Community Standards will be removed or hidden. Please treat everybody with respect. • Keep it constructive. Use your interactions here to learn about and grow your understanding of others. • Our moderators are here to uphold these guidelines for the benefit of everyone, every day. • If you are seeking support for issues related to your Facebook account, please reference our Help Center (https://www.facebook.com/help) or Help Community (https://www.facebook.com/help/community). For a full listing of our jobs, visit https://www.metacareers.com

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 140,153
Subsidiaries: 21
12-month incidents
11
Known data breaches
11
Attack type number
4

Epic

1979 Milky Way, Verona, WI, 53593, US
Last Update: 2025-11-20
Between 750 and 799

Join us in our mission to help the world get well, help the world stay well, and help future generations be healthier. We hire smart and motivated people from all academic majors to code, test, and implement healthcare software that hundreds of millions of patients and doctors rely on to improve care and ultimately save lives around the globe. No healthcare experience is necessary; we'll train you to be an expert in health IT and we'll provide you with personal development classes to grow as a professional. Our expectations for you are high, but in healthcare so are the stakes.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 15,615
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/meta.jpeg
Meta
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/epic1979.jpeg
Epic
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
Meta
100%
Compliance Rate
0/4 Standards Verified
Epic
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

Meta has 2400.0% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Epic in 2025.

Incident History — Meta (X = Date, Y = Severity)

Meta cyber incidents detection timeline including parent company and subsidiaries

Incident History — Epic (X = Date, Y = Severity)

Epic cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/meta.jpeg
Meta
Incidents

Date Detected: 11/2025
Type:Vulnerability
Attack Vector: Contact Discovery Feature Abuse, Brute-Force Queries, Metadata Exploitation
Motivation: Data Harvesting, Targeted Phishing Preparation, Identity-Based Social Engineering, Fraud Enablement
Blog: Blog

Date Detected: 11/2025
Type:Vulnerability
Attack Vector: abuse of platform feature, lack of rate limiting, automated enumeration
Motivation: research purposes, demonstration of vulnerability, potential for malicious exploitation by third parties
Blog: Blog

Date Detected: 11/2025
Type:Vulnerability
Attack Vector: Unsafe deserialization (Python pickle), ZeroMQ (ZMQ) misuse
Blog: Blog
https://images.rankiteo.com/companyimages/epic1979.jpeg
Epic
Incidents

Date Detected: 09/2021
Type:Data Leak
Attack Vector: Unauthorized Access
Motivation: Hacktivism
Blog: Blog

FAQ

Epic company demonstrates a stronger AI Cybersecurity Score compared to Meta company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Meta company has faced a higher number of disclosed cyber incidents historically compared to Epic company.

In the current year, Meta company has reported more cyber incidents than Epic company.

Neither Epic company nor Meta company has reported experiencing a ransomware attack publicly.

Meta company has disclosed at least one data breach, while the other Epic company has not reported such incidents publicly.

Meta company has reported targeted cyberattacks, while Epic company has not reported such incidents publicly.

Meta company has disclosed at least one vulnerability, while Epic company has not reported such incidents publicly.

Neither Meta nor Epic holds any compliance certifications.

Neither company holds any compliance certifications.

Meta company has more subsidiaries worldwide compared to Epic company.

Meta company employs more people globally than Epic company, reflecting its scale as a Software Development.

Neither Meta nor Epic holds SOC 2 Type 1 certification.

Neither Meta nor Epic holds SOC 2 Type 2 certification.

Neither Meta nor Epic holds ISO 27001 certification.

Neither Meta nor Epic holds PCI DSS certification.

Neither Meta nor Epic holds HIPAA certification.

Neither Meta nor Epic 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