Comparison Overview

Forge AHEAD Center

VS

Tulsa Health Department

Forge AHEAD Center

None
Last Update: 2025-11-27

Forge AHEAD Center is a regional comprehensive research center that focuses on the prevention and management of cardiometabolic diseases, including obesity, diabetes, and hypertension (HTN), associated with health disparities in Alabama, Mississippi, and Louisiana. Funded by a grant from the National Institute on Minority Health and Health Disparities (NIMHD), Forge AHEAD Center is a part of the Health Equity Action Network. The center is supported by the NIMHD award #P50MD017338, with the author(s) bearing sole responsibility for the content.

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 2
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Tulsa Health Department

5051 South 129th East Avenue, Tulsa, OK, 74134, US
Last Update: 2025-11-28
Between 750 and 799

Since its establishment in 1950, the Tulsa Health Department serves as the primary public health agency to more than 600,000 Tulsa County residents, including 13 municipalities and four unincorporated areas. The agency is one of two autonomous local health departments in Oklahoma, with statutory public health jurisdiction throughout Tulsa County and the City of Tulsa. THD’s mission is to improve the health and well-being of all Tulsa County residents, in order to make Tulsa County the healthiest county in the country. THD was among the first health departments in the U.S. to receive national accreditation through the Public Health Accreditation Board.

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 243
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/forge-ahead-center.jpeg
Forge AHEAD Center
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/tulsa-health-department.jpeg
Tulsa Health Department
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
Forge AHEAD Center
100%
Compliance Rate
0/4 Standards Verified
Tulsa Health Department
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Forge AHEAD Center in 2025.

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Tulsa Health Department in 2025.

Incident History — Forge AHEAD Center (X = Date, Y = Severity)

Forge AHEAD Center cyber incidents detection timeline including parent company and subsidiaries

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

Tulsa Health Department cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/forge-ahead-center.jpeg
Forge AHEAD Center
Incidents

No Incident

https://images.rankiteo.com/companyimages/tulsa-health-department.jpeg
Tulsa Health Department
Incidents

No Incident

FAQ

Tulsa Health Department company demonstrates a stronger AI Cybersecurity Score compared to Forge AHEAD Center company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Tulsa Health Department company has disclosed a higher number of cyber incidents compared to Forge AHEAD Center company.

In the current year, Tulsa Health Department company and Forge AHEAD Center company have not reported any cyber incidents.

Neither Tulsa Health Department company nor Forge AHEAD Center company has reported experiencing a ransomware attack publicly.

Neither Tulsa Health Department company nor Forge AHEAD Center company has reported experiencing a data breach publicly.

Neither Tulsa Health Department company nor Forge AHEAD Center company has reported experiencing targeted cyberattacks publicly.

Neither Forge AHEAD Center company nor Tulsa Health Department company has reported experiencing or disclosing vulnerabilities publicly.

Neither Forge AHEAD Center nor Tulsa Health Department holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Forge AHEAD Center company nor Tulsa Health Department company has publicly disclosed detailed information about the number of their subsidiaries.

Tulsa Health Department company employs more people globally than Forge AHEAD Center company, reflecting its scale as a Public Health.

Neither Forge AHEAD Center nor Tulsa Health Department holds SOC 2 Type 1 certification.

Neither Forge AHEAD Center nor Tulsa Health Department holds SOC 2 Type 2 certification.

Neither Forge AHEAD Center nor Tulsa Health Department holds ISO 27001 certification.

Neither Forge AHEAD Center nor Tulsa Health Department holds PCI DSS certification.

Neither Forge AHEAD Center nor Tulsa Health Department holds HIPAA certification.

Neither Forge AHEAD Center nor Tulsa Health Department holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.