Comparison Overview

Tulsa Tech

VS

University of Michigan

Tulsa Tech

PO Box 477200, Tulsa, OK, 74147-7200, US
Last Update: 2025-12-25
Between 750 and 799

The oldest and largest technology center in Oklahoma’s Career Tech System, Tulsa Tech is a career & technology center school district dedicated to accelerating independence in our students through hands-on learning in state-of-the-art facilities. Tulsa Tech helps high school and adult students from across the Tulsa region explore new careers, upgrade their training and skills, and pursue their dreams. Find out more about how we can help prepare you for success in the workplace at http://tulsatech.edu. Tulsa Tech does not discriminate on the basis of race, color, sex, pregnancy, gender, gender expression or identity, national origin, religion, disability, veteran status, sexual orientation, age or genetic information. The following person(s) has been designated to handle inquiries regarding non-discrimination policies: Title IX Coordinator, Pam Winterscheidt, [email protected], and 504 Coordinator, Elena Morales, [email protected], 3638 S. Memorial Dr, Tulsa OK, 74145, 918-828-5000.

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

University of Michigan

1109 Geddes Ave, Ann Arbor, Michigan, 48104, US
Last Update: 2025-12-17
Between 700 and 749

The mission of the University of Michigan is to serve the people of Michigan and the world through preeminence in creating, communicating, preserving, and applying knowledge, art, and academic values, and in developing leaders and citizens who will challenge the present and enrich the future. Why Work at Michigan? Being part of something greater, of serving a larger mission of discovery and care — that's the heart of what drives people to work at Michigan. In some way, great or small, every person here helps to advance this world-class institution. It's adding a purpose to your profession. Work at Michigan and become a victor for the greater good.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/tulsa-tech.jpeg
Tulsa Tech
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/university-of-michigan.jpeg
University of Michigan
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
Tulsa Tech
100%
Compliance Rate
0/4 Standards Verified
University of Michigan
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Higher Education Industry Average (This Year)

No incidents recorded for Tulsa Tech in 2025.

Incidents vs Higher Education Industry Average (This Year)

University of Michigan has 21.95% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — Tulsa Tech (X = Date, Y = Severity)

Tulsa Tech cyber incidents detection timeline including parent company and subsidiaries

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/tulsa-tech.jpeg
Tulsa Tech
Incidents

Date Detected: 6/1986
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/university-of-michigan.jpeg
University of Michigan
Incidents

Date Detected: 3/2025
Type:Breach
Attack Vector: Hacking, Encryption Cracking, Unauthorized Access
Motivation: Unauthorized access to personal information
Blog: Blog

Date Detected: 08/2023
Type:Cyber Attack
Blog: Blog

FAQ

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

University of Michigan company has faced a higher number of disclosed cyber incidents historically compared to Tulsa Tech company.

In the current year, University of Michigan company has reported more cyber incidents than Tulsa Tech company.

Neither University of Michigan company nor Tulsa Tech company has reported experiencing a ransomware attack publicly.

Both University of Michigan company and Tulsa Tech company have disclosed experiencing at least one data breach.

University of Michigan company has reported targeted cyberattacks, while Tulsa Tech company has not reported such incidents publicly.

Neither Tulsa Tech company nor University of Michigan company has reported experiencing or disclosing vulnerabilities publicly.

Neither Tulsa Tech nor University of Michigan holds any compliance certifications.

Neither company holds any compliance certifications.

University of Michigan company has more subsidiaries worldwide compared to Tulsa Tech company.

University of Michigan company employs more people globally than Tulsa Tech company, reflecting its scale as a Higher Education.

Neither Tulsa Tech nor University of Michigan holds SOC 2 Type 1 certification.

Neither Tulsa Tech nor University of Michigan holds SOC 2 Type 2 certification.

Neither Tulsa Tech nor University of Michigan holds ISO 27001 certification.

Neither Tulsa Tech nor University of Michigan holds PCI DSS certification.

Neither Tulsa Tech nor University of Michigan holds HIPAA certification.

Neither Tulsa Tech nor University of Michigan holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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