Israel's Privacy Security Regulations and AI — What Regulation 13 Requires

Overview — Five Database Security Levels

The Privacy Protection (Information Security) Regulations classify every database into one of five security levels:

• Basic database — Minimum requirements (Regulation 4)
• Medium-level database — Requires a documented security procedure (Regulation 5)
• High-level database — Heightened requirements, including annual reviews (Regulation 13)
• Unique-scope database — More than 5 million data subjects
• Special-type database — Databases held by certain public bodies

Most SaaS, fintech, and healthcare organizations in Israel are classified as high-level databases — which is precisely when Regulation 13 comes into force. For a complete map of database types, see Israeli Database Law and AI.

Core Obligations Under Regulation 13

1. Access Rights Management

Organizations must document who is authorized to access the database, at what permission level (read / write / delete), and on what basis the authorization was granted. In the AI context this means answering:

• Which employees may feed data from the database into an external AI tool?
• Which AI systems hold read access to the database API (for example, a chatbot pulling customer records)?
• Which users may download model outputs that contain personal information?

This list must be updated whenever a role changes, and access must be revoked immediately upon termination of employment.

2. Access Activity Logging (Audit Log)

Every access to a high-level database must be recorded in an immutable log. In the AI context, this requirement has significant practical implications:

• Logging every prompt that includes personal information
• Logging every API call from an AI system to the organizational database
• Logging which data was exported to an external AI tool, when, and by whom

3. Periodic Access Review

Regulation 13 requires a periodic review of authorized users — typically at least once a year. For AI systems, this review must also cover: which service accounts and API keys have access to the database; whether external vendors are still active; and whether DPA agreements with those vendors remain current.

4. Information Security Incident Management

Regulation 13 imposes an obligation to document and handle every information security incident — including unauthorized access attempts, inadvertent exposure, and data loss. AI introduces a new category of incidents that organizations must explicitly define:

• A model "hallucination" that exposed one user's private data to another
• An employee feeding sensitive data into an external AI tool without a DPA in place (unauthorized use)
• A vendor-side model update that degraded output quality or introduced bias

A serious incident (affecting 10,000 or more data subjects, or involving specially sensitive information) must be reported to the Authority within 72 hours of detection. See Amendment 13 to the Privacy Protection Law for the full notification obligation.

5. Periodic Internal Audit

A high-security database must undergo an internal audit at least once every two years. Forward-looking organizations align this audit with their ISO 27001 and ISO 42001 review cycles — significantly reducing duplicated effort. See our guide to integrating the two standards.

Five Immediate Steps for Regulation 13 Compliance in an AI Context