Comparison Overview

NACCHO

VS

Center for Advancing Health Equity

NACCHO

1201 Eye Street, NW, 4th Floor, Washington, DC, US, 20005
Last Update: 2025-11-28
Between 700 and 749

The National Association of County and City Health Officials (NACCHO) is the national organization representing local health departments. NACCHO supports efforts that protect and improve the health of all people and all communities by promoting national policy, developing resources and programs, seeking health equity, and supporting effective local public health practice and systems.

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

Center for Advancing Health Equity

1006 S Michigan Ave, Chicago, 60605, US
Last Update: 2025-11-27

The Center for Advancing Health Equity in Rural and Underserved Communities (CAHE-RUC) provides a central location for the comprehensive evaluation of the health issues and diverse healthcare needs of rural and underserved communities. CAHE-RUC is a partnership between the Asian Health Coalition and the Penn State College of Medicine that brings together the assets of a world class research institution and a respected non-profit organization to investigate health disparities that disproportionately affect rural and minority communities throughout the country. The Center takes a multidisciplinary, collaborative approach to addressing gaps in clinical medicine and public health through a comprehensive program for research, health education, training, community engagement, policy, and information dissemination. CAHE-RUC provides an innovative model of partnership that demonstrates how community-level coalitions bring value, community access, and deeper translational impact to academic institutions.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/naccho.jpeg
NACCHO
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/center-for-asian-health-equity.jpeg
Center for Advancing Health Equity
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
NACCHO
100%
Compliance Rate
0/4 Standards Verified
Center for Advancing Health Equity
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for NACCHO in 2025.

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Center for Advancing Health Equity in 2025.

Incident History — NACCHO (X = Date, Y = Severity)

NACCHO cyber incidents detection timeline including parent company and subsidiaries

Incident History — Center for Advancing Health Equity (X = Date, Y = Severity)

Center for Advancing Health Equity cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/naccho.jpeg
NACCHO
Incidents

Date Detected: 7/2021
Type:Breach
Attack Vector: External Hacking
Blog: Blog
https://images.rankiteo.com/companyimages/center-for-asian-health-equity.jpeg
Center for Advancing Health Equity
Incidents

Date Detected: 1/2024
Type:Breach
Attack Vector: Email
Blog: Blog

Date Detected: 7/2023
Type:Breach
Motivation: financial gain, data theft
Blog: Blog

FAQ

Center for Advancing Health Equity company demonstrates a stronger AI Cybersecurity Score compared to NACCHO company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Center for Advancing Health Equity company has faced a higher number of disclosed cyber incidents historically compared to NACCHO company.

In the current year, Center for Advancing Health Equity company and NACCHO company have not reported any cyber incidents.

Neither Center for Advancing Health Equity company nor NACCHO company has reported experiencing a ransomware attack publicly.

Both Center for Advancing Health Equity company and NACCHO company have disclosed experiencing at least one data breach.

Neither Center for Advancing Health Equity company nor NACCHO company has reported experiencing targeted cyberattacks publicly.

Neither NACCHO company nor Center for Advancing Health Equity company has reported experiencing or disclosing vulnerabilities publicly.

Neither NACCHO nor Center for Advancing Health Equity holds any compliance certifications.

Neither company holds any compliance certifications.

Center for Advancing Health Equity company has more subsidiaries worldwide compared to NACCHO company.

NACCHO company employs more people globally than Center for Advancing Health Equity company, reflecting its scale as a Public Health.

Neither NACCHO nor Center for Advancing Health Equity holds SOC 2 Type 1 certification.

Neither NACCHO nor Center for Advancing Health Equity holds SOC 2 Type 2 certification.

Neither NACCHO nor Center for Advancing Health Equity holds ISO 27001 certification.

Neither NACCHO nor Center for Advancing Health Equity holds PCI DSS certification.

Neither NACCHO nor Center for Advancing Health Equity holds HIPAA certification.

Neither NACCHO nor Center for Advancing Health Equity 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