Comparison Overview
BT Sourced

BT Sourced
2 Grand Canal Plaza, Upper Grand Canal Street, Dublin, undefined, undefined, IE
Last Update: 12/02/2026
We’re BT Sourced. And we’re redefining procurement, from top to bottom. We’re BT-owned, but a standalone company. That means we’re free to reinvent every aspect of the traditional procurement model – to unlock extra value for BT, our partners, colleagues and customers....

TIM
Via Gaetano Negri, 1, Milano, 20123, IT
Last Update: 08/09/2026
We are driving the digital transition of Italy and Brazil with innovative technologies and services because we want to contribute to accelerating the sustainable growth of the economy and society by bringing value and prosperity to people, companies and institutions. W...
Compliance Ranges Comparison

BT Sourced







TIM






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

BT Sourced

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