Israel’s National Cyber Portal: free checks for businesses, and how they relate to data security obligations
On 4 November 2026 the Israel National Cyber Directorate launched a portal that brings together free tools for protection against cyberattacks, with a dedicated area for businesses and organizations. Some of the tools relate directly to the obligations that the Privacy Protection (Data Security) Regulations, 5777-2017, impose on every business that is a database controller.
What was launched
The National Cyber Portal (portal.cyber.gov.il) was launched ahead of National Cyber Defense Week, held from 8 to 12 November 2026. The portal is intended for individuals, businesses and organizations, and allows them to check their level of protection, identify threats and receive recommendations. According to the Directorate’s announcement, there has been an increase of about 145% in phishing attacks compared with last year. Since the beginning of 2026 the Directorate has received more than 26,000 reports of suspected attacks, of which more than 5,000 were cyber incidents in organizations’ computer systems.
For the general public the portal offers a tool called “Click Check”: the user pastes a link received in a message or on social media and receives an assessment of how reliable it is. A link identified as malicious is automatically forwarded to the Directorate for takedown. Alongside it there is a game for practicing the identification of phishing messages, tools for checking protections, and alerts on current threats.
Tools for businesses and organizations
The business area is available after registration. According to the Directorate’s announcement it includes:
- Checks of the organization’s digital assets and email servers.
- Checks of suppliers’ level of protection.
- Checks of compatibility with secure digital authentication mechanisms.
- Guides for conducting cyber exercises.
- “Hashtag”, a tool for self-checking suspicious files.
- Targeted alerts on threats relevant to the organization’s activity, and a channel for quick reporting of cyber incidents.
The link to the Data Security Regulations
The Privacy Protection (Data Security) Regulations apply to every database controller, and a business that keeps computerized data on customers, employees or patients is usually a database controller. The Regulations do not refer to any particular tool. Several of the portal’s checks help meet these obligations and document that a check was carried out:
| Portal tool | Obligation under the Regulations | What the tool does not cover |
|---|---|---|
| Supplier checks | Before engaging an external party that is given access to the database, the controller assesses the data security risks involved (Regulation 15(a)(1)). | The agreement with the supplier and supervision of the supplier are required separately. See Supplier agreements under Regulation 15. |
| Asset and email server checks | Ongoing updates of the database systems and avoiding systems whose manufacturer does not support their security, unless a suitable security answer is provided (Regulation 13); database systems may not be connected to the internet without protective measures, and data transferred over a public network is encrypted (Regulation 14). | The check covers only what is exposed from outside. It does not examine access permissions, backups or the security procedure. |
| Secure authentication | Identification and authentication of authorized users (Regulation 9). Remote access requires measures to identify the user, and for a database at the medium or high security level also a physical means under the user’s sole control (Regulation 14(c)). | The check does not determine the database’s security level. |
| Alerts and reporting | Documentation of security incidents and provisions in the security procedure for handling them. In a severe security incident, immediate notice to the Privacy Protection Authority and a report on the steps taken (Regulation 11). | Reporting to the Cyber Directorate does not replace notice to the Privacy Protection Authority. See Security incidents. |
| Exercise guides | For a database at the medium security level, a review at least once a year of security incidents and of the need to update the security procedure; at the high level, once a quarter (Regulation 11(c)). Training for authorized users (Regulation 7). | The Regulations do not require an exercise. An exercise is a way to test whether the procedure works in practice. |
Cyber exercises in an organization
In December 2022 the National Cyber Directorate published a guide to designing and running cyber exercises in an organization. The guide distinguishes between a tabletop exercise, in which participants sit together and explain what they would do in response to an unfolding scenario, and an operational exercise, in which they act in their real systems and with their real tools. A tabletop exercise is inexpensive and simple, carries a low risk to systems, and suits a first exercise and senior management. An operational exercise tests the organization more broadly, but requires long preparation and resources, and carries a risk to systems.
According to the guide, each exercise has a single objective, from which up to three sub-objectives and up to three exercise topics are derived. The scenario should be realistic and difficult enough that some efforts fail, and it is recommended that it include no more than five attacks. Alongside the attacks, the scenario also includes innocent malfunctions and false reports. The exercise is not a test and is not intended to judge the participants, and they should be told so in advance.
Learning starts immediately at the end, with a short initial discussion, and continues with a structured debrief. The debrief filters the information collected into verified facts, and from them into findings relevant to the exercise objective, and combines them into a single picture of what happened. An insight approved by management becomes a lesson, and each lesson is translated into a task with a responsible owner in the work plan, and tested again in the next exercise.
A small business can hold a tabletop exercise of a few hours with the owner, the IT provider and whoever handles customer inquiries. An example scenario: on a Friday afternoon ransomware encrypts the customer management system, and the IT provider cannot be reached. The questions raised are who decides to disconnect the systems from the network, how to find out whether data has left the organization, whether this is a severe security incident under Regulation 11, who notifies the Privacy Protection Authority, and what customers are told. A question that the security procedure does not answer should be added to the procedure.
