CHI Health
Last Update: 2025-11-22
Between 750 and 799
#Hellohumankindness
NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 5,319
Subsidiaries: 14
12-month incidents
0
Known data breaches
9
Attack type number
4
Comparison Overview
CHI Health
VS
NewYork-Presbyterian Hospital
NewYork-Presbyterian Hospital
Last Update: 2025-11-27
Between 750 and 799
At NewYork-Presbyterian, we put patients first. It’s the kind of work that requires an unwavering commitment to excellence and a steady spirit of professionalism. And it’s a unique opportunity for you to collaborate with some of the brightest minds in health care, while building on our success as one of the nation’s best hospitals. A career here is one that helps improve the lives of countless human beings throughout the world. From preventive, inpatient and ambulatory care, to technology management and beyond, all of our work is essential to the delivery of top-notch care. Representing a wide range of fields, our talented employees collaborate across several facilities within our network, including: • NewYork-Presbyterian/Columbia University Irving Medical Center • NewYork-Presbyterian/Weill Cornell Medical Center • NewYork-Presbyterian Allen Hospital • NewYork-Presbyterian Brooklyn Methodist Hospital • NewYork-Presbyterian Hudson Valley Hospital • NewYork-Presbyterian Komansky Children's Hospital of Children's Hospital of New York • NewYork-Presbyterian Lower Manhattan Hospital • NewYork-Presbyterian Morgan Stanley Children’s Hospital of Children's Hospital of New York • NewYork-Presbyterian Queens • NewYork-Presbyterian Westchester • NewYork-Presbyterian Westchester Behavioral Health No matter where you work within our organization, you’ll enjoy inspirational and supportive leaders, the latest in technology, and a benefits package that fosters true work-life balance. These are just some of the many reasons why employee engagement and patient satisfaction are at all-time highs within our hospital. Explore our life-changing careers today, and discover the promising future ahead.
NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 26,679
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1
Compliance Badges Comparison
Security & Compliance Standards Overview
CHI Health
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
NewYork-Presbyterian Hospital
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Compliance Summary
CHI Health
100%
Compliance Rate
0/4 Standards Verified
NewYork-Presbyterian Hospital
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 CHI Health in 2025.
Incidents vs Hospitals and Health Care Industry Average (This Year)
No incidents recorded for NewYork-Presbyterian Hospital in 2025.
Incident History — CHI Health (X = Date, Y = Severity)
CHI Health cyber incidents detection timeline including parent company and subsidiaries
Incident History — NewYork-Presbyterian Hospital (X = Date, Y = Severity)
NewYork-Presbyterian Hospital cyber incidents detection timeline including parent company and subsidiaries
Notable Incidents
Last 3 Security & Risk Events by Company
FAQ
CHI Health company demonstrates a stronger AI Cybersecurity Score compared to NewYork-Presbyterian Hospital company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
CHI Health company has faced a higher number of disclosed cyber incidents historically compared to NewYork-Presbyterian Hospital company.
In the current year, NewYork-Presbyterian Hospital company and CHI Health company have not reported any cyber incidents.
CHI Health company has confirmed experiencing a ransomware attack, while NewYork-Presbyterian Hospital company has not reported such incidents publicly.
Both NewYork-Presbyterian Hospital company and CHI Health company have disclosed experiencing at least one data breach.
CHI Health company has reported targeted cyberattacks, while NewYork-Presbyterian Hospital company has not reported such incidents publicly.
Neither CHI Health company nor NewYork-Presbyterian Hospital company has reported experiencing or disclosing vulnerabilities publicly.
Neither CHI Health nor NewYork-Presbyterian Hospital holds any compliance certifications.
Neither company holds any compliance certifications.
CHI Health company has more subsidiaries worldwide compared to NewYork-Presbyterian Hospital company.
NewYork-Presbyterian Hospital company employs more people globally than CHI Health company, reflecting its scale as a Hospitals and Health Care.
Neither CHI Health nor NewYork-Presbyterian Hospital holds SOC 2 Type 1 certification.
Neither CHI Health nor NewYork-Presbyterian Hospital holds SOC 2 Type 2 certification.
Neither CHI Health nor NewYork-Presbyterian Hospital holds ISO 27001 certification.
Neither CHI Health nor NewYork-Presbyterian Hospital holds PCI DSS certification.
Neither CHI Health nor NewYork-Presbyterian Hospital holds HIPAA certification.
Neither CHI Health nor NewYork-Presbyterian Hospital holds GDPR certification.
Latest Global CVEs (Not Company-Specific)
Description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.
Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/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
- https://github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516f
- https://github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bc
- https://github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41e
- https://github.com/angular/angular/releases/tag/19.2.16
- https://github.com/angular/angular/releases/tag/20.3.14
- https://github.com/angular/angular/releases/tag/21.0.1
- https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37
Description
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.
Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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
Description
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.
Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/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
Description
Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.
Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description
Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.
Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
