Comparison Overview

Jefferson County Public Health

VS

AgriSafe Network

Jefferson County Public Health

645 Parfet St, None, Lakewood, Colorado, US, None
Last Update: 2025-11-28
View Profile
Between 750 and 799
http://www.jeffco.us/public-health

Jefferson County Public Health (JCPH) is a nationally accredited health department committed to promoting health and preventing injury and disease for the residents of Jefferson County, Colorado. Public health is what we as a society do collectively to prevent illness and premature death and promote health in our neighborhoods and communities.

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

AgriSafe Network

8342 NICC Drive, Peosta, 52068, US
Last Update: 2025-11-28
Between 750 and 799
http://www.agrisafe.org

AgriSafe is an international 501©3 organization representing health and safety professionals who strive to reduce health disparities found among the agricultural community. Our mission is to support a growing network of trained agricultural health and safety professionals that assure access to preventative services for farm families and the agricultural community. Our impact is realized across the globe because we utilize web-based technology to deliver the best trainings by experts in the field.

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 27
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/jefferson-county-public-health.jpeg
Jefferson County Public Health
—
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/agrisafe-network.jpeg
AgriSafe Network
—
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
Jefferson County Public Health
100%
Compliance Rate
0/4 Standards Verified
AgriSafe Network
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Jefferson County Public Health in 2025.

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for AgriSafe Network in 2025.

Incident History — Jefferson County Public Health (X = Date, Y = Severity)

Jefferson County Public Health cyber incidents detection timeline including parent company and subsidiaries

Incident History — AgriSafe Network (X = Date, Y = Severity)

AgriSafe Network cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/jefferson-county-public-health.jpeg
Jefferson County Public Health
Incidents

No Incident

https://images.rankiteo.com/companyimages/agrisafe-network.jpeg
AgriSafe Network
Incidents

No Incident

FAQ

Jefferson County Public Health company demonstrates a stronger AI Cybersecurity Score compared to AgriSafe Network company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, AgriSafe Network company has disclosed a higher number of cyber incidents compared to Jefferson County Public Health company.

In the current year, AgriSafe Network company and Jefferson County Public Health company have not reported any cyber incidents.

Neither AgriSafe Network company nor Jefferson County Public Health company has reported experiencing a ransomware attack publicly.

Neither AgriSafe Network company nor Jefferson County Public Health company has reported experiencing a data breach publicly.

Neither AgriSafe Network company nor Jefferson County Public Health company has reported experiencing targeted cyberattacks publicly.

Neither Jefferson County Public Health company nor AgriSafe Network company has reported experiencing or disclosing vulnerabilities publicly.

Neither Jefferson County Public Health nor AgriSafe Network holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Jefferson County Public Health company nor AgriSafe Network company has publicly disclosed detailed information about the number of their subsidiaries.

Jefferson County Public Health company employs more people globally than AgriSafe Network company, reflecting its scale as a Public Health.

Neither Jefferson County Public Health nor AgriSafe Network holds SOC 2 Type 1 certification.

Neither Jefferson County Public Health nor AgriSafe Network holds SOC 2 Type 2 certification.

Neither Jefferson County Public Health nor AgriSafe Network holds ISO 27001 certification.

Neither Jefferson County Public Health nor AgriSafe Network holds PCI DSS certification.

Neither Jefferson County Public Health nor AgriSafe Network holds HIPAA certification.

Neither Jefferson County Public Health nor AgriSafe Network 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.

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

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

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

Published
Date
2025-11-27
Updated
Date
2025-11-27
References
Description

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

Published
Date
2025-11-27
Updated
Date
2025-11-27
References