Comparison Overview

Healthy Together

VS

Zorg van de Zaak

Healthy Together

undefined, Miami, FL, undefined, US
Last Update: 2025-11-26

Healthy Together is a health technology company that provides SaaS solutions for Health & Humans Services Departments. Our mission is to improve collective health and make government more efficient. Healthy Together supports a “One Door” approach to eligibility, enrollment, and management for programs like Medicaid, SNAP, TANF and WIC, as well as behavioral health (988), disease surveillance, vital records, child welfare and more. State-level deployments include Utah, Florida, Oklahoma and Colorado. The United States Department of Veterans Affairs utilizes Healthy Together's mobile platform to provide over 18 million Veterans with access to their electronic health records and immunization history. Healthy Together's mobile application has reached #1 in the App Store Health & Fitness category and has over 225k reviews on the App Store and Play Store with a 4.9/5 star rating.

NAICS: 923
NAICS Definition:
Employees: 47
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Zorg van de Zaak

Vivaldiplantsoen 200, Utrecht, Utrecht, NL, 3533 JE
Last Update: 2025-11-27
Between 750 and 799

Wij geloven dat iedereen gelukkiger is als ze lekker aan het werk zijn, iets toevoegen aan de maatschappij, en zichzelf op positieve manier blijven ontwikkelen en uitdagen. Daarom zijn wij de arbodienst die verder kijkt dan verzuim. Wij maken onszelf het liefst volledig overbodig, en houden iedereen sterk aan het werk.

NAICS: 923
NAICS Definition: Administration of Human Resource Programs
Employees: 1,043
Subsidiaries: 11
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/healthytogethernow.jpeg
Healthy Together
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/zorgvandezaak.jpeg
Zorg van de Zaak
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
Healthy Together
100%
Compliance Rate
0/4 Standards Verified
Zorg van de Zaak
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 Healthy Together in 2025.

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

No incidents recorded for Zorg van de Zaak in 2025.

Incident History — Healthy Together (X = Date, Y = Severity)

Healthy Together cyber incidents detection timeline including parent company and subsidiaries

Incident History — Zorg van de Zaak (X = Date, Y = Severity)

Zorg van de Zaak cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/healthytogethernow.jpeg
Healthy Together
Incidents

No Incident

https://images.rankiteo.com/companyimages/zorgvandezaak.jpeg
Zorg van de Zaak
Incidents

No Incident

FAQ

Zorg van de Zaak company demonstrates a stronger AI Cybersecurity Score compared to Healthy Together company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Zorg van de Zaak company has disclosed a higher number of cyber incidents compared to Healthy Together company.

In the current year, Zorg van de Zaak company and Healthy Together company have not reported any cyber incidents.

Neither Zorg van de Zaak company nor Healthy Together company has reported experiencing a ransomware attack publicly.

Neither Zorg van de Zaak company nor Healthy Together company has reported experiencing a data breach publicly.

Neither Zorg van de Zaak company nor Healthy Together company has reported experiencing targeted cyberattacks publicly.

Neither Healthy Together company nor Zorg van de Zaak company has reported experiencing or disclosing vulnerabilities publicly.

Neither Healthy Together nor Zorg van de Zaak holds any compliance certifications.

Neither company holds any compliance certifications.

Zorg van de Zaak company has more subsidiaries worldwide compared to Healthy Together company.

Zorg van de Zaak company employs more people globally than Healthy Together company, reflecting its scale as a Health and Human Services.

Neither Healthy Together nor Zorg van de Zaak holds SOC 2 Type 1 certification.

Neither Healthy Together nor Zorg van de Zaak holds SOC 2 Type 2 certification.

Neither Healthy Together nor Zorg van de Zaak holds ISO 27001 certification.

Neither Healthy Together nor Zorg van de Zaak holds PCI DSS certification.

Neither Healthy Together nor Zorg van de Zaak holds HIPAA certification.

Neither Healthy Together nor Zorg van de Zaak 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