Comparison Overview

Mackinac Center for Public Policy

VS

Tampa Bay Partnership

Mackinac Center for Public Policy

undefined, Midland, undefined, undefined, US
Last Update: 2025-11-25
Between 700 and 749

The Mackinac Center for Public Policy is a nonpartisan research and educational institute dedicated to improving the quality of life for all Michigan residents by promoting sound solutions to state and local policy questions. The Mackinac Center assists policy makers, scholars, business people, the media and the public by providing objective analysis of Michigan issues. The goal of all Center reports, commentaries and educational programs is to equip Michigan residents and other decision makers to better evaluate policy options. The Mackinac Center for Public Policy is broadening the debate on issues that has for many years been dominated by the belief that government intervention should be the standard solution. Our main initiatives focus on fiscal, labor and education policy, and we also house the Mackinac Center Legal Foundation, a public-interest law firm that uses strategic litigation and public outreach to secure the liberties of Michigan’s residents, workers, students and entrepreneurs.

NAICS: 921
NAICS Definition: Executive, Legislative, and Other General Government Support
Employees: 63
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Tampa Bay Partnership

4300 W Cypress St, Tampa, Florida, 33607, US
Last Update: 2025-11-23
Between 700 and 749

The Tampa Bay Partnership is a coalition of regional business leaders, joined by a shared commitment to improving the personal and economic well-being of Tampa Bay residents. Formally incorporated in 1994, and re-established in 2016 as a regional research and public policy organization, the Partnership works with the region’s top employers, along with a diverse group of government and nonprofit partners, to identify and address the toughest challenges facing our community, including transportation, talent, racial equity and other emerging issues.

NAICS: 921
NAICS Definition:
Employees: 17
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/mackinac-center-for-public-policy.jpeg
Mackinac Center for Public Policy
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/tampa-bay-partnership.jpeg
Tampa Bay Partnership
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
Mackinac Center for Public Policy
100%
Compliance Rate
0/4 Standards Verified
Tampa Bay Partnership
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Mackinac Center for Public Policy in 2025.

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Tampa Bay Partnership in 2025.

Incident History — Mackinac Center for Public Policy (X = Date, Y = Severity)

Mackinac Center for Public Policy cyber incidents detection timeline including parent company and subsidiaries

Incident History — Tampa Bay Partnership (X = Date, Y = Severity)

Tampa Bay Partnership cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/mackinac-center-for-public-policy.jpeg
Mackinac Center for Public Policy
Incidents

No Incident

https://images.rankiteo.com/companyimages/tampa-bay-partnership.jpeg
Tampa Bay Partnership
Incidents

No Incident

FAQ

Mackinac Center for Public Policy company demonstrates a stronger AI Cybersecurity Score compared to Tampa Bay Partnership company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Tampa Bay Partnership company has disclosed a higher number of cyber incidents compared to Mackinac Center for Public Policy company.

In the current year, Tampa Bay Partnership company and Mackinac Center for Public Policy company have not reported any cyber incidents.

Neither Tampa Bay Partnership company nor Mackinac Center for Public Policy company has reported experiencing a ransomware attack publicly.

Neither Tampa Bay Partnership company nor Mackinac Center for Public Policy company has reported experiencing a data breach publicly.

Neither Tampa Bay Partnership company nor Mackinac Center for Public Policy company has reported experiencing targeted cyberattacks publicly.

Neither Mackinac Center for Public Policy company nor Tampa Bay Partnership company has reported experiencing or disclosing vulnerabilities publicly.

Neither Mackinac Center for Public Policy nor Tampa Bay Partnership holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Mackinac Center for Public Policy company nor Tampa Bay Partnership company has publicly disclosed detailed information about the number of their subsidiaries.

Mackinac Center for Public Policy company employs more people globally than Tampa Bay Partnership company, reflecting its scale as a Public Policy Offices.

Neither Mackinac Center for Public Policy nor Tampa Bay Partnership holds SOC 2 Type 1 certification.

Neither Mackinac Center for Public Policy nor Tampa Bay Partnership holds SOC 2 Type 2 certification.

Neither Mackinac Center for Public Policy nor Tampa Bay Partnership holds ISO 27001 certification.

Neither Mackinac Center for Public Policy nor Tampa Bay Partnership holds PCI DSS certification.

Neither Mackinac Center for Public Policy nor Tampa Bay Partnership holds HIPAA certification.

Neither Mackinac Center for Public Policy nor Tampa Bay Partnership 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