Mayanei Hayeshua Medical Center Company Cyber Security Posture
mymc.co.ilMayanei Hayeshua Medical Center (MHMC) is a growing 320-bed independent community hospital with 18 medical departments and 32 outpatient clinics and institutes. Serving the greater Petach Tikva, Givat Shmuel, Bnei Brak and Ramat Gan region – and beyond – the hospital is dedicated to providing world-class patient care. As an integral part of the community, Mayanei Hayeshua accepts patients regardless of race, religion or color. A commitment to dignity of life has always been at the heart of the hospital’s ethos. Mayanei Hayeshua is recognized throughout Israel’s medical community and overseas as providing the highest quality personal patient care.
MHMC Company Details
mayanei-hayeshua-medical-center
52 employees
118
62
Hospitals and Health Care
mymc.co.il
Scan still pending
MAY_2999978
In-progress
MHMC Risk Score (AI oriented)Between 800 and 900
This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.
MHMC Global Score.png)
Mayanei Hayeshua Medical Center 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 |
Mayanei Hayeshua Medical Center Company Cyber Security News & History
| Entity | Type | Severity | Impact | Seen | Url ID | Details | View |
|---|---|---|---|---|---|---|---|
| Mayanei Hayeshua Medical Center | Cyber Attack | 60 | 2 | 08/2023 | MAY319823 | Link | |
Rankiteo Explanation : Attack limited on finance or reputationDescription: Mayanei Hayeshua Medical Center in Bnei Brak was hit by a cyberattack, after that the hospital’s administrative computers were shut down. East of Tel Aviv is where the ultra-Orthodox hospital is located. It said that no medical equipment was harmed in the incident and that patients are being treated. The ministry, however, ordered that until further notice, the public should refrain from visiting the center's emergency room and outpatient clinics, imaging centres, and labs. | |||||||
| Mayanei Hayeshua Medical Center | Data Leak | 100 | 4 | 09/2023 | MAY114617923 | Link | |
Rankiteo Explanation : Attack with significant impact with customers data leaksDescription: Cyber criminals who attacked an Israeli hospital have started disclosing private information that was obtained during the breach. Just outside of Tel Aviv in Bnei Brak, the Ragnar Locker gang attacked the Mayanei Hayeshua Medical Centre. A whole SQL database and a sizable quantity of.pst files containing internal correspondence were among the 1TB of data that the hackers were able to steal. The attackers claimed they were posting the initial batch of hospital files they had stolen, which contained a lot of personal information, internal correspondence, finances, medical cards, as well as additional highly sensitive data. | |||||||
Mayanei Hayeshua Medical Center Company Subsidiaries
Mayanei Hayeshua Medical Center (MHMC) is a growing 320-bed independent community hospital with 18 medical departments and 32 outpatient clinics and institutes. Serving the greater Petach Tikva, Givat Shmuel, Bnei Brak and Ramat Gan region – and beyond – the hospital is dedicated to providing world-class patient care. As an integral part of the community, Mayanei Hayeshua accepts patients regardless of race, religion or color. A commitment to dignity of life has always been at the heart of the hospital’s ethos. Mayanei Hayeshua is recognized throughout Israel’s medical community and overseas as providing the highest quality personal patient care.
Access Data Using Our API
Get company history
Rapid.png)
MHMC Cyber Security News
Lawmakers warn of impact HHS firings will have on medical device cybersecurity efforts
The firings would stymie this process, hampering efforts to release new, innovative medical devices and potentially damage work done to monitor new issues.
Israel’s health, management systems crash for several hours due to Crowdstrike collapse
A worldwide CrowdStrike system malfunction led to massive failures on Microsoft Windows systems globally, including in Israel, due to a ...
Bnei Brak hospital hit by cyberattack, bringing down computers
Mayanei Hayeshua Medical Center in Bnei Brak said Tuesday it was targeted overnight in a ransomware attack that shut down its administrative ...
Cyber attack paralyzes Israeli hospital's computer systems
Mayanei Hayeshua Medical Center in Bnei Brak is dealing with a ransomware attack that damaged and shut down administrative computer systems ...
Israeli Hospital Hit By Ransomware Attack, 1TB Data Stolen
Cyber attackers who hit an Israeli hospital have begun releasing sensitive data that it collected in the breach. The Ragnar Locker gang hit ...
Israeli Hospital Near Tel Aviv Targeted In Cyberattack
Israel's hospitals found themselves in the crosshairs of cyber criminals overnight between Monday and Tuesday, as a major hospital was hit, forcing new ...
Psychiatric hospital near Jerusalem hit by suspected cyberattack
A suspected cyberattack hit the Eitanim psychiatric hospital near Jerusalem, forcing staff to switch to manual protocols, the Health ...
Start-up nation? Israel's cyber defense collapsed on October 7 and Iranian hacker groups keep attacking
Multiple Iran-affiliated hacker groups infiltrated databases containing thousands of highly sensitive files regarding Israeli soldiers, civilians and companies.
Ragnar Locker gang leaks data stolen from the Israel’s Mayanei Hayeshua hospital
The Ragnar Locker ransomware gang claimed responsibility for an attack on Israel's Mayanei Hayeshua hospital. The cybercrime group claims to have stolen 1 TB of ...
MHMC Similar Companies
Philips
Over the past decade we have transformed into a focused leader in health technology. At Philips, our purpose is to improve people’s health and well-being through meaningful innovation. We aim to improve 2.5 billion lives per year by 2030, including 400 million in underserved communities. We see h
Nytida
Nytida ger stöd till barn, unga och vuxna för hela livets behov inom funktionsnedsättning och psykosocial problematik. Vi erbjuder boende, daglig verksamhet, stöd till individ och familj samt skola på cirka 400 enheter i Sverige. Vår vision: Vi gör världen lite bättre, en människa i taget
Humana AB
Humana är ett ledande nordiskt omsorgsföretag som erbjuder tjänster inom individ- och familjeomsorg, personlig assistans, äldreomsorg och bostäder med särskild service enligt LSS. Humana har cirka 16 000 engagerade medarbetare i Sverige, Norge, Finland och Danmark som utför omsorgstjänster
Region Hovedstaden
Det handler om liv. Om at bringe liv til verden og skabe livskvalitet. Om at redde liv og forbedre liv. Som medarbejder i Region Hovedstaden træder du ind i en verden af muligheder og mangfoldighed med plads til dine ambitioner. Du er en del af et stærkt fagligt miljø, hvor vi har fingeren på pulsen
McKesson Medication Management
McKesson's vision is to help create a health care system where quality is higher, mistakes are fewer and costs are lower. As the nation's leading health care services company, we provide pharmaceuticals, medical supplies and health care information technologies that make health care safer while redu
CERBA HEALTHCARE
Cerba HealthCare, a leading player in medical diagnosis, aims to support the evolution of health systems towards more prevention. It draws on more than 50 years of expertise in clinical pathology to better assess the risk of diseases development, detect and diagnose diseases earlier, and optimize th
Frequently Asked Questions (FAQ) on Cybersecurity Incidents
MHMC CyberSecurity History Information
Total Incidents: According to Rankiteo, MHMC has faced 2 incidents in the past.
Incident Types: The types of cybersecurity incidents that have occurred include ['Cyber Attack', '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 Mayanei Hayeshua Medical Center (MHMC) is a growing 320-bed independent community hospital with 18 medical departments and 32 outpatient clinics and institutes. Serving the greater Petach Tikva, Givat Shmuel, Bnei Brak and Ramat Gan region – and beyond – the hospital is dedicated to providing world-class patient care. As an integral part of the community, Mayanei Hayeshua accepts patients regardless of race, religion or color. A commitment to dignity of life has always been at the heart of the hospital’s ethos. Mayanei Hayeshua is recognized throughout Israel’s medical community and overseas as providing the highest quality personal patient care..
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.
