Alberta Health Services Company Cyber Security Posture

albertahealthservices.ca

Alberta Health Services (AHS) is Canadaโ€™s first and largest province wide, fully-integrated health system, responsible for delivering health services to the over four million people living in Alberta. Our skilled and dedicated professionals, support staff and physicians come from numerous disciplines, from all walks of life, and from all corners of the world. Our mission is to provide a patient-focused, quality health system that is accessible and sustainable for all Albertans. Our five values โ€“ compassion, accountability, respect, excellence and safety โ€“ are at the heart of everything that we do.

AHS Company Details

Linkedin ID:

alberta-health-services

Employees number:

45103 employees

Number of followers:

188829.0

NAICS:

62

Industry Type:

Hospitals and Health Care

Homepage:

albertahealthservices.ca

IP Addresses:

153

Company ID:

ALB_2187366

Scan Status:

In-progress

AI scoreAHS 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

Alberta Health Services 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

Alberta Health Services Company Cyber Security News & History

Past Incidents
3
Attack Types
1
EntityTypeSeverityImpactSeenUrl IDDetailsView
Alberta Health ServicesData Leak50211/2021ALB1558121222Link
Rankiteo Explanation :
Attack limited on finance or reputation

Description: Alberta Health suffered a data breach after at least 12 users downloaded the wrong information from the province's COVID-19 vaccination record website. The record those users downloaded contained the name, date of birth and vaccine information. ย Albertans experienced issues accessing the updated vaccine record for travel due to the breach.

Alberta Health ServicesData Leak85308/2019ALB11183423Link
Rankiteo Explanation :
Attack with significant impact with internal employee data leaks

Description: Almost 7,000 patients were informed by Alberta Health Services that a doctor's Gmail account had been stolen, exposing their personal health information. The doctor working at the Richmond Road Diagnostic Centre in Calgary improperly used a private account to transmit health information While this privacy breach was unintentional and was deeply regretted by the physician, that does not in any way diminish the seriousness of the matter. There was no evidence to suggest that affected patients' information has been accessed by the hacker, the agency says.

Alberta Health ServicesData Leak50210/2019ALB31917423Link
Rankiteo Explanation :
Attack limited on finance or reputation

Description: Alberta Health Services (AHS) says a computer hard drive that contained the personal health information of about 650 patients has been missing since August. The exposed information includes patient names, gender, dates of birth, physician names and medical record numbers. The agency says the external drive vanished from a cardiac outpatient clinical lab at the Mazankowski Alberta Heart Institute in Edmonton. It was found that the external drive was not encrypted, as mandatory, and did not have password protection.

Alberta Health Services Company Subsidiaries

SubsidiaryImage

Alberta Health Services (AHS) is Canadaโ€™s first and largest province wide, fully-integrated health system, responsible for delivering health services to the over four million people living in Alberta. Our skilled and dedicated professionals, support staff and physicians come from numerous disciplines, from all walks of life, and from all corners of the world. Our mission is to provide a patient-focused, quality health system that is accessible and sustainable for all Albertans. Our five values โ€“ compassion, accountability, respect, excellence and safety โ€“ are at the heart of everything that we do.

Loading...

Access Data Using Our API

SubsidiaryImage

Get company history

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

AHS Cyber Security News

2025-06-20T07:00:00.000Z
Hospital cyber attacks cost $600K/hour. Hereโ€™s how AI is changing the math

When something unusual happens โ€” like a device suddenly talking to an external server it's never contacted before โ€” it flags it right away. Thatย ...

2024-11-14T08:00:00.000Z
Investigation underway after Alberta Innovates hit by cyberattack

An Alberta Crown corporation says it recently experienced "network issues" after it was the target of a cyberattack.

2025-02-27T08:00:00.000Z
Fasken Noteworthy Privacy & Cybersecurity News (February 2025)

This is a monthly bulletin published by the Privacy and Cybersecurity Group at Fasken with noteworthy news and updates. If you have anyย ...

2024-12-03T16:09:37.000Z
Privacy, Data Protection & Cybersecurity | Services

Organizations face increasing risks in the areas of privacy, data protection and cybersecurity. Canadian and international privacy laws are changing.

2025-01-21T08:00:00.000Z
Alberta overhauls its public sector access and privacy regime

In December of last year, the Alberta legislature passed a major overhaul of Alberta's access and privacy legislation.

2024-07-19T07:00:00.000Z
Little impact from CrowdStrike outage: AHS

Cybersecurity firm CrowdStrike said the glitch felt around the world occurred when it deployed a faulty update to computers running Microsoftย ...

2024-08-12T12:44:23.000Z
Donโ€™t Fall For It โ€” Keep An Eye Out For These Social Engineering Tactics

October is Cybersecurity Awareness Month and this month we're bringing attention to the rise scams, phishing attacks and social engineering.

2022-05-16T07:00:00.000Z
AHS cybersecurity head warns of 'large number of attacks' using health body's name

"We do see a large number of attacks that are going out to individuals that they're trying to pretend that they are Alberta Health Services.".

2025-02-12T08:00:00.000Z
31 Alberta schools affected by cyberattack on school software: privacy commissioner

The Office of the Information and Privacy Commissioner (OIPC) says 31 Alberta schools have now reported data breaches related to aย ...

similarCompanies

AHS Similar Companies

IQVIA

IQVIA (NYSE:IQV) is a leading global provider of clinical research services, commercial insights and healthcare intelligence to the life sciences and healthcare industries. IQVIAโ€™s portfolio of solutions are powered by IQVIA Connected Intelligenceโ„ข to deliver actionable insights and services built o

OhioHealth

OhioHealth is a nationally recognized, not-for-profit, faith-based health system of more than 35,000 associates, providers and volunteers. We lead with our mission to improve the health of those we serve throughout our 15 hospitals and 200+ urgent, primary and specialty care sites spanning 50 Ohio c

Houston Methodist

Houston Methodist is one of the nationโ€™s leading health systems and academic medical centers. The health system consists of eight hospitals: Houston Methodist Hospital, its flagship academic hospital in the Texas Medical Center, seven community hospitals and one long-term acute care hospital through

Cencora

Cencora, a company building on the legacy of AmerisourceBergen, is a leading global pharmaceutical solutions organization centered on improving the lives of people and animals around the world. We connect manufacturers, providers, and patients to ensure that anyone can get the therapies they need, w

St. Luke's Health System

As the only Idaho-based, not-for-profit health system, St. Lukeโ€™s Health System is dedicated to our mission โ€œTo improve the health of people in the communities we serve.โ€ Today that means not only treating you when youโ€™re sick or hurt, but doing everything we can to help you be as healthy as possibl

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

faq

Frequently Asked Questions (FAQ) on Cybersecurity Incidents

AHS CyberSecurity History Information

Total Incidents: According to Rankiteo, AHS has faced 3 incidents in the past.

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

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 Alberta Health Services (AHS) is Canadaโ€™s first and largest province wide, fully-integrated health system, responsible for delivering health services to the over four million people living in Alberta. Our skilled and dedicated professionals, support staff and physicians come from numerous disciplines, from all walks of life, and from all corners of the world. Our mission is to provide a patient-focused, quality health system that is accessible and sustainable for all Albertans. Our five values โ€“ compassion, accountability, respect, excellence and safety โ€“ are at the heart of everything that we do..

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: The most common types of attacks the company has faced are ['Data Leak'].

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