Comparison Overview
Equifax

Equifax
P.O. Box 740241, Atlanta, 30374, US
Last Update: 13/09/2026
At Equifax (NYSE: EFX), we believe knowledge drives progress. As a global data, analytics, and technology company, we play an essential role in the global economy by helping financial institutions, companies, employers, and government agencies make critical decisions wi...

Marsh McLennan
1166 Avenue of the Americas, New York, NY, US, 10036
Last Update: 11/09/2026
Marsh (NYSE: MRSH) is a global leader in risk, strategy and people, advising clients in 130 countries across four businesses: Marsh Risk, Guy Carpenter, Mercer and Oliver Wyman. With annual revenue over $24 billion and more than 90,000 ...
Compliance Ranges Comparison

Equifax







Marsh McLennan






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
Equifax has 45.36% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Marsh McLennan in 2026.
Incident History - Equifax (X = Date, Y = Severity)
Equifax cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Marsh McLennan (X = Date, Y = Severity)
Marsh McLennan cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Equifax

Marsh McLennan
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)