Comparison Overview

Banner Health

VS

Texas Children's Hospital

Banner Health

2901 N Central Ave., None, Phoenix, AZ, US, 85012
Last Update: 2025-12-09
Between 750 and 799

Headquartered in Arizona, Banner Health is one of the largest nonprofit health care systems in the country. The system owns and operates 33 acute-care hospitals, Banner Health Network, Banner – University Medicine, academic and employed physician groups, long-term care centers, outpatient surgery centers and an array of other services; including Banner Urgent Care, family clinics, home care and hospice services, pharmacies and a nursing registry. Banner Health is in six states: Arizona, California, Colorado, Nebraska, Nevada and Wyoming.

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

Texas Children's Hospital

6621 Fannin St., None, Houston, TX, US, 77030
Last Update: 2025-12-09

Texas Children’s Hospital is a world-class pediatric facility, nationally recognized as a top children’s hospital, and voted one of the best places to work in Houston for nine years running. We’re committed to creating a healthy community for children by providing the best pediatric care possible, through groundbreaking research and emphasis on education. We also offer a full continuum of family-centered care for women, from obstetrics to well-woman care. As a team member at Texas Children’s Hospital, you’ll work in an environment that values your voice. Texas Children's Hospital, headquartered in Houston, Texas, is recognized as one of America's best children's hospitals.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/texas-children's-hospital.jpeg
Texas Children's Hospital
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
Banner Health
Compliance Rate
0/4 Standards Verified
Texas Children's 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 Banner Health in 2025.

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

No incidents recorded for Texas Children's Hospital in 2025.

Incident History — Banner Health (X = Date, Y = Severity)

Banner Health cyber incidents detection timeline including parent company and subsidiaries

Incident History — Texas Children's Hospital (X = Date, Y = Severity)

Texas Children's Hospital cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/banner-health.jpeg
Banner Health
Incidents
https://images.rankiteo.com/companyimages/texas-children's-hospital.jpeg
Texas Children's Hospital
Incidents

No Incident

FAQ

Texas Children's Hospital company demonstrates a stronger AI Cybersecurity Score compared to Banner Health company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Banner Health company has historically faced a number of disclosed cyber incidents, whereas Texas Children's Hospital company has not reported any.

In the current year, Texas Children's Hospital company and Banner Health company have not reported any cyber incidents.

Neither Texas Children's Hospital company nor Banner Health company has reported experiencing a ransomware attack publicly.

Neither Texas Children's Hospital company nor Banner Health company has reported experiencing a data breach publicly.

Banner Health company has reported targeted cyberattacks, while Texas Children's Hospital company has not reported such incidents publicly.

Neither Banner Health company nor Texas Children's Hospital company has reported experiencing or disclosing vulnerabilities publicly.

Neither Banner Health nor Texas Children's Hospital holds any compliance certifications.

Neither company holds any compliance certifications.

Texas Children's Hospital company has more subsidiaries worldwide compared to Banner Health company.

Banner Health company employs more people globally than Texas Children's Hospital company, reflecting its scale as a Hospitals and Health Care.

Neither Banner Health nor Texas Children's Hospital holds SOC 2 Type 1 certification.

Neither Banner Health nor Texas Children's Hospital holds SOC 2 Type 2 certification.

Neither Banner Health nor Texas Children's Hospital holds ISO 27001 certification.

Neither Banner Health nor Texas Children's Hospital holds PCI DSS certification.

Neither Banner Health nor Texas Children's Hospital holds HIPAA certification.

Neither Banner Health nor Texas Children's Hospital 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