Comparison Overview

Keralty

VS

Providence

Keralty

Calle 100 # 11b -67, Bogota, Bogota, 110111, CO
Last Update: 2025-12-09
Between 750 and 799

Anteriormente Organización Sanitas Internacional, Keralty es un grupo empresarial de valor en salud, con más de 40 años de experiencia conformado por empresas de aseguramiento y prestación de servicios de salud y una red propia hospitalaria y asistencial. También forman parte de Keralty instituciones educativas y empresas con enfoque social que complementan el mundo de salud que ofrecemos al mercado. Nuestra misión es contribuir al desarrollo de los países mediante innovación tecnológica, social, organizacional y atención integrada en salud, mejorando e incrementando el bienestar de las personas a lo largo de su vida, a la vez que generamos empleo, riqueza y calidad de vida a las comunidades en que operamos, favoreciendo el desarrollo regional. Somos un grupo conformado por más de 3 millones de afiliados, más de 13.000 médicos adscritos y presente en más de 7 países, que vela por el cuidado de sus usuarios, manteniendo su salud, identificando y gestionando el riesgo y la enfermedad. Somos líderes en servicios integrales de salud en los países donde estamos presentes, para ser reconocidos por nuestro enfoque humano, científico, técnico y ético.

NAICS: 62
NAICS Definition:
Employees: 12,611
Subsidiaries: 11
12-month incidents
0
Known data breaches
0
Attack type number
0

Providence

undefined, undefined, undefined, undefined, US
Last Update: 2025-12-09
Between 750 and 799

Every day, 119,000 compassionate caregivers serve patients and communities through Providence St. Joseph Health, a national, Catholic, not-for-profit health system, driven by a belief that health is a human right. Rooted in the founding missions of the Sisters of Providence and the Sisters of St. Joseph of Orange, courageous women ahead of their time who brought health care and other social services to the American West when it was still a rugged, untamed frontier, we share a singular commitment to improve the health of all. From our earliest days, we’ve met new challenges by pioneering new solutions. Today, with 51 hospitals, 829 clinics and a comprehensive range of services, we strive to meet the needs of communities across Alaska, California, Montana, New Mexico, Oregon, Texas and Washington through a diverse family of Catholic, other faith-based and mission-driven secular organizations. Now, as we face a new frontier—a changing health care landscape—we draw upon their pioneering and compassionate spirit to plan for the next century of health for a better world, especially for the poor and vulnerable. If you need treatment, please visit www.providence.org to locate a health care provider.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 47,836
Subsidiaries: 31
12-month incidents
0
Known data breaches
3
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/keralty.jpeg
Keralty
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/providencest.josephhealth.jpeg
Providence
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
Keralty
100%
Compliance Rate
0/4 Standards Verified
Providence
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 Keralty in 2025.

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

No incidents recorded for Providence in 2025.

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

Keralty cyber incidents detection timeline including parent company and subsidiaries

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

Providence cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/keralty.jpeg
Keralty
Incidents

No Incident

https://images.rankiteo.com/companyimages/providencest.josephhealth.jpeg
Providence
Incidents

Date Detected: 10/2023
Type:Ransomware
Attack Vector: Unauthorized data access and system encryption
Blog: Blog

Date Detected: 10/2023
Type:Ransomware
Blog: Blog

Date Detected: 02/2016
Type:Breach
Attack Vector: Phishing
Blog: Blog

FAQ

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

Providence company has historically faced a number of disclosed cyber incidents, whereas Keralty company has not reported any.

In the current year, Providence company and Keralty company have not reported any cyber incidents.

Providence company has confirmed experiencing a ransomware attack, while Keralty company has not reported such incidents publicly.

Providence company has disclosed at least one data breach, while Keralty company has not reported such incidents publicly.

Neither Providence company nor Keralty company has reported experiencing targeted cyberattacks publicly.

Neither Keralty company nor Providence company has reported experiencing or disclosing vulnerabilities publicly.

Neither Keralty nor Providence holds any compliance certifications.

Neither company holds any compliance certifications.

Providence company has more subsidiaries worldwide compared to Keralty company.

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

Neither Keralty nor Providence holds SOC 2 Type 1 certification.

Neither Keralty nor Providence holds SOC 2 Type 2 certification.

Neither Keralty nor Providence holds ISO 27001 certification.

Neither Keralty nor Providence holds PCI DSS certification.

Neither Keralty nor Providence holds HIPAA certification.

Neither Keralty nor Providence 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