Comparison Overview

Grossmont Healthcare District

VS

NASTAD

Grossmont Healthcare District

9001 Wakarusa St, La Mesa, California, 91942-3300, US
Last Update: 2025-11-28

The Grossmont Healthcare District (GHD) is a public agency that supports the health & wellness of East San Diego County. We operate a Health & Wellness Library, fund local nonprofits through grants and sponsorships, support the region's future generations through scholarships, and offer free wellness programs to the community. The District is governed by a five-member Board of Directors, elected at large to four-year terms, representing more than 500,000 people living within the District's 750 square miles.

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

NASTAD

444 North Capitol Street NW, Washington, 20001, US
Last Update: 2025-11-27
Between 750 and 799

NASTAD is a leading non-partisan non-profit association that represents public health officials who administer HIV and hepatitis programs in the U.S. We work to advance the health and dignity of people living with and impacted by HIV/AIDS, viral hepatitis, and intersecting epidemics by strengthening governmental public health through advocacy, capacity building, and social justice. Each of NASTAD’s seven programmatic teams—Health Care Access, Health Systems Integration, Policy & Legislative Affairs, Hepatitis, Prevention, Health Equity, and Drug User Health—interpret and influence policies, conduct trainings, offer technical assistance, and provide advocacy mobilization for U.S. health departments to improve health outcomes for people living with HIV and hepatitis. NASTAD's vision is a world committed to ending HIV/AIDS, viral hepatitis, and intersecting epidemics.

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 107
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/grossmonthealthcare.jpeg
Grossmont Healthcare District
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/nastad.jpeg
NASTAD
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
Grossmont Healthcare District
100%
Compliance Rate
0/4 Standards Verified
NASTAD
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Grossmont Healthcare District in 2025.

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for NASTAD in 2025.

Incident History — Grossmont Healthcare District (X = Date, Y = Severity)

Grossmont Healthcare District cyber incidents detection timeline including parent company and subsidiaries

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

NASTAD cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/grossmonthealthcare.jpeg
Grossmont Healthcare District
Incidents

No Incident

https://images.rankiteo.com/companyimages/nastad.jpeg
NASTAD
Incidents

No Incident

FAQ

NASTAD company demonstrates a stronger AI Cybersecurity Score compared to Grossmont Healthcare District company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, NASTAD company has disclosed a higher number of cyber incidents compared to Grossmont Healthcare District company.

In the current year, NASTAD company and Grossmont Healthcare District company have not reported any cyber incidents.

Neither NASTAD company nor Grossmont Healthcare District company has reported experiencing a ransomware attack publicly.

Neither NASTAD company nor Grossmont Healthcare District company has reported experiencing a data breach publicly.

Neither NASTAD company nor Grossmont Healthcare District company has reported experiencing targeted cyberattacks publicly.

Neither Grossmont Healthcare District company nor NASTAD company has reported experiencing or disclosing vulnerabilities publicly.

Neither Grossmont Healthcare District nor NASTAD holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Grossmont Healthcare District company nor NASTAD company has publicly disclosed detailed information about the number of their subsidiaries.

NASTAD company employs more people globally than Grossmont Healthcare District company, reflecting its scale as a Public Health.

Neither Grossmont Healthcare District nor NASTAD holds SOC 2 Type 1 certification.

Neither Grossmont Healthcare District nor NASTAD holds SOC 2 Type 2 certification.

Neither Grossmont Healthcare District nor NASTAD holds ISO 27001 certification.

Neither Grossmont Healthcare District nor NASTAD holds PCI DSS certification.

Neither Grossmont Healthcare District nor NASTAD holds HIPAA certification.

Neither Grossmont Healthcare District nor NASTAD 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.