Comparison Overview

IoTium

VS

MGT (formerly Layer 3 Communications)

IoTium

3900 Freedom Circle, Santa Clara, 95054, US
Last Update: 2025-11-28
Between 700 and 749

IoTium provides a secure managed software-defined network infrastructure for industrial IoT to securely connect legacy and greenfield mission-critical on-site machinery and automation & control systems to applications that reside in datacenters or the cloud - all at scale. The solution is zero-touch provisioned eliminating all complexities in scalable mass deployment.

NAICS: 51125
NAICS Definition: Software Publishers
Employees: 4
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

MGT (formerly Layer 3 Communications)

1450 Oakbrook Dr, Norcross, GA, 30093, US
Last Update: 2025-11-26
Between 750 and 799

MGT is a national technology and advisory solutions leader serving state, local government, education (SLED) and targeted commercial clients. Our specialized solutions solve the most critical issues that live at the top of our clients’ leadership agenda. We partner to help clients build resilience, implement systematic change and strengthen their foundations, now and for the future. MGT is committed to impacting communities for good. Layer 3 Communications, now MGT, is an engineering firm that specializes in providing complex network services and products. Along with its hosted solutions, the company provides its customers design, management, optimization and ongoing support of network infrastructure and security (including real-time monitoring and zero-day threat mitigation). Our philosophical approach involves using capital (people, processes and technology) to solve problems.

NAICS: 51125
NAICS Definition: Software Publishers
Employees: 111
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/iotium.jpeg
IoTium
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/layer-3-communications.jpeg
MGT (formerly Layer 3 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
IoTium
100%
Compliance Rate
0/4 Standards Verified
MGT (formerly Layer 3 Communications)
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Computer Networking Products Industry Average (This Year)

No incidents recorded for IoTium in 2025.

Incidents vs Computer Networking Products Industry Average (This Year)

No incidents recorded for MGT (formerly Layer 3 Communications) in 2025.

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

IoTium cyber incidents detection timeline including parent company and subsidiaries

Incident History — MGT (formerly Layer 3 Communications) (X = Date, Y = Severity)

MGT (formerly Layer 3 Communications) cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/iotium.jpeg
IoTium
Incidents

No Incident

https://images.rankiteo.com/companyimages/layer-3-communications.jpeg
MGT (formerly Layer 3 Communications)
Incidents

No Incident

FAQ

MGT (formerly Layer 3 Communications) company demonstrates a stronger AI Cybersecurity Score compared to IoTium company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, MGT (formerly Layer 3 Communications) company has disclosed a higher number of cyber incidents compared to IoTium company.

In the current year, MGT (formerly Layer 3 Communications) company and IoTium company have not reported any cyber incidents.

Neither MGT (formerly Layer 3 Communications) company nor IoTium company has reported experiencing a ransomware attack publicly.

Neither MGT (formerly Layer 3 Communications) company nor IoTium company has reported experiencing a data breach publicly.

Neither MGT (formerly Layer 3 Communications) company nor IoTium company has reported experiencing targeted cyberattacks publicly.

Neither IoTium company nor MGT (formerly Layer 3 Communications) company has reported experiencing or disclosing vulnerabilities publicly.

Neither IoTium nor MGT (formerly Layer 3 Communications) holds any compliance certifications.

Neither company holds any compliance certifications.

IoTium company has more subsidiaries worldwide compared to MGT (formerly Layer 3 Communications) company.

MGT (formerly Layer 3 Communications) company employs more people globally than IoTium company, reflecting its scale as a Computer Networking Products.

Neither IoTium nor MGT (formerly Layer 3 Communications) holds SOC 2 Type 1 certification.

Neither IoTium nor MGT (formerly Layer 3 Communications) holds SOC 2 Type 2 certification.

Neither IoTium nor MGT (formerly Layer 3 Communications) holds ISO 27001 certification.

Neither IoTium nor MGT (formerly Layer 3 Communications) holds PCI DSS certification.

Neither IoTium nor MGT (formerly Layer 3 Communications) holds HIPAA certification.

Neither IoTium nor MGT (formerly Layer 3 Communications) holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.