Comparison Overview

PLVision

VS

Relay Networks, Inc.

PLVision

ul Siewna 18, Kraków, 31-231, PL
Last Update: 2025-11-21
View Profile
Between 750 and 799
http://plvision.eu/

PLVision is a European networking software product development company that helps businesses unlock the full potential of open and disaggregated networking. We deliver end-to-end, vendor-agnostic solutions, tailored to meet client’s specific use cases — enabling greater flexibility, scalability, and sustainability while ensuring cost control and predictability. Leveraging strategic partnerships with industry leaders, major hardware vendors, and membership in key open networking communities, PLVision ensures delivered software solutions remain future-ready and aligned with the latest open networking innovations, empowering clients to achieve their business goals and long-term success.

NAICS: 51125
NAICS Definition: Software Publishers
Employees: 177
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Relay Networks, Inc.

18283 Minnetonka Blvd, Deephaven, 55391, US
Last Update: 2025-11-21
Between 750 and 799
http://www.relaynetworks.com

Relay Networks, Inc. is a provider of network, wireless and telecom equipment and services. With customers in over 45 countries, Relay Networks strives to deliver quality and value worldwide. Based in Minneapolis, Minnesota, Relay Networks was co-founded by Bryan Bergschnieder and Darren Aschoff in 2005. With over 30 years combined experience in the industry, Relay Networks has the expertise to be your complete network and telecom solutions partner.

NAICS: 51125
NAICS Definition: Software Publishers
Employees: 13
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/plvision.jpeg
PLVision
—
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/relay-networks-inc..jpeg
Relay Networks, Inc.
—
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
PLVision
100%
Compliance Rate
0/4 Standards Verified
Relay Networks, Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Computer Networking Products Industry Average (This Year)

No incidents recorded for PLVision in 2025.

Incidents vs Computer Networking Products Industry Average (This Year)

No incidents recorded for Relay Networks, Inc. in 2025.

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

PLVision cyber incidents detection timeline including parent company and subsidiaries

Incident History — Relay Networks, Inc. (X = Date, Y = Severity)

Relay Networks, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/plvision.jpeg
PLVision
Incidents

No Incident

https://images.rankiteo.com/companyimages/relay-networks-inc..jpeg
Relay Networks, Inc.
Incidents

No Incident

FAQ

PLVision company demonstrates a stronger AI Cybersecurity Score compared to Relay Networks, Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Relay Networks, Inc. company has disclosed a higher number of cyber incidents compared to PLVision company.

In the current year, Relay Networks, Inc. company and PLVision company have not reported any cyber incidents.

Neither Relay Networks, Inc. company nor PLVision company has reported experiencing a ransomware attack publicly.

Neither Relay Networks, Inc. company nor PLVision company has reported experiencing a data breach publicly.

Neither Relay Networks, Inc. company nor PLVision company has reported experiencing targeted cyberattacks publicly.

Neither PLVision company nor Relay Networks, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither PLVision nor Relay Networks, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither PLVision company nor Relay Networks, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

PLVision company employs more people globally than Relay Networks, Inc. company, reflecting its scale as a Computer Networking Products.

Neither PLVision nor Relay Networks, Inc. holds SOC 2 Type 1 certification.

Neither PLVision nor Relay Networks, Inc. holds SOC 2 Type 2 certification.

Neither PLVision nor Relay Networks, Inc. holds ISO 27001 certification.

Neither PLVision nor Relay Networks, Inc. holds PCI DSS certification.

Neither PLVision nor Relay Networks, Inc. holds HIPAA certification.

Neither PLVision nor Relay Networks, Inc. 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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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).

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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

Published
Date
2025-11-27
Updated
Date
2025-11-27
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
References
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.

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

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

Published
Date
2025-11-27
Updated
Date
2025-11-27
References