Comparison Overview

Baylor College of Medicine

VS

University of California, San Francisco

Baylor College of Medicine

One Baylor Plaza, Houston, Texas, 77030-3498, US
Last Update: 2025-11-27
Between 750 and 799

Baylor College of Medicine is a health sciences university that creates knowledge and applies science and discoveries to further education, healthcare and community service locally and globally. Located in the Texas Medical Center, Baylor College of Medicine has affiliations with eight teaching hospitals, each known for medical excellence. The college has total research support of over $400 million annually, and more than 90 research and patient-care centers and units. Currently, Baylor College of Medicine trains more than 3,000 medical, graduate, nurse anesthesia, physician assistant, orthotics and prosthetics and genetic counseling students, as well as residents and post-doctoral fellows.

NAICS: 6113
NAICS Definition: Colleges, Universities, and Professional Schools
Employees: 12,954
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0

University of California, San Francisco

530 Parnassus Ave, San Francisco, California, US, 94122
Last Update: 2025-11-23
Between 650 and 699

UC San Francisco is driven by the idea that when the best research, the best education and the best patient care converge, great breakthroughs are achieved. We pursue this integrated excellence with singular focus, fueled by collaboration among our top-ranked professional and graduate schools, medical center, research programs and support teams.

NAICS: 6113
NAICS Definition: Colleges, Universities, and Professional Schools
Employees: 21,225
Subsidiaries: 57
12-month incidents
0
Known data breaches
14
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/baylor-college-of-medicine.jpeg
Baylor College of 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
https://images.rankiteo.com/companyimages/ucsf.jpeg
University of California, San Francisco
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
Baylor College of Medicine
100%
Compliance Rate
0/4 Standards Verified
University of California, San Francisco
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for Baylor College of Medicine in 2025.

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for University of California, San Francisco in 2025.

Incident History — Baylor College of Medicine (X = Date, Y = Severity)

Baylor College of Medicine cyber incidents detection timeline including parent company and subsidiaries

Incident History — University of California, San Francisco (X = Date, Y = Severity)

University of California, San Francisco cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/baylor-college-of-medicine.jpeg
Baylor College of Medicine
Incidents

No Incident

https://images.rankiteo.com/companyimages/ucsf.jpeg
University of California, San Francisco
Incidents

Date Detected: 12/2024
Type:Ransomware
Motivation: Financial Gain
Blog: Blog

Date Detected: 1/2024
Type:Breach
Attack Vector: Phishing
Blog: Blog

Date Detected: 10/2023
Type:Ransomware
Motivation: Financial Gain
Blog: Blog

FAQ

Baylor College of Medicine company demonstrates a stronger AI Cybersecurity Score compared to University of California, San Francisco company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

University of California, San Francisco company has historically faced a number of disclosed cyber incidents, whereas Baylor College of Medicine company has not reported any.

In the current year, University of California, San Francisco company and Baylor College of Medicine company have not reported any cyber incidents.

University of California, San Francisco company has confirmed experiencing a ransomware attack, while Baylor College of Medicine company has not reported such incidents publicly.

University of California, San Francisco company has disclosed at least one data breach, while Baylor College of Medicine company has not reported such incidents publicly.

Neither University of California, San Francisco company nor Baylor College of Medicine company has reported experiencing targeted cyberattacks publicly.

Neither Baylor College of Medicine company nor University of California, San Francisco company has reported experiencing or disclosing vulnerabilities publicly.

Neither Baylor College of Medicine nor University of California, San Francisco holds any compliance certifications.

Neither company holds any compliance certifications.

University of California, San Francisco company has more subsidiaries worldwide compared to Baylor College of Medicine company.

University of California, San Francisco company employs more people globally than Baylor College of Medicine company, reflecting its scale as a Higher Education.

Neither Baylor College of Medicine nor University of California, San Francisco holds SOC 2 Type 1 certification.

Neither Baylor College of Medicine nor University of California, San Francisco holds SOC 2 Type 2 certification.

Neither Baylor College of Medicine nor University of California, San Francisco holds ISO 27001 certification.

Neither Baylor College of Medicine nor University of California, San Francisco holds PCI DSS certification.

Neither Baylor College of Medicine nor University of California, San Francisco holds HIPAA certification.

Neither Baylor College of Medicine nor University of California, San Francisco holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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