Comparison Overview

TELUS Health

VS

Health Sciences Association of BC

TELUS Health

510 W Georgia St, None, Vancouver, British Columbia, CA, V6B 0M3
Last Update: 2025-11-27
Between 750 and 799

We’re committed to delivering remarkable health experiences for the benefit of all customers and individuals we serve around the world. Leveraging our world-leading technology and nearly 10 000 passionate team members, we’re equipped to better support our customers and solve some of the most pressing issues facing citizens, patients, healthcare professionals, employers and employees today. See how we’re committed to building the healthiest communities and workplaces on the planet.

NAICS: 923
NAICS Definition: Administration of Human Resource Programs
Employees: 7,002
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1

Health Sciences Association of BC

None
Last Update: 2025-11-21
Between 750 and 799

HSA represents more than 20,000 health science and community service professionals at over 250 hospitals and agencies in acute care, long-term care and community health, including workers at child development centres and transition houses. Working on their behalf is a highly-respected staff team including labour relations practitioners, disability management and classifications experts, legal counsel, communicators and campaigners, administrative professionals, and operations staff.

NAICS: 923
NAICS Definition: Administration of Human Resource Programs
Employees: 99
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/telus-health.jpeg
TELUS 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
https://images.rankiteo.com/companyimages/health-sciences-association-of-bc.jpeg
Health Sciences Association of BC
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
TELUS Health
100%
Compliance Rate
0/4 Standards Verified
Health Sciences Association of BC
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Health and Human Services Industry Average (This Year)

No incidents recorded for TELUS Health in 2025.

Incidents vs Health and Human Services Industry Average (This Year)

No incidents recorded for Health Sciences Association of BC in 2025.

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

TELUS Health cyber incidents detection timeline including parent company and subsidiaries

Incident History — Health Sciences Association of BC (X = Date, Y = Severity)

Health Sciences Association of BC cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/telus-health.jpeg
TELUS Health
Incidents

Date Detected: 5/2023
Type:Vulnerability
Attack Vector: Exploitation of Vulnerability
Blog: Blog
https://images.rankiteo.com/companyimages/health-sciences-association-of-bc.jpeg
Health Sciences Association of BC
Incidents

No Incident

FAQ

TELUS Health company demonstrates a stronger AI Cybersecurity Score compared to Health Sciences Association of BC company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

TELUS Health company has historically faced a number of disclosed cyber incidents, whereas Health Sciences Association of BC company has not reported any.

In the current year, Health Sciences Association of BC company and TELUS Health company have not reported any cyber incidents.

Neither Health Sciences Association of BC company nor TELUS Health company has reported experiencing a ransomware attack publicly.

Neither Health Sciences Association of BC company nor TELUS Health company has reported experiencing a data breach publicly.

Neither Health Sciences Association of BC company nor TELUS Health company has reported experiencing targeted cyberattacks publicly.

TELUS Health company has disclosed at least one vulnerability, while Health Sciences Association of BC company has not reported such incidents publicly.

Neither TELUS Health nor Health Sciences Association of BC holds any compliance certifications.

Neither company holds any compliance certifications.

Neither TELUS Health company nor Health Sciences Association of BC company has publicly disclosed detailed information about the number of their subsidiaries.

TELUS Health company employs more people globally than Health Sciences Association of BC company, reflecting its scale as a Health and Human Services.

Neither TELUS Health nor Health Sciences Association of BC holds SOC 2 Type 1 certification.

Neither TELUS Health nor Health Sciences Association of BC holds SOC 2 Type 2 certification.

Neither TELUS Health nor Health Sciences Association of BC holds ISO 27001 certification.

Neither TELUS Health nor Health Sciences Association of BC holds PCI DSS certification.

Neither TELUS Health nor Health Sciences Association of BC holds HIPAA certification.

Neither TELUS Health nor Health Sciences Association of BC 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