Erie County Medical Center Corporation Company Cyber Security Posture

ecmc.edu

ECMC is a medical leader that makes patient experience our first priority, and brings compassionate, first-class care to the eight counties of Western New York, as well as Southern Ontario. Our presence and care extend throughout our area, from our advanced academic medical center on our main campus with 602 inpatient beds, to our multiple specialized centers of excellence, to our Terrace View Long-Term Care Facility with 390 beds, to on- and off-campus primary care and family health centers. In addition, as a verified, designated Level 1 Adult Trauma Center as well as regional center for burn care, behavioral health services, transplantation, cancer care, and more, we work with some of the most critical patient cases in Western New York. With this combination of knowledgeable, experienced doctors, a wealth of research, and advanced technology, weโ€™re proud to offer Western New York a healthier futureโ€”and prouder still to show our community the difference between healthcare and true care(TM).

ECMCC Company Details

Linkedin ID:

erie-county-medical-center

Employees number:

1797 employees

Number of followers:

14033.0

NAICS:

62

Industry Type:

Hospitals and Health Care

Homepage:

ecmc.edu

IP Addresses:

Scan still pending

Company ID:

ERI_2356601

Scan Status:

In-progress

AI scoreECMCC Risk Score (AI oriented)

Between 800 and 900

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

Ailogo

Erie County Medical Center Corporation 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 800 and 900

Erie County Medical Center Corporation Company Cyber Security News & History

Past Incidents
1
Attack Types
1
EntityTypeSeverityImpactSeenUrl IDDetailsView
Erie County Medical Center CorporationRansomware85304/2017ERI24514822Link
Rankiteo Explanation :
Attack with significant impact with internal employee data leaks

Description: Erie County Medical Center was the victim of a ransomware attack in April 2017 that shut down the hospital's entire computer network but also affected the care delivered to patients or nursing home residents. According to Peter Cutler, the facility has accepted all inbound patients and has continued with all scheduled surgical procedures. While IT professionals attempt to bring computer systems back up, hospital and nursing home employees manually admitted patients, filled prescriptions, and scheduled tests. The FBI and the State Police investigated the incident and restored everything quickly.

Erie County Medical Center Corporation Company Subsidiaries

SubsidiaryImage

ECMC is a medical leader that makes patient experience our first priority, and brings compassionate, first-class care to the eight counties of Western New York, as well as Southern Ontario. Our presence and care extend throughout our area, from our advanced academic medical center on our main campus with 602 inpatient beds, to our multiple specialized centers of excellence, to our Terrace View Long-Term Care Facility with 390 beds, to on- and off-campus primary care and family health centers. In addition, as a verified, designated Level 1 Adult Trauma Center as well as regional center for burn care, behavioral health services, transplantation, cancer care, and more, we work with some of the most critical patient cases in Western New York. With this combination of knowledgeable, experienced doctors, a wealth of research, and advanced technology, weโ€™re proud to offer Western New York a healthier futureโ€”and prouder still to show our community the difference between healthcare and true care(TM).

Loading...

Access Data Using Our API

SubsidiaryImage

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?linkedin_id=erie-county-medical-center' -H 'apikey: YOUR_API_KEY_HERE'
newsone

ECMCC Cyber Security News

2025-05-26T07:00:00.000Z
Healthcare Data Breach Statistics

In 2023, more than 93 million healthcare records were exposed or stolen in data breaches at business associates compared to 34.9 million recordsย ...

2025-04-21T07:00:00.000Z
Buffalo hospitals cautiously seek innovative medical applications of AI

The AI tools currently being used by Kaleida are deliberately narrow in scope. One helps clinicians interpret CT scans and EKGs, anotherย ...

2024-09-17T07:00:00.000Z
HTNYS' 44th Annual Trustee Conference: Photos and recap

Read the latest blog posts by HANYS' experts on key health and healthcare policy issues.

2018-01-29T08:00:00.000Z
Erie County Medical Center: Anatomy of a ransomware attack

Buffalo, NY hospital's response to cybercriminals taking its data hostage provides valuable lessons for other healthcare providers.

2024-07-30T07:00:00.000Z
Q&A: Lucia Rossi, VP of Population Health at Erie County Medical Center

Rossi: Erie County Medical Center is one of the only Level One trauma centers in the State of New York. It is also one of the largest safety netย ...

2024-10-28T07:00:00.000Z
The 2024 Upstate Power 100

The 2024 Upstate Power 100: The New York leaders revitalizing Rust Belt cities and reimagining rural regions.

2024-08-10T07:00:00.000Z
HIPAA Violation Cases

A summary of HIPAA violation cases from 2013 to 2024 indicating that HHS' Office for Civil Rights is increasing enforcement action.

2024-08-01T07:00:00.000Z
Acadian Ambulance Services Leaks Protected Health Information After Cyber Attack

Acadian Ambulance Services is investigating a cyber attack that leaked the protected health and personal information of potentially millionsย ...

2023-10-23T07:00:00.000Z
Healthcare ransomware attacks cost US $77.5B since 2016

539 ransomware attacks on healthcare organizations in the US have been confirmed. These attacks impacted more than 52 million patient records.

similarCompanies

ECMCC Similar Companies

Help at Home

In our 45+ year history, Help at Home has provided care for individuals, helping them to remain independent and able to live their best lives in their own homes. Our clients have always been like family. As the leading national provider of high-quality, relationship-based home care for seniors and p

Cincinnati Children's

Cincinnati Childrenโ€™s, a nonprofit academic medical center established in 1883, offers services from well-child care to treatment for the most rare and complex conditions. It is the Department of Pediatrics at the University of Cincinnati College of Medicine and trains more than 600 residents and cl

Intermountain Health

As the largest nonprofit health system in the Mountain West, Intermountain Health is dedicated to creating healthier communities and helping our patients and caregivers thrive. Itโ€™s time to think of health in a whole new way, and by partnering with our patients and communities, providing expert

At AdventHealth, Extending the Healing Ministry of Christ is our mission. It calls us to be His hands and feet in helping people feel whole. Our story is one of hope โ€” one that strives to heal and restore the body, mind and spirit. More than 80,000 skilled and compassionate caregivers in physician

Aveanna Healthcare

About Aveanna It all started with a simple idea: How can we help people live better lives by providing better homecare? That idea became a company called Aveanna, dedicated to bringing new possibilities and new hope to those we serve. At Aveanna, we believe that the ultimate place for caring is rig

Evangelische Heimstiftung GmbH

Stell dir vor, gemeinsam gestalten wir gute Pflege. Diakonisch รขโ‚ฌโ€œ Innovativ รขโ‚ฌโ€œ Professionell. Wir sind die Evangelische Heimstiftung รขโ‚ฌโ€œ das grรƒยถรƒลธte diakonische Pflegeunternehmen in THE Lรƒโ€žND. Gemeinsam mit 10.200 Mitarbeitenden und 810 Auszubildenden betreuen wir 14.760 Menschen in 172 Einrichtu

faq

Frequently Asked Questions (FAQ) on Cybersecurity Incidents

ECMCC CyberSecurity History Information

Total Incidents: According to Rankiteo, ECMCC 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 ECMC is a medical leader that makes patient experience our first priority, and brings compassionate, first-class care to the eight counties of Western New York, as well as Southern Ontario. Our presence and care extend throughout our area, from our advanced academic medical center on our main campus with 602 inpatient beds, to our multiple specialized centers of excellence, to our Terrace View Long-Term Care Facility with 390 beds, to on- and off-campus primary care and family health centers. In addition, as a verified, designated Level 1 Adult Trauma Center as well as regional center for burn care, behavioral health services, transplantation, cancer care, and more, we work with some of the most critical patient cases in Western New York. With this combination of knowledgeable, experienced doctors, a wealth of research, and advanced technology, weโ€™re proud to offer Western New York a healthier futureโ€”and prouder still to show our community the difference between healthcare and true care(TM)..

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