Comparison Overview

Openreach

VS

stc

Openreach

6 Gracechurch Street, London, England, EC3V 0AT, GB
Last Update: 2025-11-25

We’re the people that make the net work. As the nation’s largest wholesale broadband network, we’re rolling out Ultrafast Full Fibre broadband across the UK. It’s our fastest and most reliable broadband yet, and we’re well on our way to making it available to 25m homes and businesses – building the UK’s fibre future. Check openreach.co.uk/ultrafastfullfibre to see when Ultrafast Full Fibre may be available at your address.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 16,763
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
2

stc

King Abdul Aziz Complex, Mursalat, Riyadh, Riyadh, SA
Last Update: 2025-11-27

We are a forward-focused digital champion always been focused on innovation and evolution. Our purpose is to create and bring greater dimension and richness to people’s personal and professional lives.  With stc, You will always be empowered to focus on delivering what’s next through collaborative and agile ways of working, and a culture that is open to fresh ideas. Transforming the future through impactful digital solutions and mega-projects while fostering our commitment to sustainability. Join a people-centric environment; that cares about maximizing your wellbeing, and is committed to unlocking your potential.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 17,035
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/openreach.jpeg
Openreach
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/stc.jpeg
stc
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Openreach
100%
Compliance Rate
0/4 Standards Verified
stc
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Openreach in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for stc in 2025.

Incident History — Openreach (X = Date, Y = Severity)

Openreach cyber incidents detection timeline including parent company and subsidiaries

Incident History — stc (X = Date, Y = Severity)

stc cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/openreach.jpeg
Openreach
Incidents

Date Detected: 12/2024
Type:Ransomware
Blog: Blog

Date Detected: 05/2018
Type:Data Leak
Attack Vector: Exposed Default Password
Motivation: Unintentional Exposure
Blog: Blog
https://images.rankiteo.com/companyimages/stc.jpeg
stc
Incidents

No Incident

FAQ

stc company demonstrates a stronger AI Cybersecurity Score compared to Openreach company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Openreach company has historically faced a number of disclosed cyber incidents, whereas stc company has not reported any.

In the current year, stc company and Openreach company have not reported any cyber incidents.

Openreach company has confirmed experiencing a ransomware attack, while stc company has not reported such incidents publicly.

Neither stc company nor Openreach company has reported experiencing a data breach publicly.

Neither stc company nor Openreach company has reported experiencing targeted cyberattacks publicly.

Neither Openreach company nor stc company has reported experiencing or disclosing vulnerabilities publicly.

Neither Openreach nor stc holds any compliance certifications.

Neither company holds any compliance certifications.

Openreach company has more subsidiaries worldwide compared to stc company.

stc company employs more people globally than Openreach company, reflecting its scale as a Telecommunications.

Neither Openreach nor stc holds SOC 2 Type 1 certification.

Neither Openreach nor stc holds SOC 2 Type 2 certification.

Neither Openreach nor stc holds ISO 27001 certification.

Neither Openreach nor stc holds PCI DSS certification.

Neither Openreach nor stc holds HIPAA certification.

Neither Openreach nor stc holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H