Comparison Overview

World Health Organization Western Pacific Region

VS

Hoop

World Health Organization Western Pacific Region

United Nations Avenue, None, Manila, National Capital Region, PH, None
Last Update: 2025-11-25

This is the official LinkedIn page of the World Health Organization in the Western Pacific Region. With our partners, we work to promote health, keep the world safe and serve the vulnerable — all in one of the most diverse and dynamic regions on the planet. From strengthening health systems to responding to emergencies and advancing universal health coverage, we are committed to building a healthier future for nearly 2 billion people across 38 countries and areas. #HealthForAll

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

Hoop

London, GB
Last Update: 2025-11-28
Between 750 and 799

Hoop - the incredible app that helps parents and kids to find activities. We will only list healthy activities, classes or events on our app. Prior to Covid19, Hoop was used by over 1,000,000 families. I'm re-launching it in 2022 so parents can get this amazing resource back. It's the best. It really is! ... Tim (Dad, CEO)

NAICS: 92312
NAICS Definition: Administration of Public Health Programs
Employees: 3
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/world-health-organization-western-pacific-region.jpeg
World Health Organization Western Pacific Region
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/hoop-health.jpeg
Hoop
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
World Health Organization Western Pacific Region
100%
Compliance Rate
0/4 Standards Verified
Hoop
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for World Health Organization Western Pacific Region in 2025.

Incidents vs Public Health Industry Average (This Year)

No incidents recorded for Hoop in 2025.

Incident History — World Health Organization Western Pacific Region (X = Date, Y = Severity)

World Health Organization Western Pacific Region cyber incidents detection timeline including parent company and subsidiaries

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

Hoop cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/world-health-organization-western-pacific-region.jpeg
World Health Organization Western Pacific Region
Incidents

Date Detected: 6/2019
Type:Ransomware
Attack Vector: Unknown
Motivation: Financial
Blog: Blog
https://images.rankiteo.com/companyimages/hoop-health.jpeg
Hoop
Incidents

No Incident

FAQ

Hoop company demonstrates a stronger AI Cybersecurity Score compared to World Health Organization Western Pacific Region company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

World Health Organization Western Pacific Region company has historically faced a number of disclosed cyber incidents, whereas Hoop company has not reported any.

In the current year, Hoop company and World Health Organization Western Pacific Region company have not reported any cyber incidents.

World Health Organization Western Pacific Region company has confirmed experiencing a ransomware attack, while Hoop company has not reported such incidents publicly.

Neither Hoop company nor World Health Organization Western Pacific Region company has reported experiencing a data breach publicly.

Neither Hoop company nor World Health Organization Western Pacific Region company has reported experiencing targeted cyberattacks publicly.

Neither World Health Organization Western Pacific Region company nor Hoop company has reported experiencing or disclosing vulnerabilities publicly.

Neither World Health Organization Western Pacific Region nor Hoop holds any compliance certifications.

Neither company holds any compliance certifications.

Neither World Health Organization Western Pacific Region company nor Hoop company has publicly disclosed detailed information about the number of their subsidiaries.

World Health Organization Western Pacific Region company employs more people globally than Hoop company, reflecting its scale as a Public Health.

Neither World Health Organization Western Pacific Region nor Hoop holds SOC 2 Type 1 certification.

Neither World Health Organization Western Pacific Region nor Hoop holds SOC 2 Type 2 certification.

Neither World Health Organization Western Pacific Region nor Hoop holds ISO 27001 certification.

Neither World Health Organization Western Pacific Region nor Hoop holds PCI DSS certification.

Neither World Health Organization Western Pacific Region nor Hoop holds HIPAA certification.

Neither World Health Organization Western Pacific Region nor Hoop 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