Comparison Overview

OhioHealth

VS

EsSalud

OhioHealth

3430 OhioHealth Parkway, Columbus, Ohio, US, 43202
Last Update: 2025-12-09
Between 750 and 799

OhioHealth is a nationally recognized, not-for-profit, faith-based health system of more than 35,000 associates, providers and volunteers. We lead with our mission to improve the health of those we serve throughout our 16 hospitals and 200+ urgent, primary and specialty care sites spanning 50 Ohio counties. Headquartered in Columbus, Ohio, we’re proud to be consistently recognized by FORTUNE as one of the “100 Best Companies to Work For” and rated a Top Hospital & Health System by Fair360 in 2024.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 14,532
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

EsSalud

120 Jirón Domingo Cueto, Jesús María, Lima, PE, 15072
Last Update: 2025-12-09

El Seguro Social de Salud, EsSalud, es un organismo público descentralizado, con personería jurídica de derecho público interno, adscrito al Sector Trabajo y Promoción Social. Tiene por finalidad dar cobertura a los asegurados y sus derechohabientes, a través del otorgamiento de prestaciones de prevención, promoción, recuperación, rehabilitación, prestaciones económicas, y prestaciones sociales que corresponden al régimen contributivo de la Seguridad Social en Salud, así como otros seguros de riesgos humanos.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 16,002
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/ohiohealth.jpeg
OhioHealth
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/essalud.jpeg
EsSalud
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
OhioHealth
100%
Compliance Rate
0/4 Standards Verified
EsSalud
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for OhioHealth in 2025.

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for EsSalud in 2025.

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

OhioHealth cyber incidents detection timeline including parent company and subsidiaries

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

EsSalud cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ohiohealth.jpeg
OhioHealth
Incidents

No Incident

https://images.rankiteo.com/companyimages/essalud.jpeg
EsSalud
Incidents

No Incident

FAQ

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

Historically, EsSalud company has disclosed a higher number of cyber incidents compared to OhioHealth company.

In the current year, EsSalud company and OhioHealth company have not reported any cyber incidents.

Neither EsSalud company nor OhioHealth company has reported experiencing a ransomware attack publicly.

Neither EsSalud company nor OhioHealth company has reported experiencing a data breach publicly.

Neither EsSalud company nor OhioHealth company has reported experiencing targeted cyberattacks publicly.

Neither OhioHealth company nor EsSalud company has reported experiencing or disclosing vulnerabilities publicly.

Neither OhioHealth nor EsSalud holds any compliance certifications.

Neither company holds any compliance certifications.

Neither OhioHealth company nor EsSalud company has publicly disclosed detailed information about the number of their subsidiaries.

EsSalud company employs more people globally than OhioHealth company, reflecting its scale as a Hospitals and Health Care.

Neither OhioHealth nor EsSalud holds SOC 2 Type 1 certification.

Neither OhioHealth nor EsSalud holds SOC 2 Type 2 certification.

Neither OhioHealth nor EsSalud holds ISO 27001 certification.

Neither OhioHealth nor EsSalud holds PCI DSS certification.

Neither OhioHealth nor EsSalud holds HIPAA certification.

Neither OhioHealth nor EsSalud 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