What Happened?
A technological fault in Meuhedet's digital system allowed unauthorized access to insured members' medical information. The incident was discovered after a member reported being able to view the medical file of his stepsister. The database where the incident occurred contains personal information about a large number of data subjects, including highly sensitive health information.
Meuhedet knew about the incident as early as November 2025, but did not report it immediately as required by Regulation 11(d) of the Privacy Protection (Information Security) Regulations. Only after about a month and a half of internal investigations, at the end of January 2026, was it determined that the fault was systemic. The incident was reported to the Authority only about two months after the member's complaint.
The Authority's Position: Immediate Reporting, No Delay
According to the Authority, from the moment Meuhedet became aware of the incident and blocked the member's access, it already had sufficient information indicating a serious information security event, and the report should have been submitted immediately. Waiting for the completion of internal investigations empties the requirement of "immediacy." The required report is an initial report based on information known at the time, with additional details to be provided in a supplementary report later.
Key Takeaways: What to Check Now
Reporting Must Be Immediate
The reporting obligation arises the moment a serious security incident becomes known, and must be carried out promptly upon discovery without delay. The initial report is based on information known at the time, and supplementary details can be added later. Anyone who waits "to understand first" exposes themselves to significant financial sanctions.
DPO Involvement
Organizations should examine how they operate information security incident response, with emphasis on the involvement of the Data Protection Officer (DPO). The DPO should be involved in identifying and determining whether an incident qualifies as a serious information security event requiring immediate reporting — before the completion of internal investigations. Quick and accurate decision-making by the DPO is what prevents exposure to fines.
Clear Internal Procedures
Organizations should assume the Authority is not lenient. NIS 256,000 for a two-month reporting delay — this precedent will serve as the basis for additional sanctions. A clear internal procedure is needed: incident identification, immediate reporting to the Authority in parallel with internal investigation, and a supplementary report afterward. The sensitivity of the data and the number of affected individuals influence the severity of the sanction.
Amendment 13: Not Just a Warning, Active Enforcement
Amendment 13 to the Privacy Protection Law, which took effect in August 2025, granted the Authority significant enforcement powers, including the ability to impose financial sanctions of hundreds of thousands of shekels and criminal investigation powers. The Authority worked on this case for six months, including a written and oral hearing, before determining the violation and the fine amount. This is the first case to mature — and it is meant to serve as a central message about the importance of immediate reporting.
Recommended Actions
- Review your security incident response procedure — ensure it includes immediate reporting to the Authority in parallel with internal investigation, not after it.
- DPO involvement — ensure the Data Protection Officer is involved in determining whether an incident is serious, before investigations are complete.
- Staff training — ensure relevant staff know when the reporting obligation arises and who to contact within the organization.
Think this doesn't apply to you? The immediate reporting obligation applies to any database controller where a serious security incident occurs — not just public bodies. If your organization processes personal data, it's worth examining your procedures now, before the Authority does it for you.
Source: Official publication by Israel's Privacy Protection Authority
Frequently asked questions
What is a financial sanction under Amendment 13?
Amendment 13 to the Privacy Protection Law, which took effect in August 2025, granted the Privacy Protection Authority enhanced enforcement powers, including the ability to impose financial sanctions of hundreds of thousands of shekels on organizations that violate the law. The first sanction was imposed on Meuhedet HMO in the amount of NIS 256,000 for failing to immediately report a serious security incident.
When does the immediate reporting obligation for a serious security incident arise?
The reporting obligation arises the moment a serious security incident becomes known, and must be carried out promptly upon discovery without delay. There is no need to wait for the completion of internal investigations. An initial report must be submitted immediately, and supplementary details can be provided in a supplementary report later.
Can the Authority be notified after an internal investigation of the incident?
No. The Authority determined that waiting for the completion of all investigations empties the requirement of immediacy. The initial report must be submitted immediately with the information known, and the investigations and additional details can and should be completed in a supplementary report later.
What involvement is required from the Data Protection Officer (DPO) in security incidents?
The Data Protection Officer must be involved in identifying and determining whether an incident qualifies as a serious information security event requiring immediate reporting to the Authority, before the completion of internal investigations. Quick and accurate decision-making by the DPO is what prevents exposure to fines.
The above is general information only and does not constitute legal advice. For guidance tailored to your specific circumstances — talk to us.
Want to know what applies to your company?
Talk to us