Comparison Overview

Cigna Healthcare

VS

Oregon Health & Science University

Cigna Healthcare

900 Cottage Grove Road, Bloomfield, 06002, US
Last Update: 2025-12-09
Between 800 and 849

We are a health benefits provider that advocates for better health through every stage of life. We guide our customers through the health care system, empowering them with the information and insight they need to improve their health and vitality.

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

Oregon Health & Science University

3181 SW Sam Jackson Park Rd, Portland, Oregon, 97239, US
Last Update: 2025-12-09
Between 750 and 799

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: 16,777
Subsidiaries: 6
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/cigna.jpeg
Cigna Healthcare
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
Cigna Healthcare
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 Cigna Healthcare in 2025.

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

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

Incident History — Cigna Healthcare (X = Date, Y = Severity)

Cigna Healthcare 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/cigna.jpeg
Cigna Healthcare
Incidents

Date Detected: 3/2012
Type:Breach
Attack Vector: Email
Blog: Blog

Date Detected: 10/2008
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/ohsu.jpeg
Oregon Health & Science University
Incidents

No Incident

FAQ

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

Cigna Healthcare 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 Cigna Healthcare company have not reported any cyber incidents.

Neither Oregon Health & Science University company nor Cigna Healthcare company has reported experiencing a ransomware attack publicly.

Cigna Healthcare company has disclosed at least one data breach, while the other Oregon Health & Science University company has not reported such incidents publicly.

Neither Oregon Health & Science University company nor Cigna Healthcare company has reported experiencing targeted cyberattacks publicly.

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

Neither Cigna Healthcare 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 Cigna Healthcare company.

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

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

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

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

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

Neither Cigna Healthcare nor Oregon Health & Science University holds HIPAA certification.

Neither Cigna Healthcare nor Oregon Health & Science University holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 9.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

Risk Information
cvss3
Base: 8.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

Risk Information
cvss3
Base: 5.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N