Comparison Overview
S&P Global
S&P Global
55 Water Street, New York, 10041, US
Last Update: 09/09/2026
S&P Global (NYSE: SPGI) enables businesses, governments, and individuals with trusted data, expertise and technology to make decisions with conviction. We are Advancing Essential Intelligence through world-leading benchmarks, data, and insights that customers need in or...
American Express
World Financial Center, 200 Vesey Street, New York, 10285, US
Last Update: 10/09/2026
At American Express, we know that with the right backing, people and businesses have the power to progress in incredible ways. Whether we’re supporting our customers’ financial confidence to move ahead, taking commerce to new heights, or encouraging people to explore th...
Compliance Ranges Comparison
S&P Global
American Express
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
S&P Global 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 American Express in 2026.
Incident History - S&P Global (X = Date, Y = Severity)
S&P Global cyber incidents detection timeline including parent company and subsidiaries.
Incident History - American Express (X = Date, Y = Severity)
American Express cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
S&P Global
American Express
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)