Comparison Overview

ImageWorks Corp.

VS

STERIS

ImageWorks Corp.

US
Last Update: 2025-12-11

ImageWorks is a provider of next generation digital imaging solutions for dental applications. We focus on providing not only great image quality, but also a great return on investment.

NAICS: 3391
NAICS Definition: Medical Equipment and Supplies Manufacturing
Employees: 21
Subsidiaries: 0
12-month incidents
1
Known data breaches
1
Attack type number
1

STERIS

5960 Heisley Rd, Mentor, OH, 44060, US
Last Update: 2025-12-09
Between 750 and 799

STERIS is a leading provider of infection prevention and other procedural products and services, focused primarily on healthcare, pharmaceutical and medical device Customers. MISSION WE HELP OUR CUSTOMERS CREATE A HEALTHIER AND SAFER WORLD by providing innovative healthcare and life science products and services around the globe. VISION We strive to be a GREAT COMPANY. We provide world-class products and services for our Customers, safe and rewarding work for our people, and superior returns for our Shareholders. • $5 Billion in revenue in FY24 • More than 17,000 Associates worldwide • Over 4,000 Customer-facing professionals • Listed on the New York Stock Exchange under the symbol “STE” To learn more, visit www.steris.com. Want to join the team? View and apply for open roles at careers.steris.com.

NAICS: 3391
NAICS Definition: Medical Equipment and Supplies Manufacturing
Employees: 10,167
Subsidiaries: 9
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
ImageWorks Corp.
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/steris-corporation.jpeg
STERIS
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
ImageWorks Corp.
100%
Compliance Rate
0/4 Standards Verified
STERIS
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Medical Equipment Manufacturing Industry Average (This Year)

ImageWorks Corp. has 8.7% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Medical Equipment Manufacturing Industry Average (This Year)

No incidents recorded for STERIS in 2025.

Incident History — ImageWorks Corp. (X = Date, Y = Severity)

ImageWorks Corp. cyber incidents detection timeline including parent company and subsidiaries

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

STERIS cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
ImageWorks Corp.
Incidents

Date Detected: 12/2025
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/steris-corporation.jpeg
STERIS
Incidents

No Incident

FAQ

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

ImageWorks Corp. company has historically faced a number of disclosed cyber incidents, whereas STERIS company has not reported any.

In the current year, ImageWorks Corp. company has reported more cyber incidents than STERIS company.

Neither STERIS company nor ImageWorks Corp. company has reported experiencing a ransomware attack publicly.

ImageWorks Corp. company has disclosed at least one data breach, while the other STERIS company has not reported such incidents publicly.

Neither STERIS company nor ImageWorks Corp. company has reported experiencing targeted cyberattacks publicly.

Neither ImageWorks Corp. company nor STERIS company has reported experiencing or disclosing vulnerabilities publicly.

Neither ImageWorks Corp. nor STERIS holds any compliance certifications.

Neither company holds any compliance certifications.

STERIS company has more subsidiaries worldwide compared to ImageWorks Corp. company.

STERIS company employs more people globally than ImageWorks Corp. company, reflecting its scale as a Medical Equipment Manufacturing.

Neither ImageWorks Corp. nor STERIS holds SOC 2 Type 1 certification.

Neither ImageWorks Corp. nor STERIS holds SOC 2 Type 2 certification.

Neither ImageWorks Corp. nor STERIS holds ISO 27001 certification.

Neither ImageWorks Corp. nor STERIS holds PCI DSS certification.

Neither ImageWorks Corp. nor STERIS holds HIPAA certification.

Neither ImageWorks Corp. nor STERIS holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N