Comparison Overview

kegra GmbH

VS

Cayaba Care

kegra GmbH

Am Ellernbusch 18-20, Düren, 52355, DE
Last Update: 2025-11-21
Between 750 and 799

Die kegra GmbH bietet Dienstleistungen wie Pflegeberatung, Case & Care Management und das Online-Netzwerk Pflegelando an. Das Ziel ist, Kunden bei pflegerelevanten Themen zu beraten und zu unterstützen. Case & Care Manager arbeiten gemeinsam mit Kunden an der Koordination und Gestaltung von Pflege- und Betreuungsangeboten, insbesondere für Menschen, die außerhalb der Klinik auf Intensiv- und Beatmungspflege angewiesen sind.

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

Cayaba Care

Last Update: 2025-11-21
Between 750 and 799

The US is one of the most dangerous developed countries in which to give birth, and these poor maternal outcomes disproportionately impact minority women and underserved populations across major US cities. Cayaba Care is focused on closing this gap by providing a complete set of maternity services, including pregnancy, birth planning, and postpartum, as well as lactation, doula, nutrition, and mental health support. Our care model focuses on the integration, not replacement, of patients’ primary Obstetric providers, and we provide personalized support via a combination of in-home, in-clinic, and virtual in order to reduce any barriers to patients receiving recommended care. Our program is designed by OBs and fellow moms who have a depth of experience in providing culturally competent care tailored to our patients' needs.

NAICS: 923
NAICS Definition: Administration of Human Resource Programs
Employees: 42
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/kegra-gmbh.jpeg
kegra GmbH
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/cayabacare.jpeg
Cayaba Care
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
kegra GmbH
100%
Compliance Rate
0/4 Standards Verified
Cayaba Care
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 kegra GmbH in 2025.

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

No incidents recorded for Cayaba Care in 2025.

Incident History — kegra GmbH (X = Date, Y = Severity)

kegra GmbH cyber incidents detection timeline including parent company and subsidiaries

Incident History — Cayaba Care (X = Date, Y = Severity)

Cayaba Care cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/kegra-gmbh.jpeg
kegra GmbH
Incidents

No Incident

https://images.rankiteo.com/companyimages/cayabacare.jpeg
Cayaba Care
Incidents

No Incident

FAQ

kegra GmbH company demonstrates a stronger AI Cybersecurity Score compared to Cayaba Care company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Cayaba Care company has disclosed a higher number of cyber incidents compared to kegra GmbH company.

In the current year, Cayaba Care company and kegra GmbH company have not reported any cyber incidents.

Neither Cayaba Care company nor kegra GmbH company has reported experiencing a ransomware attack publicly.

Neither Cayaba Care company nor kegra GmbH company has reported experiencing a data breach publicly.

Neither Cayaba Care company nor kegra GmbH company has reported experiencing targeted cyberattacks publicly.

Neither kegra GmbH company nor Cayaba Care company has reported experiencing or disclosing vulnerabilities publicly.

Neither kegra GmbH nor Cayaba Care holds any compliance certifications.

Neither company holds any compliance certifications.

Neither kegra GmbH company nor Cayaba Care company has publicly disclosed detailed information about the number of their subsidiaries.

Cayaba Care company employs more people globally than kegra GmbH company, reflecting its scale as a Health and Human Services.

Neither kegra GmbH nor Cayaba Care holds SOC 2 Type 1 certification.

Neither kegra GmbH nor Cayaba Care holds SOC 2 Type 2 certification.

Neither kegra GmbH nor Cayaba Care holds ISO 27001 certification.

Neither kegra GmbH nor Cayaba Care holds PCI DSS certification.

Neither kegra GmbH nor Cayaba Care holds HIPAA certification.

Neither kegra GmbH nor Cayaba Care 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