Comparison Overview

ODVA

VS

NAFEMS

ODVA

4220 Varsity Dr, Ann Arbor, MI, 48108, US
Last Update: 2025-11-26
View Profile
Between 750 and 799
https://www.odva.org/

ODVA is a global association whose members are comprised of the world’s leading automation companies. ODVA’s mission is to advance open, interoperable information and communication technologies in industrial automation. ODVA recognizes its media independent network protocol, the Common Industrial Protocol or “CIP™” – and the network adaptations of CIP – EtherNet/IP™, DeviceNet™, CompoNet™ and ControlNet™ – as its core technology and the primary common interest of its membership. For future interoperability of production systems and the integration of the production systems with other systems, ODVA embraces the adoption of commercial-off-the-shelf (COTS) and standard, unmodified Internet and Ethernet technologies as a guiding principle wherever possible. This principle is exemplified by EtherNet/IP – the world’s number one industrial Ethernet network.

NAICS: 81391
NAICS Definition: Business Associations
Employees: 135
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

NAFEMS

Springwood Booths Park, Knutsford, WA16 8QZ, GB
Last Update: 2025-11-29
Between 750 and 799
https://www.nafems.org

NAFEMS is the international association dedicated to the engineering analysis and simulation community. In fact, NAFEMS is the only independent association dedicated to FEA and CFD worldwide. With over 1500 member companies ranging from major manufacturers across all industries, to software developers, consultancies and academic institutions, all of our members share a common interest in design and simulation. We are the only association which provides vital 'best practice'​ information specifically for those involved in FEA, CFD and CAE, ensuring safe and efficient analysis methods. Members of NAFEMS enjoy access to our industry-recognised training programs, independent events and acclaimed publication - all of which are designed with the needs of the analysis community in mind.

NAICS: 81391
NAICS Definition: Business Associations
Employees: 74
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/odva.jpeg
ODVA
—
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/nafems.jpeg
NAFEMS
—
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
ODVA
100%
Compliance Rate
0/4 Standards Verified
NAFEMS
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industry Associations Industry Average (This Year)

No incidents recorded for ODVA in 2025.

Incidents vs Industry Associations Industry Average (This Year)

No incidents recorded for NAFEMS in 2025.

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

ODVA cyber incidents detection timeline including parent company and subsidiaries

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

NAFEMS cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/odva.jpeg
ODVA
Incidents

No Incident

https://images.rankiteo.com/companyimages/nafems.jpeg
NAFEMS
Incidents

No Incident

FAQ

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

Historically, NAFEMS company has disclosed a higher number of cyber incidents compared to ODVA company.

In the current year, NAFEMS company and ODVA company have not reported any cyber incidents.

Neither NAFEMS company nor ODVA company has reported experiencing a ransomware attack publicly.

Neither NAFEMS company nor ODVA company has reported experiencing a data breach publicly.

Neither NAFEMS company nor ODVA company has reported experiencing targeted cyberattacks publicly.

Neither ODVA company nor NAFEMS company has reported experiencing or disclosing vulnerabilities publicly.

Neither ODVA nor NAFEMS holds any compliance certifications.

Neither company holds any compliance certifications.

Neither ODVA company nor NAFEMS company has publicly disclosed detailed information about the number of their subsidiaries.

ODVA company employs more people globally than NAFEMS company, reflecting its scale as a Industry Associations.

Neither ODVA nor NAFEMS holds SOC 2 Type 1 certification.

Neither ODVA nor NAFEMS holds SOC 2 Type 2 certification.

Neither ODVA nor NAFEMS holds ISO 27001 certification.

Neither ODVA nor NAFEMS holds PCI DSS certification.

Neither ODVA nor NAFEMS holds HIPAA certification.

Neither ODVA nor NAFEMS 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