Vancouver Coastal Health Company Cyber Security Posture

vch.ca

Join a team connected by collaboration, support and most importantly, the goal of providing quality patient care. We value career growth with employer-supported training, encourage a culture where everyoneโ€™s voice is heard and strive to create a supportive team environment. To learn more, visit vch.ca/careers Facebook - https://www.facebook.com/VCHhealthcare/ Twitter - https://twitter.com/VCHhealthcare YouTube - https://www.youtube.com/@VCHhealthcare Instagram - https://www.instagram.com/vchhealthcare/

VCH Company Details

Linkedin ID:

vancouver-coastal-health

Employees number:

10413 employees

Number of followers:

79673.0

NAICS:

62

Industry Type:

Hospitals and Health Care

Homepage:

vch.ca

IP Addresses:

46

Company ID:

VAN_2219870

Scan Status:

In-progress

AI scoreVCH Risk Score (AI oriented)

Between 500 and 600

This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.

Ailogo

Vancouver Coastal Health Company Scoring based on AI Models

Model NameDateDescriptionCurrent Score DifferenceScore
AVERAGE-Industry03-12-2025

This score represents the average cybersecurity rating of companies already scanned within the same industry. It provides a benchmark to compare an individual company's security posture against its industry peers.

N/A

Between 500 and 600

Vancouver Coastal Health Company Cyber Security News & History

Past Incidents
1
Attack Types
1
EntityTypeSeverityImpactSeenUrl IDDetailsView
Vancouver Coastal HealthRansomware85305/2020VAN194413123Link
Rankiteo Explanation :
Attack with significant impact with internal employee data leaks

Description: Vancouver Coastal Health experienced an attack. Malicious ransomware was discovered in data related to its Employee and Family Assistance Program on May 21. There is no evidence any data has been removed or misused from Employee and Family Assistance Program computers.

Vancouver Coastal Health Company Subsidiaries

SubsidiaryImage

Join a team connected by collaboration, support and most importantly, the goal of providing quality patient care. We value career growth with employer-supported training, encourage a culture where everyoneโ€™s voice is heard and strive to create a supportive team environment. To learn more, visit vch.ca/careers Facebook - https://www.facebook.com/VCHhealthcare/ Twitter - https://twitter.com/VCHhealthcare YouTube - https://www.youtube.com/@VCHhealthcare Instagram - https://www.instagram.com/vchhealthcare/

Loading...

Access Data Using Our API

SubsidiaryImage

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?linkedin_id=vancouver-coastal-health' -H 'apikey: YOUR_API_KEY_HERE'
newsone

VCH Cyber Security News

2024-07-19T07:00:00.000Z
B.C. hospitals pivot to paper amid global technology outage

Hospitals in BC had to switch to using pen and paper to manage their records and scheduling as a global IT outage caused widespread disruptions around theย ...

2025-02-18T08:00:00.000Z
New Lions Gate Hospital tower set to open

The new, modern acute care tower at Lions Gate Hospital in North Vancouver is set to open on March 9, 2025.

2024-07-22T07:00:00.000Z
Microsoft Crash Throws BC Health Authorities Back to Analogue Age

On Friday computers around the world running Windows 10 crashed, causing hiccups for health-care workers and patients.

2024-11-16T08:00:00.000Z
Student nurse attacked at VGH

None

2024-07-20T07:00:00.000Z
Global IT outage hits Canada: Airports, TD Bank, U.S. border, hospital disruptions and more after faulty CrowdStrike update

A global IT outage that disrupted multiple industries, including banks, health care, border crossings and airlines.

2023-09-13T17:26:00.000Z
Join a team connected by care

Are you up for a rewarding and challenging career in the health care field? Explore what we have to offer by viewing our featured positions today.

2024-07-19T07:00:00.000Z
CrowdStrike Cyber Outage: Canada Impacted as Well

A global cyber outage has disrupted banking, airlines, and media due to a faulty update from cybersecurity provider CrowdStrike,ย ...

2024-06-10T07:00:00.000Z
Health Technology Excellence Award Winners Circle

Honoring excellence in the field of health technology management The Health Technology Excellence Award is presented each year to an ECRIย ...

2023-02-15T08:00:00.000Z
Management, lack of money blamed for poor cybersecurity at Canadian hospitals

The biggest impediment to improving the cybersecurity of Canadian hospitals is "lack of focus" of management and lack of money, says theย ...

similarCompanies

VCH Similar Companies

UCLA Health

For more than half a century, UCLA Health has provided the best in healthcare and the latest in medical technology to the people of Los Angeles and throughout the world. Comprised of Ronald Reagan UCLA Medical Center, UCLA Medical Center Santa Monica, Resnick Neuropsychiatric Hospital at UCLA, UCLA

LUX MED

LUX MED - leader and trustworthy expert We care for the health of the patients professionally and with engagement, we have been developing our business for over 20 years. Today we are the leader and expert on the private healthcare market. We take under our care both individual patients and corpo

Duke University Health System

As a world-class academic and health care system, Duke Health strives to transform medicine and health locally and globally through innovative scientific research, rapid translation of breakthrough discoveries, educating future clinical and scientific leaders, advocating and practicing evidence-base

Hospital Albert Einstein

O nascimento da Sociedade Beneficente Israelita Brasileira Albert Einstein, na dรฉcada de 50, resultou do compromisso da comunidade judaica em oferecer ร  populaรงรฃo brasileira uma referรชncia em qualidade da prรกtica mรฉdica. Mas a Sociedade queria ir alรฉm da simples construรงรฃo de um hospital. E assi

Ambea

Ambea โˆšยงr Skandinaviens kunskapsledande omsorgsfโˆšโˆ‚retag med cirka 31 000 medarbetare. Inom vโˆšโ€ขr fโˆšโˆ‚retagsgrupp erbjuder vi boende, stโˆšโˆ‚d, utbildning och bemanning inom vโˆšโ€ขrd och omsorg. Ambea har drygt 950 enheter i Sverige, Norge och Danmark. Vi ska vara kvalitetsledande i allt vi gโˆšโˆ‚r och vโˆšโ€ขr vis

Corewell Health

People are at the heart of everything we do, and the inspiration for our legacy of outstanding outcomes, innovation, strong community partnerships, philanthropy and transparency. Corewell Health is a not-for-profit health system that provides health care and coverage with an exceptional team of 65,0

faq

Frequently Asked Questions (FAQ) on Cybersecurity Incidents

VCH CyberSecurity History Information

Total Incidents: According to Rankiteo, VCH has faced 1 incidents in the past.

Incident Types: The types of cybersecurity incidents that have occurred include ['Ransomware'].

Total Financial Loss: The total financial loss from these incidents is estimated to be {total_financial_loss}.

Cybersecurity Posture: The company's overall cybersecurity posture is described as Join a team connected by collaboration, support and most importantly, the goal of providing quality patient care. We value career growth with employer-supported training, encourage a culture where everyoneโ€™s voice is heard and strive to create a supportive team environment. To learn more, visit vch.ca/careers Facebook - https://www.facebook.com/VCHhealthcare/ Twitter - https://twitter.com/VCHhealthcare YouTube - https://www.youtube.com/@VCHhealthcare Instagram - https://www.instagram.com/vchhealthcare/.

Detection and Response: The company detects and responds to cybersecurity incidents through {description_of_detection_and_response_process}.

Incident Details

Incident 1: Ransomware Attack

Title: {Incident_Title}

Description: {Brief_description_of_the_incident}

Date Detected: {Detection_Date}

Date Publicly Disclosed: {Disclosure_Date}

Date Resolved: {Resolution_Date}

Type: {Type_of_Attack}

Attack Vector: {Attack_Vector}

Vulnerability Exploited: {Vulnerability}

Threat Actor: {Threat_Actor}

Motivation: {Motivation}

Incident 2: Data Breach

Title: {Incident_Title}

Description: {Brief_description_of_the_incident}

Date Detected: {Detection_Date}

Date Publicly Disclosed: {Disclosure_Date}

Date Resolved: {Resolution_Date}

Type: {Type_of_Attack}

Attack Vector: {Attack_Vector}

Vulnerability Exploited: {Vulnerability}

Threat Actor: {Threat_Actor}

Motivation: {Motivation}

Common Attack Types: As of now, the company has not encountered any reported incidents involving common cyberattacks.

Identification of Attack Vectors: The company identifies the attack vectors used in incidents through {description_of_identification_process}.

Impact of the Incidents

Incident 1: Ransomware Attack

Financial Loss: {Financial_Loss}

Data Compromised: {Data_Compromised}

Systems Affected: {Systems_Affected}

Downtime: {Downtime}

Operational Impact: {Operational_Impact}

Conversion Rate Impact: {Conversion_Rate_Impact}

Revenue Loss: {Revenue_Loss}

Customer Complaints: {Customer_Complaints}

Brand Reputation Impact: {Brand_Reputation_Impact}

Legal Liabilities: {Legal_Liabilities}

Identity Theft Risk: {Identity_Theft_Risk}

Payment Information Risk: {Payment_Information_Risk}

Incident 2: Data Breach

Financial Loss: {Financial_Loss}

Data Compromised: {Data_Compromised}

Systems Affected: {Systems_Affected}

Downtime: {Downtime}

Operational Impact: {Operational_Impact}

Conversion Rate Impact: {Conversion_Rate_Impact}

Revenue Loss: {Revenue_Loss}

Customer Complaints: {Customer_Complaints}

Brand Reputation Impact: {Brand_Reputation_Impact}

Legal Liabilities: {Legal_Liabilities}

Identity Theft Risk: {Identity_Theft_Risk}

Payment Information Risk: {Payment_Information_Risk}

Average Financial Loss: The average financial loss per incident is {average_financial_loss}.

Commonly Compromised Data Types: The types of data most commonly compromised in incidents are {list_of_commonly_compromised_data_types}.

Incident 1: Ransomware Attack

Entity Name: {Entity_Name}

Entity Type: {Entity_Type}

Industry: {Industry}

Location: {Location}

Size: {Size}

Customers Affected: {Customers_Affected}

Incident 2: Data Breach

Entity Name: {Entity_Name}

Entity Type: {Entity_Type}

Industry: {Industry}

Location: {Location}

Size: {Size}

Customers Affected: {Customers_Affected}

Response to the Incidents

Incident 1: Ransomware Attack

Incident Response Plan Activated: {Yes/No}

Third Party Assistance: {Yes/No}

Law Enforcement Notified: {Yes/No}

Containment Measures: {Containment_Measures}

Remediation Measures: {Remediation_Measures}

Recovery Measures: {Recovery_Measures}

Communication Strategy: {Communication_Strategy}

Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}

On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}

Network Segmentation: {Network_Segmentation}

Enhanced Monitoring: {Enhanced_Monitoring}

Incident 2: Data Breach

Incident Response Plan Activated: {Yes/No}

Third Party Assistance: {Yes/No}

Law Enforcement Notified: {Yes/No}

Containment Measures: {Containment_Measures}

Remediation Measures: {Remediation_Measures}

Recovery Measures: {Recovery_Measures}

Communication Strategy: {Communication_Strategy}

Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}

On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}

Network Segmentation: {Network_Segmentation}

Enhanced Monitoring: {Enhanced_Monitoring}

Incident Response Plan: The company's incident response plan is described as {description_of_incident_response_plan}.

Third-Party Assistance: The company involves third-party assistance in incident response through {description_of_third_party_involvement}.

Data Breach Information

Incident 2: Data Breach

Type of Data Compromised: {Type_of_Data}

Number of Records Exposed: {Number_of_Records}

Sensitivity of Data: {Sensitivity_of_Data}

Data Exfiltration: {Yes/No}

Data Encryption: {Yes/No}

File Types Exposed: {File_Types}

Personally Identifiable Information: {Yes/No}

Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: {description_of_prevention_measures}.

Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through {description_of_handling_process}.

Ransomware Information

Incident 1: Ransomware Attack

Ransom Demanded: {Ransom_Amount}

Ransom Paid: {Ransom_Paid}

Ransomware Strain: {Ransomware_Strain}

Data Encryption: {Yes/No}

Data Exfiltration: {Yes/No}

Ransom Payment Policy: The company's policy on paying ransoms in ransomware incidents is described as {description_of_ransom_payment_policy}.

Data Recovery from Ransomware: The company recovers data encrypted by ransomware through {description_of_data_recovery_process}.

Regulatory Compliance

Ransomware Logo

Incident 1: Ransomware Attack

Regulations Violated: {Regulations_Violated}

Fines Imposed: {Fines_Imposed}

Legal Actions: {Legal_Actions}

Regulatory Notifications: {Regulatory_Notifications}

Data Breach Logo

Incident 2: Data Breach

Regulations Violated: {Regulations_Violated}

Fines Imposed: {Fines_Imposed}

Legal Actions: {Legal_Actions}

Regulatory Notifications: {Regulatory_Notifications}

Regulatory Frameworks: The company complies with the following regulatory frameworks regarding cybersecurity: {list_of_regulatory_frameworks}.

Ensuring Regulatory Compliance: The company ensures compliance with regulatory requirements through {description_of_compliance_measures}.

Lessons Learned and Recommendations

Incident 1: Ransomware Attack

Lessons Learned: {Lessons_Learned}

Incident 2: Data Breach

Lessons Learned: {Lessons_Learned}

Incident 1: Ransomware Attack

Recommendations: {Recommendations}

Incident 2: Data Breach

Recommendations: {Recommendations}

Key Lessons Learned: The key lessons learned from past incidents are {list_of_key_lessons_learned}.

Implemented Recommendations: The company has implemented the following recommendations to improve cybersecurity: {list_of_implemented_recommendations}.

References

Incident 1: Ransomware Attack

Source: {Source}

URL: {URL}

Date Accessed: {Date_Accessed}

Incident 2: Data Breach

Source: {Source}

URL: {URL}

Date Accessed: {Date_Accessed}

Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at {list_of_additional_resources}.

Investigation Status

Incident 1: Ransomware Attack

Investigation Status: {Investigation_Status}

Incident 2: Data Breach

Investigation Status: {Investigation_Status}

Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through {description_of_communication_process}.

Stakeholder and Customer Advisories

Incident 1: Ransomware Attack

Stakeholder Advisories: {Stakeholder_Advisories}

Customer Advisories: {Customer_Advisories}


Incident 2: Data Breach

Stakeholder Advisories: {Stakeholder_Advisories}

Customer Advisories: {Customer_Advisories}

Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: {description_of_advisories_provided}.

Initial Access Broker

Incident 1: Ransomware Attack

Entry Point: {Entry_Point}

Reconnaissance Period: {Reconnaissance_Period}

Backdoors Established: {Backdoors_Established}

High Value Targets: {High_Value_Targets}

Data Sold on Dark Web: {Yes/No}

Incident 2: Data Breach

Entry Point: {Entry_Point}

Reconnaissance Period: {Reconnaissance_Period}

Backdoors Established: {Backdoors_Established}

High Value Targets: {High_Value_Targets}

Data Sold on Dark Web: {Yes/No}

Monitoring and Mitigation of Initial Access Brokers: The company monitors and mitigates the activities of initial access brokers through {description_of_monitoring_and_mitigation_measures}.

Post-Incident Analysis

Incident 1: Ransomware Attack

Root Causes: {Root_Causes}

Corrective Actions: {Corrective_Actions}

Incident 2: Data Breach

Root Causes: {Root_Causes}

Corrective Actions: {Corrective_Actions}

Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as {description_of_post_incident_analysis_process}.

Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: {list_of_corrective_actions_taken}.

Additional Questions

General Information

Ransom Payment History: The company has {paid/not_paid} ransoms in the past.

Last Ransom Demanded: The amount of the last ransom demanded was {last_ransom_amount}.

Last Attacking Group: The attacking group in the last incident was {last_attacking_group}.

Incident Details

Most Recent Incident Detected: The most recent incident detected was on {most_recent_incident_detected_date}.

Most Recent Incident Publicly Disclosed: The most recent incident publicly disclosed was on {most_recent_incident_publicly_disclosed_date}.

Most Recent Incident Resolved: The most recent incident resolved was on {most_recent_incident_resolved_date}.

Impact of the Incidents

Highest Financial Loss: The highest financial loss from an incident was {highest_financial_loss}.

Most Significant Data Compromised: The most significant data compromised in an incident was {most_significant_data_compromised}.

Most Significant System Affected: The most significant system affected in an incident was {most_significant_system_affected}.

Response to the Incidents

Third-Party Assistance in Most Recent Incident: The third-party assistance involved in the most recent incident was {third_party_assistance_in_most_recent_incident}.

Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident were {containment_measures_in_most_recent_incident}.

Data Breach Information

Most Sensitive Data Compromised: The most sensitive data compromised in a breach was {most_sensitive_data_compromised}.

Number of Records Exposed: The number of records exposed in the most significant breach was {number_of_records_exposed}.

Ransomware Information

Highest Ransom Demanded: The highest ransom demanded in a ransomware incident was {highest_ransom_demanded}.

Highest Ransom Paid: The highest ransom paid in a ransomware incident was {highest_ransom_paid}.

Regulatory Compliance

Highest Fine Imposed: The highest fine imposed for a regulatory violation was {highest_fine_imposed}.

Most Significant Legal Action: The most significant legal action taken for a regulatory violation was {most_significant_legal_action}.

Lessons Learned and Recommendations

Most Significant Lesson Learned: The most significant lesson learned from past incidents was {most_significant_lesson_learned}.

Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was {most_significant_recommendation_implemented}.

References

Most Recent Source: The most recent source of information about an incident is {most_recent_source}.

Most Recent URL for Additional Resources: The most recent URL for additional resources on cybersecurity best practices is {most_recent_url}.

Investigation Status

Current Status of Most Recent Investigation: The current status of the most recent investigation is {current_status_of_most_recent_investigation}.

Stakeholder and Customer Advisories

Most Recent Stakeholder Advisory: The most recent stakeholder advisory issued was {most_recent_stakeholder_advisory}.

Most Recent Customer Advisory: The most recent customer advisory issued was {most_recent_customer_advisory}.

Initial Access Broker

Most Recent Entry Point: The most recent entry point used by an initial access broker was {most_recent_entry_point}.

Most Recent Reconnaissance Period: The most recent reconnaissance period for an incident was {most_recent_reconnaissance_period}.

Post-Incident Analysis

Most Significant Root Cause: The most significant root cause identified in post-incident analysis was {most_significant_root_cause}.

Most Significant Corrective Action: The most significant corrective action taken based on post-incident analysis was {most_significant_corrective_action}.

What Do We Measure?

revertimgrevertimgrevertimgrevertimg
Incident
revertimgrevertimgrevertimgrevertimg
Finding
revertimgrevertimgrevertimgrevertimg
Grade
revertimgrevertimgrevertimgrevertimg
Digital Assets

Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.

These are some of the factors we use to calculate the overall score:

Network Security

Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.

SBOM (Software Bill of Materials)

Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.

CMDB (Configuration Management Database)

Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.

Threat Intelligence

Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.

Top LeftTop RightBottom LeftBottom Right
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.
Users Love Us Badge