Comparison Overview

Kettering Health

VS

Oregon Health & Science University

Kettering Health

3535 Southern Blvd., Kettering, OH, US, 45429
Last Update: 2026-03-29
View Profile
Between 0 and 549
http://www.ketteringhealth.org

As a faith-based, nonprofit healthcare system, Kettering Health's mission is to live God's love by promoting and restoring health. We're made up of 14 medical centers and more than 120 outpatient locations throughout western Ohio, as well as Kettering Health Medical Group. With more than 700 board-certified providers, we're dedicated to elevating the health, healing, and hope of our community.

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

Oregon Health & Science University

3181 SW Sam Jackson Park Rd, Portland, Oregon, US, 97239
Last Update: 2026-03-30
Between 750 and 799
http://ohsu.edu

At OHSU, we deliver breakthroughs for better health. We're driven by the belief that better health starts with innovations in the lab, in the classroom, at the bedside and in our communities. From cancer to Alzheimer's to cardiovascular care, we collaborate every day to identify and deliver new ways to understand disease, treat illness and train the next generation of scientists and health professionals. It takes all of us - from scientists, clinicians and nurses to a top-notch professional staff. Join us.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ketteringhealth.jpeg
Kettering 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
https://images.rankiteo.com/companyimages/ohsu.jpeg
Oregon Health & Science University
—
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
Kettering Health
100%
Compliance Rate
0/4 Standards Verified
Oregon Health & Science University
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 Kettering Health in 2026.

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

No incidents recorded for Oregon Health & Science University in 2026.

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

Kettering Health cyber incidents detection timeline including parent company and subsidiaries

Incident History — Oregon Health & Science University (X = Date, Y = Severity)

Oregon Health & Science University cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ketteringhealth.jpeg
Kettering Health
Incidents

Date Detected: 10/2025
Type:Ransomware
Attack Vector: Browser-Based Exploitation, Malicious JavaScript (Auto-Copy to Clipboard), User-Initiated Command Execution (e.g., PowerShell, mshta, LOLBINs), SEO Poisoning, Malvertising (Google Ads), Compromised/Legitimate-Looking Domains, Conditional Loading (OS/Geo/IP Targeting)
Motivation: Financial Gain (Ransomware, Data Theft), Credential Harvesting, Lateral Movement for Targeted Attacks, Espionage (APT-Linked), Session Hijacking
Blog: Blog

Date Detected: 5/2025
Type:Cyber Attack
Blog: Blog

Date Detected: 5/2025
Type:Ransomware
Attack Vector: Remote Desktop Protocol (RDP), social engineering (ClickFix technique), malicious PowerShell commands, rundll32.exe execution, lateral movement
Motivation: financial gain (double extortion), data theft
Blog: Blog
https://images.rankiteo.com/companyimages/ohsu.jpeg
Oregon Health & Science University
Incidents

No Incident

FAQ

Oregon Health & Science University company demonstrates a stronger AI Cybersecurity Score compared to Kettering Health company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Kettering Health company has historically faced a number of disclosed cyber incidents, whereas Oregon Health & Science University company has not reported any.

In the current year, Oregon Health & Science University company and Kettering Health company have not reported any cyber incidents.

Kettering Health company has confirmed experiencing a ransomware attack, while Oregon Health & Science University company has not reported such incidents publicly.

Neither Oregon Health & Science University company nor Kettering Health company has reported experiencing a data breach publicly.

Kettering Health company has reported targeted cyberattacks, while Oregon Health & Science University company has not reported such incidents publicly.

Neither Kettering Health company nor Oregon Health & Science University company has reported experiencing or disclosing vulnerabilities publicly.

Neither Kettering Health nor Oregon Health & Science University holds any compliance certifications.

Neither company holds any compliance certifications.

Oregon Health & Science University company has more subsidiaries worldwide compared to Kettering Health company.

Oregon Health & Science University company employs more people globally than Kettering Health company, reflecting its scale as a Hospitals and Health Care.

Neither Kettering Health nor Oregon Health & Science University holds SOC 2 Type 1 certification.

Neither Kettering Health nor Oregon Health & Science University holds SOC 2 Type 2 certification.

Neither Kettering Health nor Oregon Health & Science University holds ISO 27001 certification.

Neither Kettering Health nor Oregon Health & Science University holds PCI DSS certification.

Neither Kettering Health nor Oregon Health & Science University holds HIPAA certification.

Neither Kettering Health nor Oregon Health & Science University holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References