Comparison Overview

Ericsson

VS

Motorola Solutions

Ericsson

Torshamnsgatan 21, Kista, Stockholm, SE
Last Update: 2025-11-23
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

Motorola Solutions

500 W. Monroe Street, Chicago, IL, US, 60661
Last Update: 2025-11-23

About Motorola Solutions | Solving for safer Safety and security are at the heart of everything we do at Motorola Solutions. We build and connect technologies to help protect people, property and places. Our solutions foster the collaboration that’s critical for safer communities, safer schools, safer hospitals, safer businesses, and ultimately, safer nations. Learn more about our commitment to innovating for a safer future for us all at www.motorolasolutions.com.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 25,588
Subsidiaries: 10
12-month incidents
2
Known data breaches
1
Attack type number
2

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/motorolasolutions.jpeg
Motorola Solutions
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
Motorola Solutions
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)

Motorola Solutions has 238.98% more incidents than the average of same-industry companies with at least one recorded incident.

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

Ericsson cyber incidents detection timeline including parent company and subsidiaries

Incident History — Motorola Solutions (X = Date, Y = Severity)

Motorola Solutions 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/motorolasolutions.jpeg
Motorola Solutions
Incidents

Date Detected: 1/2025
Type:Breach
Attack Vector: Misconfiguration
Blog: Blog

Date Detected: 1/2025
Type:Vulnerability
Attack Vector: Unauthenticated Access
Blog: Blog

FAQ

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

Motorola Solutions company has faced a higher number of disclosed cyber incidents historically compared to Ericsson company.

In the current year, Motorola Solutions company has reported more cyber incidents than Ericsson company.

Neither Motorola Solutions company nor Ericsson company has reported experiencing a ransomware attack publicly.

Motorola Solutions company has disclosed at least one data breach, while Ericsson company has not reported such incidents publicly.

Neither Motorola Solutions company nor Ericsson company has reported experiencing targeted cyberattacks publicly.

Both Ericsson company and Motorola Solutions company have disclosed vulnerabilities.

Neither Ericsson nor Motorola Solutions holds any compliance certifications.

Neither company holds any compliance certifications.

Motorola Solutions company has more subsidiaries worldwide compared to Ericsson company.

Ericsson company employs more people globally than Motorola Solutions company, reflecting its scale as a Telecommunications.

Neither Ericsson nor Motorola Solutions holds SOC 2 Type 1 certification.

Neither Ericsson nor Motorola Solutions holds SOC 2 Type 2 certification.

Neither Ericsson nor Motorola Solutions holds ISO 27001 certification.

Neither Ericsson nor Motorola Solutions holds PCI DSS certification.

Neither Ericsson nor Motorola Solutions holds HIPAA certification.

Neither Ericsson nor Motorola Solutions 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