Comparison Overview

UC San Diego

VS

Brigham Young University

UC San Diego

9500 Gilman Dr, La Jolla, CA, US, 92093
Last Update: 2026-04-01
Between 800 and 849

Recognized as one of the top 15 research universities worldwide, our culture of collaboration sparks discoveries that advance society and drive economic impact. Everything we do is dedicated to ensuring our students have the opportunity to become changemakers, equipped with the multidisciplinary tools needed to accelerate answers to our world’s most pressing issues.

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

Brigham Young University

Main Campus, Provo, UT, US, 84602
Last Update: 2026-03-29
Between 800 and 849

We believe a world yearning for hope and joy needs the graduates of Brigham Young University—disciples of Jesus Christ who are driven by love for God and His children and who are prepared to serve and lead. This preparation demands a unique university model: at BYU, belief enhances inquiry, study amplifies faith, and revelation leads to rich understanding; at BYU, helping students develop their full divine potential is central to both our teaching and our scholarship. As the flagship higher education institution of The Church of Jesus Christ of Latter-day Saints, BYU strives to be among the exceptional universities in the world and an essential university for the world.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ucsandiego.jpeg
UC San Diego
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/brigham-young-university.jpeg
Brigham Young 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
UC San Diego
100%
Compliance Rate
0/4 Standards Verified
Brigham Young University
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for UC San Diego in 2026.

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for Brigham Young University in 2026.

Incident History — UC San Diego (X = Date, Y = Severity)

UC San Diego cyber incidents detection timeline including parent company and subsidiaries

Incident History — Brigham Young University (X = Date, Y = Severity)

Brigham Young University cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ucsandiego.jpeg
UC San Diego
Incidents

Date Detected: 3/2026
Type:Breach
Attack Vector: Compromised file transfer application (Accellion FTA)
Blog: Blog

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

Date Detected: 1/2024
Type:Breach
Attack Vector: Phishing
Blog: Blog
https://images.rankiteo.com/companyimages/brigham-young-university.jpeg
Brigham Young University
Incidents

Date Detected: 03/2012
Type:Data Leak
Attack Vector: Email
Motivation: Accidental
Blog: Blog

FAQ

UC San Diego company demonstrates a stronger AI Cybersecurity Score compared to Brigham Young University company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

UC San Diego company has faced a higher number of disclosed cyber incidents historically compared to Brigham Young University company.

In the current year, UC San Diego company has reported more cyber incidents than Brigham Young University company.

UC San Diego company has confirmed experiencing a ransomware attack, while Brigham Young University company has not reported such incidents publicly.

UC San Diego company has disclosed at least one data breach, while the other Brigham Young University company has not reported such incidents publicly.

Neither Brigham Young University company nor UC San Diego company has reported experiencing targeted cyberattacks publicly.

Neither UC San Diego company nor Brigham Young University company has reported experiencing or disclosing vulnerabilities publicly.

Neither UC San Diego nor Brigham Young University holds any compliance certifications.

Neither company holds any compliance certifications.

UC San Diego company has more subsidiaries worldwide compared to Brigham Young University company.

UC San Diego company employs more people globally than Brigham Young University company, reflecting its scale as a Higher Education.

Neither UC San Diego nor Brigham Young University holds SOC 2 Type 1 certification.

Neither UC San Diego nor Brigham Young University holds SOC 2 Type 2 certification.

Neither UC San Diego nor Brigham Young University holds ISO 27001 certification.

Neither UC San Diego nor Brigham Young University holds PCI DSS certification.

Neither UC San Diego nor Brigham Young University holds HIPAA certification.

Neither UC San Diego nor Brigham Young University holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was found in Nothings stb up to 1.26. Impacted is the function stbtt_InitFont_internal in the library stb_truetype.h of the component TTF File Handler. Performing a manipulation results in out-of-bounds read. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:N/A:P
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/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

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read in VS6ComFile!get_macro_mem_COM. Opening a crafted V7 file may lead to information disclosure from the affected product.

Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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

V-SFT versions 6.2.10.0 and prior contain a stack-based buffer overflow in VS6ComFile!CSaveData::_conv_AnimationItem. Opening a crafted V7 file may lead to arbitrary code execution on the affected product.

Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read vulnerability in VS6MemInIF!set_temp_type_default. Opening a crafted V7 file may lead to information disclosure from the affected product.

Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read vulnerability in VS6ComFile!load_link_inf. Opening a crafted V7 file may lead to information disclosure from the affected product.

Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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