Comparison Overview
CyrusOne

CyrusOne
2850 N Harwood Street, Dallas, 75201, US
Last Update: 01/09/2026
CyrusOne is a leading global data center developer and operator, delivering sophisticated digital infrastructure solutions worldwide. Headquartered in Dallas, Texas, the company operates over 60 data centers across the United States, Europe, and Japan. Specializing in c...

Capgemini
Place de l'Étoile, Paris, 75017, FR
Last Update: 14/09/2026
Capgemini is an AI-powered global business and technology transformation partner, delivering tangible business value. We imagine the future of organizations and make it real with AI, technology and people. With our strong heritage of nearly 60 years, we are a responsibl...
Compliance Ranges Comparison

CyrusOne







Capgemini






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

CyrusOne

Capgemini
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)