Comparison Overview

MediBank

VS

Cuyahoga County Board of Health

MediBank

Bizness Square, Hitech City Road, Whitefields, Hyderabad, Telangana, IN, 500081
Last Update: 2025-11-25
Between 750 and 799

MediBank is India's premier platform centralizing Electronic Health Records (EHR) for both patients and doctors. By digitizing health records and utilizing AI-driven health charts, we aim to streamline healthcare coordination and enhance early issue detection. Our ultimate goal is to revolutionize healthcare in India by bridging the gap between patients and doctors, optimizing diagnostic accuracy, and promoting proactive care.

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

Cuyahoga County Board of Health

Cleveland, US
Last Update: 2025-11-28
Between 750 and 799

The Cuyahoga County Board of Health is your trusted source for public health information. Our mission is to work in partnership with the community to protect and improve the health and well-being of everyone in Cuyahoga County. Our vision is to create the conditions in which all people who live, learn, work and play in Cuyahoga County have the opportunity to be healthy. Our core values are: Health equity Integrity Partnership Innovation

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 164
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/medibankind.jpeg
MediBank
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/cuyahoga-county-board-of-health.jpeg
Cuyahoga County Board of 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
Compliance Summary
MediBank
100%
Compliance Rate
0/4 Standards Verified
Cuyahoga County Board of Health
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for MediBank in 2025.

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Cuyahoga County Board of Health in 2025.

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

MediBank cyber incidents detection timeline including parent company and subsidiaries

Incident History — Cuyahoga County Board of Health (X = Date, Y = Severity)

Cuyahoga County Board of Health cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/medibankind.jpeg
MediBank
Incidents

No Incident

https://images.rankiteo.com/companyimages/cuyahoga-county-board-of-health.jpeg
Cuyahoga County Board of Health
Incidents

No Incident

FAQ

Cuyahoga County Board of Health company demonstrates a stronger AI Cybersecurity Score compared to MediBank company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Cuyahoga County Board of Health company has disclosed a higher number of cyber incidents compared to MediBank company.

In the current year, Cuyahoga County Board of Health company and MediBank company have not reported any cyber incidents.

Neither Cuyahoga County Board of Health company nor MediBank company has reported experiencing a ransomware attack publicly.

Neither Cuyahoga County Board of Health company nor MediBank company has reported experiencing a data breach publicly.

Neither Cuyahoga County Board of Health company nor MediBank company has reported experiencing targeted cyberattacks publicly.

Neither MediBank company nor Cuyahoga County Board of Health company has reported experiencing or disclosing vulnerabilities publicly.

Neither MediBank nor Cuyahoga County Board of Health holds any compliance certifications.

Neither company holds any compliance certifications.

Neither MediBank company nor Cuyahoga County Board of Health company has publicly disclosed detailed information about the number of their subsidiaries.

Cuyahoga County Board of Health company employs more people globally than MediBank company, reflecting its scale as a Public Health.

Neither MediBank nor Cuyahoga County Board of Health holds SOC 2 Type 1 certification.

Neither MediBank nor Cuyahoga County Board of Health holds SOC 2 Type 2 certification.

Neither MediBank nor Cuyahoga County Board of Health holds ISO 27001 certification.

Neither MediBank nor Cuyahoga County Board of Health holds PCI DSS certification.

Neither MediBank nor Cuyahoga County Board of Health holds HIPAA certification.

Neither MediBank nor Cuyahoga County Board of Health 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