Comparison Overview

Rangely District Hospital

VS

Johns Hopkins Medicine

Rangely District Hospital

225 Eagle Crest Drive, Rangely, Colorado, 81648-2104, US
Last Update: 2025-12-09

Rangely District Hospital is a 25 bed Critical Access Hospital and Level IV Trauma Center, located at 225 Eagle Crest Drive, Rangely, CO, 81648.

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

Johns Hopkins Medicine

600 N. Wolfe Street, None, Baltimore, MD, US, 21231
Last Update: 2025-12-11

Johns Hopkins Medicine is a governing structure for the University’s School of Medicine and the health system, coordinating their research, teaching, patient care, and related enterprises. The Johns Hopkins Hospital opened in 1889, followed four years later by the university’s School of Medicine, revolutionizing medical practice, teaching, and research in the United States. The hospital is now part of the Johns Hopkins Health System, which includes two other acute-care hospitals and additional integrated health-care delivery components, with a network of primary and specialty care practices throughout Maryland, outpatient care, long-term care, and home care. The Johns Hopkins University opened in 1876 as America’s first research university, founded for the express purpose of expanding knowledge and putting that knowledge to work for the good of humanity. Two Interconnected Institutions: Over the years, the University and Hospital have grown, and—sometimes jointly, sometimes separately—they have created affiliated organizations. The Johns Hopkins Institutions is a collective name for the University and the Johns Hopkins Health System. The Johns Hopkins University includes nine academic and research divisions, and numerous centers, institutes, and affiliated entities. Johns Hopkins Medicine is a governing structure for the University’s School of Medicine and the health system, coordinating their research, teaching, patient care, and related enterprises.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/rangely-district-hospital.jpeg
Rangely District 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
https://images.rankiteo.com/companyimages/johns-hopkins-medicine.jpeg
Johns Hopkins Medicine
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
Rangely District Hospital
100%
Compliance Rate
0/4 Standards Verified
Johns Hopkins Medicine
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 Rangely District Hospital in 2025.

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

No incidents recorded for Johns Hopkins Medicine in 2025.

Incident History — Rangely District Hospital (X = Date, Y = Severity)

Rangely District Hospital cyber incidents detection timeline including parent company and subsidiaries

Incident History — Johns Hopkins Medicine (X = Date, Y = Severity)

Johns Hopkins Medicine cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/rangely-district-hospital.jpeg
Rangely District Hospital
Incidents

Date Detected: 8/2012
Type:Ransomware
Blog: Blog
https://images.rankiteo.com/companyimages/johns-hopkins-medicine.jpeg
Johns Hopkins Medicine
Incidents

Date Detected: 5/2023
Type:Breach
Attack Vector: External Hacking
Blog: Blog

FAQ

Johns Hopkins Medicine company demonstrates a stronger AI Cybersecurity Score compared to Rangely District Hospital company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Rangely District Hospital and Johns Hopkins Medicine have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Johns Hopkins Medicine company and Rangely District Hospital company have not reported any cyber incidents.

Rangely District Hospital company has confirmed experiencing a ransomware attack, while Johns Hopkins Medicine company has not reported such incidents publicly.

Johns Hopkins Medicine company has disclosed at least one data breach, while Rangely District Hospital company has not reported such incidents publicly.

Neither Johns Hopkins Medicine company nor Rangely District Hospital company has reported experiencing targeted cyberattacks publicly.

Neither Rangely District Hospital company nor Johns Hopkins Medicine company has reported experiencing or disclosing vulnerabilities publicly.

Neither Rangely District Hospital nor Johns Hopkins Medicine holds any compliance certifications.

Neither company holds any compliance certifications.

Johns Hopkins Medicine company has more subsidiaries worldwide compared to Rangely District Hospital company.

Johns Hopkins Medicine company employs more people globally than Rangely District Hospital company, reflecting its scale as a Hospitals and Health Care.

Neither Rangely District Hospital nor Johns Hopkins Medicine holds SOC 2 Type 1 certification.

Neither Rangely District Hospital nor Johns Hopkins Medicine holds SOC 2 Type 2 certification.

Neither Rangely District Hospital nor Johns Hopkins Medicine holds ISO 27001 certification.

Neither Rangely District Hospital nor Johns Hopkins Medicine holds PCI DSS certification.

Neither Rangely District Hospital nor Johns Hopkins Medicine holds HIPAA certification.

Neither Rangely District Hospital nor Johns Hopkins Medicine 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