This guide is general information, not legal advice. Check how the law applies to your business with a lawyer or a privacy consultant.

Amendment 13 to Israel’s Protection of Privacy Law took effect on 14 August 2025. For most Israeli businesses the biggest change is not any single new clause. It is that the law now has teeth: the Privacy Protection Authority can impose financial sanctions itself, without going to court.

If your business holds data about customers, patients or employees, the law applies to you, whatever your size. This guide explains what changed, which duties existed before the amendment, and what to do this month.

What Amendment 13 changed

1. Enforcement powers and administrative fines

The Privacy Protection Authority has moved from a body focused on registration and oversight to an enforcement authority. It can impose administrative fines for breaches of the law and of the data security regulations. According to law firm analyses, amounts depend on the type of breach and on the number of people in the database, and for large or sensitive databases they can reach millions of shekels. According to reports, the Authority has already started imposing them.

2. Broader definitions

The amendment updated the definitions of “personal information” and of sensitive data, now called “information of special sensitivity”. The category includes, among other things, medical, genetic and biometric data. In practice, more businesses hold sensitive data than they think. Clinics, private practices, accounting firms and insurance agencies almost always do.

3. Less registration, same duties

The duty to register databases was narrowed and now applies mainly to public bodies, data brokers and large databases of sensitive data. That does not mean the duties went away. An exemption from registration is not an exemption from data security. Anyone who holds a database must comply with the regulations.

4. A privacy protection officer

Some organizations must now appoint a privacy protection officer. The duty applies mainly to public bodies, data brokers, and businesses whose core activity involves processing sensitive data at scale or systematically monitoring people. Most small businesses won’t need one, but it is worth checking.

What did not change, and matters most: the data security regulations

The Protection of Privacy (Data Security) Regulations of 2017 have been in force for years. They set out what you actually have to do to secure a database. What changed is that someone now enforces them.

The regulations sort databases into three security levels. The higher the level, the more duties apply:

Security level Roughly who it applies to Example duties
Basic Most databases without sensitive data Database definition document, security procedure, system mapping, access control, staff training
Medium Databases with sensitive data, and those of public bodies and data brokers Everything in Basic, plus periodic audits, incident logging and reporting severe security incidents to the Authority
High Medium-level databases that are especially large (many people or many authorized users) Everything in Medium, plus periodic risk assessments and penetration tests

The exact level depends on details in the regulations, so treat this table as orientation, not a substitute for checking.

Duties worth knowing in particular:

  • System mapping. You need to know which systems hold the data and how they connect to the network and the internet, and keep that map current when things change.
  • Severe security incidents. For medium and high-level databases, such an incident must be reported to the Authority immediately.
  • Outside suppliers. When a supplier (an IT provider, software vendor or cloud service) gets access to the database, you need an agreement that sets out its security duties, and you need to check it meets them.
  • Documentation. Keep records of actions, checks and incidents, so you can show what was done.

Where small businesses fall short

In most small businesses the problem isn’t unwillingness. It’s that nobody knows exactly what is exposed. A few scenarios that keep repeating:

  • A forgotten server. A staging copy of the website, an old online shop, or a system a supplier set up years ago, still connected to the internet and never updated.
  • Open remote access. During remote-work periods, remote desktop (RDP) connections or admin panels were often opened straight to the internet, and left that way.
  • A silent change. The IT provider opens a port to fix a problem, a certificate expires, or a new subdomain goes live. Nobody tells the owner.

Each of these undermines both the system mapping the regulations require and the security itself.

7 practical steps

  1. Map your databases. What data you hold, about whom, how many people, and where it lives (an office server, the cloud, a supplier’s software).
  2. Set a security level for each database. If you hold medical, genetic, biometric or other sensitive data, assume at least Medium and check.
  3. Write a definition document and a security procedure. A short, clear document beats a long template nobody reads.
  4. Map what is exposed to the internet. Not just the main website: every domain, subdomain, server and service. This is where most surprises turn up.
  5. Sort out your suppliers. Check who has access to the data and update agreements to include security duties.
  6. Prepare an incident procedure. Who decides, who is told, and when you report to the Authority.
  7. Check again and again, and document it. Security isn’t a one-off project. Schedule periodic checks and keep a record of what was found and what was fixed.

Where external monitoring helps, and where it doesn’t

Continuous external attack surface monitoring helps mostly with steps 4 and 7. It finds what your business exposes to the internet, alerts you when something changes, and keeps a history of findings and fixes. That is what lets you show an insurer, a customer or the regulator that problems are found and handled.

External monitoring does not make a business “compliant”. It does not replace database mapping, procedures, access control, supplier agreements, legal advice, or a penetration test where the regulations require one. It gives you a current picture of the part attackers see first.

In short

Amendment 13 did not invent the duty to secure data. It made it a duty that is enforced. A small or medium business doesn’t need a security department to start: it needs to know what it holds, what is exposed, and to document that it is dealing with it.

Further reading: IAPP overview of Amendment 13, IAPP tutorial on the data security regulations, and the Privacy Protection Authority’s official publications on gov.il.