What Amendment 13 is
The Privacy Protection Law is Israel’s main law governing how organizations collect, store and use personal information. Amendment 13 to the law was approved by the Knesset in 2024 and came into force in August 2025, and it is considered one of the most significant updates to the law since it was enacted.
The amendment updated key definitions in the law, including the definitions of personal data and of information of special sensitivity (sensitive data). It changed the arrangement for registering databases (database registration), added a duty to appoint a privacy protection officer (DPO) in certain organizations, and above all gave the Privacy Protection Authority much stronger enforcement tools than it had before.
For businesses, the practical meaning is simple: obligations that existed on paper, especially data security obligations, are now backed by enforcement.
Enforcement powers and administrative fines
The most notable change concerns enforcement. The Privacy Protection Authority received broader supervision and investigation powers, and the power to impose administrative fines on organizations that violate the provisions of the law, in an administrative proceeding and without the need for a criminal proceeding. The amount of the fine depends, among other things, on the type of violation and the scope of the information it involves, and in some cases it can be very significant for a business.
Beyond the fine itself, enforcement has a cost that is hard to measure: management time spent on the inquiry, reputational damage, and customers who lose trust. An organization going through an inquiry by the Authority has to show what it actually did to protect the information, and policy documents that were never implemented will not help it. And such an inquiry does not have to start with a data breach: it can also start after a complaint from a customer or an employee.
Databases: what changed
In the past, many organizations were required to register their databases with the Database Registrar. The amendment narrowed the registration requirement so that today it applies only to certain types of databases, and in some cases a notice to the Authority is required instead of registration.
It is important to understand what this narrowing does not change. The substantive obligations apply to every database, registered or not: using the information only for the purpose for which it was collected (purpose limitation), allowing people to review the information about them (right of access), restricting access to it (access control) and securing it as required. A business that concluded from the amendment that it no longer has anything to do understood it the wrong way around.
In practice, a database can be almost any organized collection of personal information: a CRM system, a customer list in a spreadsheet, employee files, an accounting system or inquiries that come in from a form on the website. Personal information is often found outside the central systems too: in files downloaded to employees’ computers, in mailboxes and in shared folders (file shares). A data mapping exercise that ignores these places leaves out exactly the information that is hardest to protect.
Data security: an existing duty that is now enforced
The Privacy Protection Regulations (Data Security) have existed for several years, and they detail what an organization must do to secure databases. The regulations divide databases into security levels, basic, intermediate and high, according to the type of information, the number of people it concerns and the number of authorized users. The higher the level, the stricter the requirements.
The requirements include, among others:
- A database definitions document and a written security procedure.
- Permission management: each user gets access only to what they need (least privilege), and there is a record of who is authorized.
- Appropriate identification and authentication measures for access to systems.
- Access logging and tracking of events in the systems (audit log), at the higher security levels.
- Protection of the systems’ connection to the internet and of remote access.
- Backup and the ability to restore (backup and restore).
- Handling security incidents (incident response), and in certain cases reporting a severe incident to the Authority.
- Periodic review (periodic audit), and for high-level databases also a risk assessment and penetration tests.
Most of these requirements are IT matters: who can sign in to which system, how they are authenticated, what is logged, how backups are made and how incidents are handled. That is why Amendment 13 concerns the IT company just as much as it concerns the legal adviser.
Privacy protection officer
The amendment requires certain organizations to appoint a privacy protection officer (DPO). Among the bodies the duty applies to: public bodies, certain data brokers, and bodies whose main activity includes processing information of special sensitivity on a significant scale or systematic monitoring of people on a significant scale. The exact definitions matter, and it is worth checking them with a legal adviser.
The privacy protection officer is responsible for overseeing compliance with the law, advising management and serving as the contact person for the Authority and for people who make inquiries about their information. This is a different role from the information security officer, whom certain bodies were already required by law to appoint. In practice the two work closely together, because privacy cannot be protected without information security.
What a business needs to do now
- Map the information (data mapping): which personal information the organization holds, where it is located, who accesses it and for what purpose it is used.
- Check the legal status: whether there is a database that requires registration or notice, and what the security level of each database is. Legal advice is needed here.
- Check whether there is a duty to appoint a privacy protection officer or an information security officer.
- Close security gaps (remediation): permissions, MFA, access logging, backup, network separation (segmentation) and endpoint and server protection (EDR).
- Write and update documents: a definitions document, a security procedure and a privacy policy that reflect the actual situation.
- Review suppliers: who processes information on the organization’s behalf (data processor), and what the agreement with them says about security.
- Prepare for an incident (incident response): what to do when a leak is suspected, who decides, and whom you need to inform.
The role of the IT company
The common gap in businesses is between the documents and reality. A well-written security procedure is worth little if in practice every employee signs in with administrator rights (local admin), the backup has never been tested and there is no record of who accessed the database (audit log). In an inquiry by the Authority, or after a leak, it is reality that gets examined.
That is why the business’s IT company needs to know the regulation in depth, alongside the technology. It needs to know what the data security regulations require at each level, adapt permissions, logging and backup to them, and be able to show what was done and when. The National Cyber Directorate guidance and the ISO 27001 standard provide a recognized framework that helps do this systematically.
Summary
- Amendment 13 has been in force since August 2025, and it gives the Privacy Protection Authority broad enforcement powers and the power to impose administrative fines.
- Narrowing the registration requirement does not cancel the security obligations. They apply to every database.
- Certain organizations must appoint a privacy protection officer.
- In practice, most of the obligations involve IT: permissions, authentication, logging, backup and incident response.
- A practical first step: mapping the information and a gap analysis, together with a legal adviser and an IT company that knows the requirements.