Comparison Overview
BT for global business

BT for global business
BT Centre, London, undefined, EC1A 7AJ, GB
Last Update: 03/01/2026
We serve global multinational organisations around the world with our security, cloud and networking services. We can help your organisation to move to the cloud; turn collaboration into part of your culture; improve your contact centres; transform your customer servic...

Cox Communications
6205 Peachtree Dunwoody Road, Atlanta, 30328, US
Last Update: 01/04/2026
Cox Communications is committed to creating more moments of real human connection. We bring people closer to family and friends through technology that’s inspired by a culture that puts people first, and we’re always working to improve life in the communities we serve. ...
Compliance Ranges Comparison

BT for global business







Cox Communications






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for BT for global business in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Cox Communications in 2026.
Incident History - BT for global business (X = Date, Y = Severity)
BT for global business cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cox Communications (X = Date, Y = Severity)
Cox Communications cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BT for global business

Cox Communications
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)