Comparison Overview

PACE Health Management

VS

Generate Health STL

PACE Health Management

24 Yuille St, Frankston South, 3199, AU
Last Update: 2025-11-21
View Profile
Between 750 and 799
https://www.pacehm.com.au

Our mission is to “Help People Help Themselves” Our allied health team work across a wide scope of practice. We exist to foster behaviour change to help develop long term sustainable outcomes and better facilitate self-management of chronic diseases or conditions. We will achieve our goals by collaborating and developing our diverse skill sets, by being flexible in our thinking and behaviour, and being persistent. We will employ people who share our goals and who have the skills that we will support and enhance to achieve those goals.

NAICS: 923
NAICS Definition: Administration of Human Resource Programs
Employees: 66
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

Generate Health STL

undefined, St Louis, undefined, undefined, us
Last Update: 2025-11-26
Between 750 and 799
http://www.generatehealthstl.org

Generate Health believes St. Louis can be a more thriving region if we improve the health and well-being of Black moms, birthing people, babies and families. As a coalition, we build collective power to advocate for racially equitable policies and practices that center, support and celebrate Black families throughout their pregnancy and parenthood journeys.

NAICS: 923
NAICS Definition:
Employees: 15
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/pace-health-management.jpeg
PACE Health Management
—
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/generate-health-stl.jpeg
Generate Health STL
—
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
PACE Health Management
100%
Compliance Rate
0/4 Standards Verified
Generate Health STL
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Health and Human Services Industry Average (This Year)

No incidents recorded for PACE Health Management in 2025.

Incidents vs Health and Human Services Industry Average (This Year)

No incidents recorded for Generate Health STL in 2025.

Incident History — PACE Health Management (X = Date, Y = Severity)

PACE Health Management cyber incidents detection timeline including parent company and subsidiaries

Incident History — Generate Health STL (X = Date, Y = Severity)

Generate Health STL cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pace-health-management.jpeg
PACE Health Management
Incidents

No Incident

https://images.rankiteo.com/companyimages/generate-health-stl.jpeg
Generate Health STL
Incidents

No Incident

FAQ

PACE Health Management company demonstrates a stronger AI Cybersecurity Score compared to Generate Health STL company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Generate Health STL company has disclosed a higher number of cyber incidents compared to PACE Health Management company.

In the current year, Generate Health STL company and PACE Health Management company have not reported any cyber incidents.

Neither Generate Health STL company nor PACE Health Management company has reported experiencing a ransomware attack publicly.

Neither Generate Health STL company nor PACE Health Management company has reported experiencing a data breach publicly.

Neither Generate Health STL company nor PACE Health Management company has reported experiencing targeted cyberattacks publicly.

Neither PACE Health Management company nor Generate Health STL company has reported experiencing or disclosing vulnerabilities publicly.

Neither PACE Health Management nor Generate Health STL holds any compliance certifications.

Neither company holds any compliance certifications.

Neither PACE Health Management company nor Generate Health STL company has publicly disclosed detailed information about the number of their subsidiaries.

PACE Health Management company employs more people globally than Generate Health STL company, reflecting its scale as a Health and Human Services.

Neither PACE Health Management nor Generate Health STL holds SOC 2 Type 1 certification.

Neither PACE Health Management nor Generate Health STL holds SOC 2 Type 2 certification.

Neither PACE Health Management nor Generate Health STL holds ISO 27001 certification.

Neither PACE Health Management nor Generate Health STL holds PCI DSS certification.

Neither PACE Health Management nor Generate Health STL holds HIPAA certification.

Neither PACE Health Management nor Generate Health STL 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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References