Comparison Overview

Motorola Solutions

VS

Rogers Communications

Motorola Solutions

500 W. Monroe Street, Chicago, IL, US, 60661
Last Update: 2025-12-19

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
1
Known data breaches
1
Attack type number
1

Rogers Communications

333 Bloor Street East, Toronto, Ontario, CA, M4W 1G9
Last Update: 2025-12-17
Between 750 and 799

Rogers is Canada’s communications and entertainment company, driven to connect and entertain Canadians. For more information, please visit rogers.com or investors.rogers.com. Déterminée à connecter et à divertir les Canadiens et Canadiennes, Rogers est la référence canadienne en matière de communications et de divertissement. Pour en savoir plus, visitez rogers.com ou investisseurs.rogers.com. This LinkedIn company page is moderated. For more info, please review our commenting policy here: http://roge.rs/2ofPXLN

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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
https://images.rankiteo.com/companyimages/rogers-communications.jpeg
Rogers Communications
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
Motorola Solutions
100%
Compliance Rate
0/4 Standards Verified
Rogers Communications
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

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

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Rogers Communications in 2025.

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

Motorola Solutions cyber incidents detection timeline including parent company and subsidiaries

Incident History — Rogers Communications (X = Date, Y = Severity)

Rogers Communications cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/motorolasolutions.jpeg
Motorola Solutions
Incidents

Date Detected: 1/2025
Type:Breach
Attack Vector: Misconfiguration
Blog: Blog
https://images.rankiteo.com/companyimages/rogers-communications.jpeg
Rogers Communications
Incidents

No Incident

FAQ

Rogers Communications 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 historically faced a number of disclosed cyber incidents, whereas Rogers Communications company has not reported any.

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

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

Motorola Solutions company has disclosed at least one data breach, while the other Rogers Communications company has not reported such incidents publicly.

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

Neither Motorola Solutions company nor Rogers Communications company has reported experiencing or disclosing vulnerabilities publicly.

Neither Motorola Solutions nor Rogers Communications holds any compliance certifications.

Neither company holds any compliance certifications.

Both Rogers Communications company and Motorola Solutions company have a similar number of subsidiaries worldwide.

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

Neither Motorola Solutions nor Rogers Communications holds SOC 2 Type 1 certification.

Neither Motorola Solutions nor Rogers Communications holds SOC 2 Type 2 certification.

Neither Motorola Solutions nor Rogers Communications holds ISO 27001 certification.

Neither Motorola Solutions nor Rogers Communications holds PCI DSS certification.

Neither Motorola Solutions nor Rogers Communications holds HIPAA certification.

Neither Motorola Solutions nor Rogers Communications holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Marshmallow is a lightweight library for converting complex objects to and from simple Python datatypes. In versions from 3.0.0rc1 to before 3.26.2 and from 4.0.0 to before 4.1.2, Schema.load(data, many=True) is vulnerable to denial of service attacks. A moderately sized request can consume a disproportionate amount of CPU time. This issue has been patched in version 3.26.2 and 4.1.2.

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

KEDA is a Kubernetes-based Event Driven Autoscaling component. Prior to versions 2.17.3 and 2.18.3, an Arbitrary File Read vulnerability has been identified in KEDA, potentially affecting any KEDA resource that uses TriggerAuthentication to configure HashiCorp Vault authentication. The vulnerability stems from an incorrect or insufficient path validation when loading the Service Account Token specified in spec.hashiCorpVault.credential.serviceAccount. An attacker with permissions to create or modify a TriggerAuthentication resource can exfiltrate the content of any file from the node's filesystem (where the KEDA pod resides) by directing the file's content to a server under their control, as part of the Vault authentication request. The potential impact includes the exfiltration of sensitive system information, such as secrets, keys, or the content of files like /etc/passwd. This issue has been patched in versions 2.17.3 and 2.18.3.

Risk Information
cvss4
Base: 8.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/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

Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Prior to versions 1.6.13, 1.7.14, 1.8.15, and 1.9.2, a Regular Expression Denial of Service (ReDoS) vulnerability exists in Fedify's document loader. The HTML parsing regex at packages/fedify/src/runtime/docloader.ts:259 contains nested quantifiers that cause catastrophic backtracking when processing maliciously crafted HTML responses. This issue has been patched in versions 1.6.13, 1.7.14, 1.8.15, and 1.9.2.

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

Authenticated Remote Code Execution (RCE) in PluXml CMS 5.8.22 allows an attacker with administrator panel access to inject a malicious PHP webshell into a theme file (e.g., home.php).

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

An issue was discovered in Xiongmai XM530 IP cameras on firmware V5.00.R02.000807D8.10010.346624.S.ONVIF 21.06. The GetStreamUri exposes RTSP URIs containing hardcoded credentials enabling direct unauthorized video stream access.

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