Comparison Overview

University of Utah

VS

University of Kentucky

University of Utah

201 Presidents Circle, ROOM 203, Salt Lake City, ut, 84112-9008, US
Last Update: 2025-12-17
Between 700 and 749

The University of Utah, located in Salt Lake City in the foothills of the Wasatch Mountains, is the flagship institution of higher learning in Utah. Founded in 1850, it serves over 31,000 students from across the U.S. and the world. With over 72 major subjects at the undergraduate level and more than 90 major fields of study at the graduate level, including law and medicine, the university prepares students to live and compete in the global workplace. Known for its proximity to seven world-class ski resorts within 40 minutes of campus, the U encourages an active, holistic lifestyle, innovation and collaborative thinking to engage students, faculty and business leaders. The University of Utah became a member of the PAC-12 conference in July 2011. Technology and Commercialization The University of Utah is tops in the country for creating start-up companies from university research, according to a ranking by the Association of University Technology Managers (AUTM). See http://unews.utah.edu/news_releases/u-of-utah-no-1-for-startups for more information. Forbes magazine’s recent ranking of the “Best States for Business” pointed to “an educated labor force” as a big reason Utah came in at number one. The U supplies many of the employees for companies that keep expanding their operations in Utah, such as Goldman Sachs, Adobe, Omniture, Oracle, Ebay and many others. http://pac12info.utah.edu/commercialization-of-innovation/ Healthcare University of Utah Health Care recently ranked first in the nation in a prestigious national study. The University Health System Consortium’s 2010 Quality and Accountability Study compared 98 of the nation’s top academic medical centers and ranked them based on core quality measures, patient safety indicators, mortality rates, re-admission rates, and patient satisfaction scores. See more about University of Utah Health Care at http://healthcare.utah.edu/index.php

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

University of Kentucky

undefined, Lexington, KY, 40506, US
Last Update: 2025-12-17
Between 800 and 849

The University of Kentucky is a public, research-extensive, land grant university dedicated to improving people's lives through excellence in teaching, research, health care, cultural enrichment, and economic development for over 150 years. The University of Kentucky: - Facilitates learning, informed by scholarship and research. - Expands knowledge through research, scholarship and creative activity. - Serves a global community by disseminating, sharing and applying knowledge. The University, as the flagship institution, plays a critical leadership role for the Commonwealth by contributing to the economic development and quality of life within Kentucky's borders and beyond. The University nurtures a diverse community characterized by fairness and equal opportunity. From Paducah to Pikeville, Covington to Cumberland, the University of Kentucky touches lives across the Bluegrass State, providing education, cultural stimulation and economic development in all 120 counties. Considering that residents of all Kentucky counties benefit from the University's medical care, community service, innovative research and creative teaching and instruction, there's no question UK is The University of Kentucky.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/university-of-utah.jpeg
University of Utah
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/universityofkentucky.jpeg
University of Kentucky
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
University of Utah
100%
Compliance Rate
0/4 Standards Verified
University of Kentucky
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for University of Utah in 2025.

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for University of Kentucky in 2025.

Incident History — University of Utah (X = Date, Y = Severity)

University of Utah cyber incidents detection timeline including parent company and subsidiaries

Incident History — University of Kentucky (X = Date, Y = Severity)

University of Kentucky cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/university-of-utah.jpeg
University of Utah
Incidents

Date Detected: 08/2020
Type:Ransomware
Blog: Blog

Date Detected: 07/2020
Type:Breach
Attack Vector: Phishing
Blog: Blog
https://images.rankiteo.com/companyimages/universityofkentucky.jpeg
University of Kentucky
Incidents

No Incident

FAQ

University of Kentucky company demonstrates a stronger AI Cybersecurity Score compared to University of Utah company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

University of Utah company has historically faced a number of disclosed cyber incidents, whereas University of Kentucky company has not reported any.

In the current year, University of Kentucky company and University of Utah company have not reported any cyber incidents.

University of Utah company has confirmed experiencing a ransomware attack, while University of Kentucky company has not reported such incidents publicly.

University of Utah company has disclosed at least one data breach, while the other University of Kentucky company has not reported such incidents publicly.

Neither University of Kentucky company nor University of Utah company has reported experiencing targeted cyberattacks publicly.

Neither University of Utah company nor University of Kentucky company has reported experiencing or disclosing vulnerabilities publicly.

Neither University of Utah nor University of Kentucky holds any compliance certifications.

Neither company holds any compliance certifications.

University of Kentucky company has more subsidiaries worldwide compared to University of Utah company.

University of Kentucky company employs more people globally than University of Utah company, reflecting its scale as a Higher Education.

Neither University of Utah nor University of Kentucky holds SOC 2 Type 1 certification.

Neither University of Utah nor University of Kentucky holds SOC 2 Type 2 certification.

Neither University of Utah nor University of Kentucky holds ISO 27001 certification.

Neither University of Utah nor University of Kentucky holds PCI DSS certification.

Neither University of Utah nor University of Kentucky holds HIPAA certification.

Neither University of Utah nor University of Kentucky holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.

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
Description

Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.

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

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

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

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

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

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

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