Comparison Overview
Match

Match
8750 N Central Expy, Dallas, Texas, US, 75231
Last Update: 04/02/2026
Match pioneered the concept of online dating when we launched in 1995. Today, we're part of Match Group - a family of dozens of brands like Tinder and Hinge that are creating new ways to meet people, make friends, and build relationships that are fundamental to happines...

N/A
Last Update: 09/09/2026
More than one billion people around the world use Instagram, and we’re proud to be bringing them closer to the people and things they love. Instagram inspires people to see the world differently, discover new interests, and express themselves. Since launching in 2010, ...
Compliance Ranges Comparison

Match













Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Match in 2026.
Incidents vs Software Development Industry Avg (This Year)
Instagram has 482.52% more incidents than the average of all companies with at least one recorded incident.
Incident History - Match (X = Date, Y = Severity)
Match cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Instagram (X = Date, Y = Severity)
Instagram cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Match

FAQ
Latest Global CVEs
Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer overflow, leading to memory corruption. Successful exploitation would require the EPDLP module to be enabled in the client configuration, and that Memory Integrity is disabled. A successful exploit could potentially result in a denial-of-service, arbitrary code execution, or privilege escalation on the local machine.
Netskope was notified of an out-of-bounds heap read affecting the Endpoint DLP (EPDLP) service of the Netskope Client. A local standard user could potentially send a specially crafted message that is not properly validated with a bounds check, likely crashing the kernel driver handler. Successful exploitation could potentially crash the EPDLP service, temporarily interrupting DLP enforcement. A successful exploit could potentially also reveal per-boot memory layout information to unauthorized users.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to a denial of service where a specific functionality on a Db2 server can be disabled by a privileged user under certain conditions.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an attacker with the ability to control or impersonate a DRDA server endpoint to execute arbitrary commands on Db2 clients due to a stack-based buffer overflow that improperly copies user-controlled data into a fixed-size stack buffer without bounds checking.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.