Comparison Overview

The California State University

VS

Brigham Young University

The California State University

401 Golden Shore, Long Beach, CA, 90802, US
Last Update: 2025-11-20
Between 800 and 849

The California State University is the largest system of four-year higher education in the country, with 23 campuses, 56,000 faculty and staff and more than 450,000 students. Created in 1960, the mission of the CSU is to provide high-quality, affordable education to meet the ever-changing needs of California. With its commitment to quality, opportunity, and student success, the CSU is renowned for superb teaching, innovative research and for producing job-ready graduates. The CSU powers California and the nation, sending nearly 127,000 career-ready graduates into the workforce each year. In fact, one in every 20 Americans holding a college degree earned it at the CSU and our alumni are 4 million strong.

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

Brigham Young University

Main Campus, Provo, UT, US, 84602
Last Update: 2025-11-23
Between 750 and 799

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,356
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/the-california-state-university.jpeg
The California State 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
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
The California State University
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 The California State University in 2025.

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for Brigham Young University in 2025.

Incident History — The California State University (X = Date, Y = Severity)

The California State University 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/the-california-state-university.jpeg
The California State University
Incidents

Date Detected: 12/2018
Type:Breach
Attack Vector: Unauthorized Access
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

The California State University company demonstrates a stronger AI Cybersecurity Score compared to Brigham Young University company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

The California State University and Brigham Young University have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Brigham Young University company and The California State University company have not reported any cyber incidents.

Neither Brigham Young University company nor The California State University company has reported experiencing a ransomware attack publicly.

The California State University 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 The California State University company has reported experiencing targeted cyberattacks publicly.

Neither The California State University company nor Brigham Young University company has reported experiencing or disclosing vulnerabilities publicly.

Neither The California State University nor Brigham Young University holds any compliance certifications.

Neither company holds any compliance certifications.

The California State University company has more subsidiaries worldwide compared to Brigham Young University company.

The California State University company employs more people globally than Brigham Young University company, reflecting its scale as a Higher Education.

Neither The California State University nor Brigham Young University holds SOC 2 Type 1 certification.

Neither The California State University nor Brigham Young University holds SOC 2 Type 2 certification.

Neither The California State University nor Brigham Young University holds ISO 27001 certification.

Neither The California State University nor Brigham Young University holds PCI DSS certification.

Neither The California State University nor Brigham Young University holds HIPAA certification.

Neither The California State University nor Brigham Young University 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