Thunder Bay Regional Health Sciences Centre Company Cyber Security Posture
tbrhsc.netThunder Bay Regional Health Sciences Centre (TBRHSC) is a 425-bed acute care facility and academic health sciences centre. As the only tertiary health care provider in the region, Thunder Bay Regional Health Sciences Centre provides comprehensive care to more than 245,000 people in a region the size of France. TBRHSC teaches the next generation of health care providers and advances medical research through the Thunder Bay Regional Health Research Institute (TBRHRI). Patients benefit from interprofessional teams of dedicated health care providers and access to leading-edge medical technology and clinical trials. TBRHSC is proudly affiliated with Lakehead University and Confederation College and is a host training facility for students from the NOSM University, as well as other medical schools. TBRHSC operates on sacred land. We respectfully acknowledge that we work on the traditional lands of the people of Fort William First Nation. This land is the territory of the Anishinabek Nation and is home to the Robinson-Superior Treaty of 1850. Today, Thunder Bay is the home to many Indigenous Peoples from across Turtle Island and we are grateful to have the opportunity to work together in this community and on this territory. We are committed to embedding equity, diversity and inclusion in all the care, education and research that we do. We believe that our differences are key to our growth as an organization and a community, and to our ability to develop innovative approaches to deliver exceptional care to patients, every time.
TBRHSC Company Details
tbrhsc
1520 employees
7579.0
62
Hospitals and Health Care
tbrhsc.net
Scan still pending
THU_2630474
In-progress
TBRHSC Risk Score (AI oriented)Between 800 and 900
This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.
TBRHSC Global Score.png)
Thunder Bay Regional Health Sciences Centre Company Scoring based on AI Models
| Model Name | Date | Description | Current Score Difference | Score |
|---|---|---|---|---|
| AVERAGE-Industry | 03-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 800 and 900 |
Thunder Bay Regional Health Sciences Centre Company Cyber Security News & History
| Entity | Type | Severity | Impact | Seen | Url ID | Details | View |
|---|---|---|---|---|---|---|---|
| Thunder Bay Regional Health Sciences Centre | Data Leak | 60 | 3 | 04/2020 | THU1546291222 | Link | |
Rankiteo Explanation : Attack with significant impact with internal employee data leaksDescription: 245 employees at the Thunder Bay Regional Health Sciences Centre had their personal information published online by their workplace. It was published on the hospital's website which included their names, and other personally identifying information. The information was online for about a week and a half. The internal error in early, took down the identifying information. | |||||||
Thunder Bay Regional Health Sciences Centre Company Subsidiaries
Thunder Bay Regional Health Sciences Centre (TBRHSC) is a 425-bed acute care facility and academic health sciences centre. As the only tertiary health care provider in the region, Thunder Bay Regional Health Sciences Centre provides comprehensive care to more than 245,000 people in a region the size of France. TBRHSC teaches the next generation of health care providers and advances medical research through the Thunder Bay Regional Health Research Institute (TBRHRI). Patients benefit from interprofessional teams of dedicated health care providers and access to leading-edge medical technology and clinical trials. TBRHSC is proudly affiliated with Lakehead University and Confederation College and is a host training facility for students from the NOSM University, as well as other medical schools. TBRHSC operates on sacred land. We respectfully acknowledge that we work on the traditional lands of the people of Fort William First Nation. This land is the territory of the Anishinabek Nation and is home to the Robinson-Superior Treaty of 1850. Today, Thunder Bay is the home to many Indigenous Peoples from across Turtle Island and we are grateful to have the opportunity to work together in this community and on this territory. We are committed to embedding equity, diversity and inclusion in all the care, education and research that we do. We believe that our differences are key to our growth as an organization and a community, and to our ability to develop innovative approaches to deliver exceptional care to patients, every time.
Access Data Using Our API
Get company history
Rapid.png)
TBRHSC Cyber Security News
Porter flights cancelled, but Thunder Bay police, hospital, city services not affected by global IT outage
Porter Airlines has cancelled flights until noon, including the 11:20 a.m. flight arriving in Thunder Bay and the noon flight departing Thunder ...
Thunder Bay: Doane Grant Thornton helps business leaders make a vibrant community
Accounting firm Doane Grant Thornton spent the last few months asking members of the local business community how they can improve Thunder Bay.
Northeastern Ontario hospitals impacted by global IT outage
Some flights, border crossings affected. Sault Area Hospital announced at around 1:30 p.m. Friday that its computer systems had been restored.
London police and hospital service not affected by global IT outage
The London Police Service said it is not affected by the IT issue and people can still call 9-1-1 to reach police in an emergency situation.
David Bruno seeks Liberal nomination in Thunder Bay-Rainy River
David Bruno officially announced on Wednesday he will be seeking the Liberal Party nomination in the riding, joining Thunder Bay city councillor ...
TBRHSC Similar Companies
Kindred
Kindred’s mission is to help our patients reach their highest potential for health and healing with intensive medical and rehabilitative care through a compassionate patient experience. Kindred’s 61 long-term acute care hospitals (LTACHs), along with 18 community-based, short-term acute care hospit
Helse Vest
The Western Norway Regional Health Authority (WNRHA, Helse Vest) has overall responsibility for providing specialised health services in the counties of Rogaland, Hordaland and Sogn og Fjordane. Its role is to ensure that the inhabitants of the region have access to the services they are legally ent
CVS Health
CVS Health is the leading health solutions company, delivering care like no one else can. We reach more people and improve the health of communities across America through our local presence, digital channels and over 300,000 dedicated colleagues – including more than 40,000 physicians, pharmacists,
Helse Sør-Øst RHF
South Eastern Norway Regional health Authority is a merger between the former Eastern and South regional Health Authority. Responsible for secondary healthcare services for the south-eastern parts of Norway 2.5 million people (approx 52% of population) cost containment budget 58 billion Nkr. 100%
Hampshire and Isle of Wight Healthcare NHS Foundation Trust
We provide a wide range of community, mental health and learning disability services for people across Hampshire and the Isle of Wight. We have a team of over 12,500 people working in the community and local hospitals. We serve a population of around 1.5million people, providing care for every stag
IHH HEALTHCARE MALAYSIA
IHH Healthcare Malaysia is one of the largest private healthcare providers in Malaysia, with approximately 3,000 beds. Our healthcare network comprises 11 Pantai Hospitals, four Gleneagles Hospitals, Prince Court Medical Centre and Timberland Medical Centre, and is complemented by ancillary service
Frequently Asked Questions (FAQ) on Cybersecurity Incidents
TBRHSC CyberSecurity History Information
Total Incidents: According to Rankiteo, TBRHSC has faced 1 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 Thunder Bay Regional Health Sciences Centre (TBRHSC) is a 425-bed acute care facility and academic health sciences centre. As the only tertiary health care provider in the region, Thunder Bay Regional Health Sciences Centre provides comprehensive care to more than 245,000 people in a region the size of France. TBRHSC teaches the next generation of health care providers and advances medical research through the Thunder Bay Regional Health Research Institute (TBRHRI). Patients benefit from interprofessional teams of dedicated health care providers and access to leading-edge medical technology and clinical trials. TBRHSC is proudly affiliated with Lakehead University and Confederation College and is a host training facility for students from the NOSM University, as well as other medical schools. TBRHSC operates on sacred land. We respectfully acknowledge that we work on the traditional lands of the people of Fort William First Nation. This land is the territory of the Anishinabek Nation and is home to the Robinson-Superior Treaty of 1850. Today, Thunder Bay is the home to many Indigenous Peoples from across Turtle Island and we are grateful to have the opportunity to work together in this community and on this territory. We are committed to embedding equity, diversity and inclusion in all the care, education and research that we do. We believe that our differences are key to our growth as an organization and a community, and to our ability to develop innovative approaches to deliver exceptional care to patients, every time..
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
Incident 1: Ransomware Attack
Regulations Violated: {Regulations_Violated}
Fines Imposed: {Fines_Imposed}
Legal Actions: {Legal_Actions}
Regulatory Notifications: {Regulatory_Notifications}
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
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?
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:
Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.
Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.
Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.
Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.
