Comparison Overview

St. Luke's Health System

VS

NSW Health

St. Luke's Health System

190 East Bannock Street, Boise, Idaho, US, 83712
Last Update: 2025-12-09
Between 700 and 749

As the only Idaho-based, not-for-profit health system, St. Luke’s Health System is dedicated to our mission “To improve the health of people in the communities we serve.” Today that means not only treating you when you’re sick or hurt, but doing everything we can to help you be as healthy as possible. Working together, we share resources, skills, and knowledge to provide the best possible care, no matter which of our hospitals you choose. Each St. Luke’s Health System hospital is nationally recognized for excellence in patient care, with prestigious awards and designations reflecting the exceptional care that is synonymous with the St. Luke's name.

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

NSW Health

1 Reserve Road, None, St. Leonards, New South Wales, AU, 2065
Last Update: 2025-12-09
Between 750 and 799

​​​​​​​With more than 170,000 staff and 228 hospitals, there are millions of ways we are enriching the health of the NSW community every day. In front of a patient, working in a kitchen, developing new treatments, or at a desk, each one of our staff is a vital member of the largest health organisation in Australia. What binds us is our shared passion and commitment to caring for people. We’re empowering staff to work to their full potential and equip people with skills and capabilities to be agile and responsive. ​​​Join the team enriching health in millions of ways every ​day. Find out more: https://www.health.nsw.gov.au/careers/Pages/benefits.aspx View our social media community guidelines here: https://www.health.nsw.gov.au/social/Pages/community-guidelines

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/stlukeshealthsystem.jpeg
St. Luke's Health System
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/nsw-health.jpeg
NSW Health
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
St. Luke's Health System
100%
Compliance Rate
0/4 Standards Verified
NSW Health
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 St. Luke's Health System in 2025.

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

No incidents recorded for NSW Health in 2025.

Incident History — St. Luke's Health System (X = Date, Y = Severity)

St. Luke's Health System cyber incidents detection timeline including parent company and subsidiaries

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

NSW Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/stlukeshealthsystem.jpeg
St. Luke's Health System
Incidents

Date Detected: 5/2022
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/nsw-health.jpeg
NSW Health
Incidents

Date Detected: 6/2020
Type:Breach
Blog: Blog

Date Detected: 08/2018
Type:Data Leak
Blog: Blog

FAQ

NSW Health company demonstrates a stronger AI Cybersecurity Score compared to St. Luke's Health System company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

NSW Health company has faced a higher number of disclosed cyber incidents historically compared to St. Luke's Health System company.

In the current year, NSW Health company and St. Luke's Health System company have not reported any cyber incidents.

Neither NSW Health company nor St. Luke's Health System company has reported experiencing a ransomware attack publicly.

Both NSW Health company and St. Luke's Health System company have disclosed experiencing at least one data breach.

Neither NSW Health company nor St. Luke's Health System company has reported experiencing targeted cyberattacks publicly.

Neither St. Luke's Health System company nor NSW Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither St. Luke's Health System nor NSW Health holds any compliance certifications.

Neither company holds any compliance certifications.

Neither St. Luke's Health System company nor NSW Health company has publicly disclosed detailed information about the number of their subsidiaries.

NSW Health company employs more people globally than St. Luke's Health System company, reflecting its scale as a Hospitals and Health Care.

Neither St. Luke's Health System nor NSW Health holds SOC 2 Type 1 certification.

Neither St. Luke's Health System nor NSW Health holds SOC 2 Type 2 certification.

Neither St. Luke's Health System nor NSW Health holds ISO 27001 certification.

Neither St. Luke's Health System nor NSW Health holds PCI DSS certification.

Neither St. Luke's Health System nor NSW Health holds HIPAA certification.

Neither St. Luke's Health System nor NSW Health 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