Comparison Overview

Ericsson

VS

Deutsche Telekom

Ericsson

Torshamnsgatan 21, Kista, Stockholm, SE
Last Update: 2025-12-09
Between 800 and 849

The future of mobile isn’t on the horizon, it’s happening now. At Ericsson, we’re building the foundation for an open network ecosystem where industries, developers, and enterprises thrive. The convergence of 5G, AI, cloud, and network APIs isn’t just a technological shift; it’s a transformation that is redefining industries and enhancing everyday life. Open, programmable networks are enabling real-time innovation and unlocking new business models across the globe. Imagine a world where developers can dynamically access network capabilities on demand, where enterprises don’t just use connectivity but shape it. This isn’t a distant vision, it’s the ecosystem we’re creating today. Collaboration fuels everything we do. By working across industries, we’re designing a future where connectivity isn’t just seamless. It’s intelligent, programmable, and transformative. The shift is happening. Are you part of it?

NAICS: 517
NAICS Definition: Telecommunications
Employees: 97,356
Subsidiaries: 8
12-month incidents
0
Known data breaches
0
Attack type number
1

Deutsche Telekom

Friedrich-Ebert-Allee 140, Bonn, Germany, 53113, DE
Last Update: 2025-12-09

Welcome to Deutsche Telekom. As one of the world's most valuable brands, we design innovative solutions and products in the areas of connectivity, networks, digitalization and security. #connectingyourworld At Deutsche Telekom, we believe that each and every one of us has the power to move society forward. That's why we're committed to creating a culture of collaboration and innovation that everyone can participate in. We believe that diversity and inclusion are the key to creative solutions. Our employees work in 34 countries worldwide. As a leading employer, we support them with offers and benefits that enrich their work and private life. These include flexible working hours, hybrid and remote work, learning and development opportunities, health and wellbeing, as well as attractive employee benefits.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 66,644
Subsidiaries: 64
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ericsson.jpeg
Ericsson
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/telekom.jpeg
Deutsche Telekom
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
Ericsson
100%
Compliance Rate
0/4 Standards Verified
Deutsche Telekom
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Ericsson in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Deutsche Telekom in 2025.

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

Ericsson cyber incidents detection timeline including parent company and subsidiaries

Incident History — Deutsche Telekom (X = Date, Y = Severity)

Deutsche Telekom cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ericsson.jpeg
Ericsson
Incidents

Date Detected: 03/2022
Type:Vulnerability
Attack Vector: Exposure of Resource to Wrong Sphere
Blog: Blog
https://images.rankiteo.com/companyimages/telekom.jpeg
Deutsche Telekom
Incidents

No Incident

FAQ

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

Ericsson company has historically faced a number of disclosed cyber incidents, whereas Deutsche Telekom company has not reported any.

In the current year, Deutsche Telekom company and Ericsson company have not reported any cyber incidents.

Neither Deutsche Telekom company nor Ericsson company has reported experiencing a ransomware attack publicly.

Neither Deutsche Telekom company nor Ericsson company has reported experiencing a data breach publicly.

Neither Deutsche Telekom company nor Ericsson company has reported experiencing targeted cyberattacks publicly.

Ericsson company has disclosed at least one vulnerability, while Deutsche Telekom company has not reported such incidents publicly.

Neither Ericsson nor Deutsche Telekom holds any compliance certifications.

Neither company holds any compliance certifications.

Deutsche Telekom company has more subsidiaries worldwide compared to Ericsson company.

Ericsson company employs more people globally than Deutsche Telekom company, reflecting its scale as a Telecommunications.

Neither Ericsson nor Deutsche Telekom holds SOC 2 Type 1 certification.

Neither Ericsson nor Deutsche Telekom holds SOC 2 Type 2 certification.

Neither Ericsson nor Deutsche Telekom holds ISO 27001 certification.

Neither Ericsson nor Deutsche Telekom holds PCI DSS certification.

Neither Ericsson nor Deutsche Telekom holds HIPAA certification.

Neither Ericsson nor Deutsche Telekom holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N