Comparison Overview

HEMOSC

VS

Ledge Light Health District

HEMOSC

Avenida Professor Othon Gama d'Eça 756, Florianópolis, 88015-240, BR
Last Update: 2025-11-28
Between 750 and 799

O HEMOSC é o Hemocentro Coordenador de Santa Catarina, responsável por todas as ações de captação de doação voluntária de sangue e aféreses e uso de sangue para fins terapêuticos. Além disso, tem a atribuição de garantir a qualidade e o controle da coleta, qualificação do doador, produção dos hemocomponentes, estocagem e distribuição desses, além de promover o desenvolvimento de conhecimento científico e tecnológico na área. Conta com uma cobertura em 98% do estado, com sete hemocentros, duas unidades de coleta e oito agências transfusionais localizadas em Blumenau, Chapecó, Criciúma, Florianópolis, Jaraguá do Sul, Joaçaba, Joinville, Lages e Tubarão. Contamos com sete hemocentros, localizados nas cidades de Blumenau, Chapecó, Criciúma, Florianópolis, Joaçaba, Joinville e Lages, e com duas Unidades de Coleta nas cidades de Jaraguá do Sul e Tubarão.

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

Ledge Light Health District

216 Broad Street, New London, CT, 06320, US
Last Update: 2025-11-28
Between 750 and 799

Ledge Light Health District – LLHD – serves as the local health department for East Lyme, Groton, Ledyard, Lyme, New London, North Stonington, Old Lyme, Stonington and Waterford, Connecticut. From restaurant inspections to smoking cessation classes, we work hard to promote healthy communities and prevent disease, illness and injury. As a health district, formed under Connecticut General Statutes Section 19a-241, LLHD is a special unit of government, allowing member municipalities to provide comprehensive public health services to residents in a more efficient manner by consolidating the services within one organization. The Director of Health and staff of LLHD work to promote health and wellness among the 151,000 residents we serve. By enforcing the Connecticut Public Health Code, conducting health education programs, monitoring disease outbreaks and nurturing our environment, LLHD is focused on promoting healthy communities.

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 49
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/hemosc.jpeg
HEMOSC
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/ledge-light-health-district.jpeg
Ledge Light Health 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
Compliance Summary
HEMOSC
100%
Compliance Rate
0/4 Standards Verified
Ledge Light Health District
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for HEMOSC in 2025.

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Ledge Light Health District in 2025.

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

HEMOSC cyber incidents detection timeline including parent company and subsidiaries

Incident History — Ledge Light Health District (X = Date, Y = Severity)

Ledge Light Health District cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/hemosc.jpeg
HEMOSC
Incidents

No Incident

https://images.rankiteo.com/companyimages/ledge-light-health-district.jpeg
Ledge Light Health District
Incidents

No Incident

FAQ

Both HEMOSC company and Ledge Light Health District company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Ledge Light Health District company has disclosed a higher number of cyber incidents compared to HEMOSC company.

In the current year, Ledge Light Health District company and HEMOSC company have not reported any cyber incidents.

Neither Ledge Light Health District company nor HEMOSC company has reported experiencing a ransomware attack publicly.

Neither Ledge Light Health District company nor HEMOSC company has reported experiencing a data breach publicly.

Neither Ledge Light Health District company nor HEMOSC company has reported experiencing targeted cyberattacks publicly.

Neither HEMOSC company nor Ledge Light Health District company has reported experiencing or disclosing vulnerabilities publicly.

Neither HEMOSC nor Ledge Light Health District holds any compliance certifications.

Neither company holds any compliance certifications.

Neither HEMOSC company nor Ledge Light Health District company has publicly disclosed detailed information about the number of their subsidiaries.

HEMOSC company employs more people globally than Ledge Light Health District company, reflecting its scale as a Public Health.

Neither HEMOSC nor Ledge Light Health District holds SOC 2 Type 1 certification.

Neither HEMOSC nor Ledge Light Health District holds SOC 2 Type 2 certification.

Neither HEMOSC nor Ledge Light Health District holds ISO 27001 certification.

Neither HEMOSC nor Ledge Light Health District holds PCI DSS certification.

Neither HEMOSC nor Ledge Light Health District holds HIPAA certification.

Neither HEMOSC nor Ledge Light Health District 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