Comparison Overview

Delaware Guidance Services for Children and Youth, Inc.

VS

Courage to Caregivers, Inc.

Delaware Guidance Services for Children and Youth, Inc.

1200 N. French Street, Wilmington, 19801, US
Last Update: 2026-01-19

Delaware Guidance Services for Children & Youth, Inc. (DGS) has been serving Delaware’s families since 1953 and is the largest not-for-profit provider of behavioral health services for children and youth in the state. We serve approximately 10,000 children and their families annually with a continuum of mental health programs offered through clinics in Wilmington, Newark, Dover, Lewes and Seaford. Accredited by the Joint Commission on Accreditation of Healthcare Organizations (JCAHO), we are also a member of Delaware’s Division of Child Mental Health Services system. DGS mission is to “provide quality therapeutic services to children, youth, and their families to increase their social, emotional, and behavioral wellness” and its vision for Delaware is “resilient families nurturing children’s well-being.” DGS accomplishes its mission using a strength and family-based approach that seeks to understand and address the effects of trauma by building resiliency and intervening at the individual, the family and the community level. DGS delivers services in the setting that best meets each client’s needs including in the office, home, school or other community setting. DGS is the largest provider of outpatient behavioral health services to children and their families in the State of Delaware. Fully accredited by the Joint Commission on Accreditation of Healthcare Organizations (JCAHO) since 1976, DGS serves over 10,000 Delaware children through over 100,000 visits each year. The families we serve come from diverse backgrounds (38% African-American, 57% Caucasian, and 5% Hispanic), over 80% receive Medicaid and approximately 90% have household incomes under $30,000.

NAICS: 62133
NAICS Definition: Offices of Mental Health Practitioners (except Physicians)
Employees: 103
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Courage to Caregivers, Inc.

46 Shopping Plaza - PMB #113, Chagrin Falls, OH, 44023, US
Last Update: 2025-12-05

Courage to Caregivers is a nonprofit located in Northeast Ohio with the mission to provide hope, support, and courage to caregivers and loved ones of those living with mental illness. We focus exclusively on the caregiver and see ourselves in the caregiver burnout prevention business. We offer three programs -One to One Peer Support, Support Groups and Breathing Meditation classes. Our programs are currently at no cost to the participant. All programs are now virtual and we support caregivers nationwide. We provide tailored workshops and breathing meditation presentations for social service organizations, behavioral health organizations, and corporations. Interested organizations can contact Sara Borse at [email protected]. Consider following us on social media: Facebook: CourageToCaregivers Instagram: @couragetocaregivers Twitter: @courage2carecle Subscribe to our YouTube Channel to view weekly breathing meditation videos

NAICS: 621
NAICS Definition:
Employees: 16
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/delaware-guidance-services.jpeg
Delaware Guidance Services for Children and Youth, Inc.
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/couragetocaregivers.jpeg
Courage to Caregivers, Inc.
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
Delaware Guidance Services for Children and Youth, Inc.
100%
Compliance Rate
0/4 Standards Verified
Courage to Caregivers, Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mental Health Care Industry Average (This Year)

No incidents recorded for Delaware Guidance Services for Children and Youth, Inc. in 2026.

Incidents vs Mental Health Care Industry Average (This Year)

No incidents recorded for Courage to Caregivers, Inc. in 2026.

Incident History — Delaware Guidance Services for Children and Youth, Inc. (X = Date, Y = Severity)

Delaware Guidance Services for Children and Youth, Inc. cyber incidents detection timeline including parent company and subsidiaries

Incident History — Courage to Caregivers, Inc. (X = Date, Y = Severity)

Courage to Caregivers, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/delaware-guidance-services.jpeg
Delaware Guidance Services for Children and Youth, Inc.
Incidents

No Incident

https://images.rankiteo.com/companyimages/couragetocaregivers.jpeg
Courage to Caregivers, Inc.
Incidents

No Incident

FAQ

Delaware Guidance Services for Children and Youth, Inc. company demonstrates a stronger AI Cybersecurity Score compared to Courage to Caregivers, Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Courage to Caregivers, Inc. company has disclosed a higher number of cyber incidents compared to Delaware Guidance Services for Children and Youth, Inc. company.

In the current year, Courage to Caregivers, Inc. company and Delaware Guidance Services for Children and Youth, Inc. company have not reported any cyber incidents.

Neither Courage to Caregivers, Inc. company nor Delaware Guidance Services for Children and Youth, Inc. company has reported experiencing a ransomware attack publicly.

Neither Courage to Caregivers, Inc. company nor Delaware Guidance Services for Children and Youth, Inc. company has reported experiencing a data breach publicly.

Neither Courage to Caregivers, Inc. company nor Delaware Guidance Services for Children and Youth, Inc. company has reported experiencing targeted cyberattacks publicly.

Neither Delaware Guidance Services for Children and Youth, Inc. company nor Courage to Caregivers, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Delaware Guidance Services for Children and Youth, Inc. nor Courage to Caregivers, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Delaware Guidance Services for Children and Youth, Inc. company nor Courage to Caregivers, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

Delaware Guidance Services for Children and Youth, Inc. company employs more people globally than Courage to Caregivers, Inc. company, reflecting its scale as a Mental Health Care.

Neither Delaware Guidance Services for Children and Youth, Inc. nor Courage to Caregivers, Inc. holds SOC 2 Type 1 certification.

Neither Delaware Guidance Services for Children and Youth, Inc. nor Courage to Caregivers, Inc. holds SOC 2 Type 2 certification.

Neither Delaware Guidance Services for Children and Youth, Inc. nor Courage to Caregivers, Inc. holds ISO 27001 certification.

Neither Delaware Guidance Services for Children and Youth, Inc. nor Courage to Caregivers, Inc. holds PCI DSS certification.

Neither Delaware Guidance Services for Children and Youth, Inc. nor Courage to Caregivers, Inc. holds HIPAA certification.

Neither Delaware Guidance Services for Children and Youth, Inc. nor Courage to Caregivers, Inc. holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Backstage is an open framework for building developer portals, and @backstage/backend-defaults provides the default implementations and setup for a standard Backstage backend app. Prior to versions 0.12.2, 0.13.2, 0.14.1, and 0.15.0, the `FetchUrlReader` component, used by the catalog and other plugins to fetch content from URLs, followed HTTP redirects automatically. This allowed an attacker who controls a host listed in `backend.reading.allow` to redirect requests to internal or sensitive URLs that are not on the allowlist, bypassing the URL allowlist security control. This is a Server-Side Request Forgery (SSRF) vulnerability that could allow access to internal resources, but it does not allow attackers to include additional request headers. This vulnerability is fixed in `@backstage/backend-defaults` version 0.12.2, 0.13.2, 0.14.1, and 0.15.0. Users should upgrade to this version or later. Some workarounds are available. Restrict `backend.reading.allow` to only trusted hosts that you control and that do not issue redirects, ensure allowed hosts do not have open redirect vulnerabilities, and/or use network-level controls to block access from Backstage to sensitive internal endpoints.

Risk Information
cvss3
Base: 3.5
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N
Description

Backstage is an open framework for building developer portals, and @backstage/cli-common provides config loading functionality used by the backend and command line interface of Backstage. Prior to version 0.1.17, the `resolveSafeChildPath` utility function in `@backstage/backend-plugin-api`, which is used to prevent path traversal attacks, failed to properly validate symlink chains and dangling symlinks. An attacker could bypass the path validation via symlink chains (creating `link1 → link2 → /outside` where intermediate symlinks eventually resolve outside the allowed directory) and dangling symlinks (creating symlinks pointing to non-existent paths outside the base directory, which would later be created during file operations). This function is used by Scaffolder actions and other backend components to ensure file operations stay within designated directories. This vulnerability is fixed in `@backstage/backend-plugin-api` version 0.1.17. Users should upgrade to this version or later. Some workarounds are available. Run Backstage in a containerized environment with limited filesystem access and/or restrict template creation to trusted users.

Risk Information
cvss3
Base: 6.3
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
Description

Backstage is an open framework for building developer portals. Multiple Scaffolder actions and archive extraction utilities were vulnerable to symlink-based path traversal attacks. An attacker with access to create and execute Scaffolder templates could exploit symlinks to read arbitrary files via the `debug:log` action by creating a symlink pointing to sensitive files (e.g., `/etc/passwd`, configuration files, secrets); delete arbitrary files via the `fs:delete` action by creating symlinks pointing outside the workspace, and write files outside the workspace via archive extraction (tar/zip) containing malicious symlinks. This affects any Backstage deployment where users can create or execute Scaffolder templates. This vulnerability is fixed in `@backstage/backend-defaults` versions 0.12.2, 0.13.2, 0.14.1, and 0.15.0; `@backstage/plugin-scaffolder-backend` versions 2.2.2, 3.0.2, and 3.1.1; and `@backstage/plugin-scaffolder-node` versions 0.11.2 and 0.12.3. Users should upgrade to these versions or later. Some workarounds are available. Follow the recommendation in the Backstage Threat Model to limit access to creating and updating templates, restrict who can create and execute Scaffolder templates using the permissions framework, audit existing templates for symlink usage, and/or run Backstage in a containerized environment with limited filesystem access.

Risk Information
cvss3
Base: 7.1
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L
Description

FastAPI Api Key provides a backend-agnostic library that provides an API key system. Version 1.1.0 has a timing side-channel vulnerability in verify_key(). The method applied a random delay only on verification failures, allowing an attacker to statistically distinguish valid from invalid API keys by measuring response latencies. With enough repeated requests, an adversary could infer whether a key_id corresponds to a valid key, potentially accelerating brute-force or enumeration attacks. All users relying on verify_key() for API key authentication prior to the fix are affected. Users should upgrade to version 1.1.0 to receive a patch. The patch applies a uniform random delay (min_delay to max_delay) to all responses regardless of outcome, eliminating the timing correlation. Some workarounds are available. Add an application-level fixed delay or random jitter to all authentication responses (success and failure) before the fix is applied and/or use rate limiting to reduce the feasibility of statistical timing attacks.

Risk Information
cvss3
Base: 3.7
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Description

The Flux Operator is a Kubernetes CRD controller that manages the lifecycle of CNCF Flux CD and the ControlPlane enterprise distribution. Starting in version 0.36.0 and prior to version 0.40.0, a privilege escalation vulnerability exists in the Flux Operator Web UI authentication code that allows an attacker to bypass Kubernetes RBAC impersonation and execute API requests with the operator's service account privileges. In order to be vulnerable, cluster admins must configure the Flux Operator with an OIDC provider that issues tokens lacking the expected claims (e.g., `email`, `groups`), or configure custom CEL expressions that can evaluate to empty values. After OIDC token claims are processed through CEL expressions, there is no validation that the resulting `username` and `groups` values are non-empty. When both values are empty, the Kubernetes client-go library does not add impersonation headers to API requests, causing them to be executed with the flux-operator service account's credentials instead of the authenticated user's limited permissions. This can result in privilege escalation, data exposure, and/or information disclosure. Version 0.40.0 patches the issue.

Risk Information
cvss3
Base: 5.3
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N