Comparison Overview

Health PEI

VS

Hospital Authority

Health PEI

16 Garfield St, Charlottetown, Prince Edward Island, C1A, CA
Last Update: 2025-12-17
Between 700 and 749

Health PEI is a crown corporation responsible for the operation and delivery of publicly funded health services in Prince Edward Island, Canada. The organization operates hospitals, health centres, public long-term care nursing facilities and community-based programs and services.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 1,258
Subsidiaries: 6
12-month incidents
0
Known data breaches
2
Attack type number
3

Hospital Authority

Hospital Authority Building, Hong Kong, undefined, 852, HK
Last Update: 2025-12-17

The Hospital Authority (HA) is a statutory body established under the Hospital Authority Ordinance in 1990. We have been responsible for managing Hong Kong's public hospitals services since December 1991. We are accountable to the Hong Kong Special Administrative Region Government through the Secretary for Health, who formulates overall health policies for Hong Kong and overseas the work of HA.

NAICS: 62
NAICS Definition: Health Care and Social Assistance
Employees: 11,255
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/health-pei.jpeg
Health PEI
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/hospital-authority.jpeg
Hospital Authority
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
Health PEI
100%
Compliance Rate
0/4 Standards Verified
Hospital Authority
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for Health PEI in 2025.

Incidents vs Hospitals and Health Care Industry Average (This Year)

No incidents recorded for Hospital Authority in 2025.

Incident History — Health PEI (X = Date, Y = Severity)

Health PEI cyber incidents detection timeline including parent company and subsidiaries

Incident History — Hospital Authority (X = Date, Y = Severity)

Hospital Authority cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/health-pei.jpeg
Health PEI
Incidents

Date Detected: 06/2022
Type:Breach
Attack Vector: Laptop Theft
Motivation: Theft
Blog: Blog

Date Detected: 4/2022
Type:Breach
Attack Vector: Theft of Laptop
Blog: Blog

Date Detected: 03/2020
Type:Malware
Blog: Blog
https://images.rankiteo.com/companyimages/hospital-authority.jpeg
Hospital Authority
Incidents

No Incident

FAQ

Hospital Authority company demonstrates a stronger AI Cybersecurity Score compared to Health PEI company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Health PEI company has historically faced a number of disclosed cyber incidents, whereas Hospital Authority company has not reported any.

In the current year, Hospital Authority company and Health PEI company have not reported any cyber incidents.

Health PEI company has confirmed experiencing a ransomware attack, while Hospital Authority company has not reported such incidents publicly.

Health PEI company has disclosed at least one data breach, while the other Hospital Authority company has not reported such incidents publicly.

Neither Hospital Authority company nor Health PEI company has reported experiencing targeted cyberattacks publicly.

Neither Health PEI company nor Hospital Authority company has reported experiencing or disclosing vulnerabilities publicly.

Neither Health PEI nor Hospital Authority holds any compliance certifications.

Neither company holds any compliance certifications.

Health PEI company has more subsidiaries worldwide compared to Hospital Authority company.

Hospital Authority company employs more people globally than Health PEI company, reflecting its scale as a Hospitals and Health Care.

Neither Health PEI nor Hospital Authority holds SOC 2 Type 1 certification.

Neither Health PEI nor Hospital Authority holds SOC 2 Type 2 certification.

Neither Health PEI nor Hospital Authority holds ISO 27001 certification.

Neither Health PEI nor Hospital Authority holds PCI DSS certification.

Neither Health PEI nor Hospital Authority holds HIPAA certification.

Neither Health PEI nor Hospital Authority holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Improper Authorization (CWE-285) in Kibana can lead to privilege escalation (CAPEC-233) by allowing an authenticated user to bypass intended permission restrictions via a crafted HTTP request. This allows an attacker who lacks the live queries - read permission to successfully retrieve the list of live queries.

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

Weblate is a web based localization tool. In versions prior to 5.15.1, it was possible to overwrite Git configuration remotely and override some of its behavior. Version 5.15.1 fixes the issue.

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

Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can allow an authenticated user with snapshot restore privileges to cause Excessive Allocation (CAPEC-130) of memory and a denial of service (DoS) via crafted HTTP request.

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

Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can allow a low-privileged authenticated user to cause Excessive Allocation (CAPEC-130) of computing resources and a denial of service (DoS) of the Kibana process via a crafted HTTP request.

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

Improper neutralization of input during web page generation ('Cross-site Scripting') (CWE-79) allows an unauthenticated user to embed a malicious script in content that will be served to web browsers causing cross-site scripting (XSS) (CAPEC-63) via a vulnerability a function handler in the Vega AST evaluator.

Risk Information
cvss3
Base: 6.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N