Israel: Dramatic Overhaul Of Israeli Data Security Regulations

Last Updated: 13 April 2017
Article by Haim Ravia and Dotan Hammer

Last week, the Israeli Parliament (the Knesset) promulgated the Protection of Privacy Regulations (Data Security), 5777-2017 (the "Regulations"). This marks the consummation of a legislative process that began in 2010 with the Israeli Law, Information and Technology Authority (ILITA, the Israeli privacy regulator), when the first draft of the Regulations was published for public comment.

The Regulations introduce a far reaching reform to the existing information security regulations which date back to 1986 and have become ill-suited for our technology era. Among other issues, the new Regulations introduce an overarching data breach notification requirement for the first time in Israel. Such requirements are common in many other jurisdictions. In the United States, for instance, breach notifications have led to a wave of class action suits against data handlers whose databases were breached.

When will the Regulations apply?

The Regulations will enter into force in late March 2018, giving data handlers 12 months to prepare.

To whom will the Regulations apply?

The Regulations apply to anyone who owns, manages or maintains a database containing personal data in Israel. All Israeli organizations, companies and public agencies are subject to the Regulations. The Regulations would require these actors to reevaluate their information security protocols and adapt them to the newly promulgated requirements.

Layered approach

The Regulations classify databases into four categories, each subject to an escalating degree of information security requirement:

  1. Databases maintained by individuals;
  2. Databases subject to the basic level of data security requirements;
  3. Databases subject to the intermediate level of data security requirements;
  4. Databases subject to the high level of data security requirements.

    • Databases maintained by individuals. These are databases maintained by an individual, such as a sole proprietor. Also included in this category are databases held by a corporation with a single shareholder, and to which no more than 3 people have access credentials. In either case, databases in this category may not be used to make information available to other parties (for example, databases used to provide direct marketing services to others); the number of data subjects may not exceed 100,000; and the data must not be subject to professional confidentiality obligations under law or codes of ethics (for example, a database maintained by a sole-practitioner attorney).
    • Databases subject to the basic level of data security. These are databases that do not fall within any of the other categories.
    • Databases subject to the intermediate level of data security. A database to which more than 10 people have access credentials and whose purposes include making information available to other parties. Also included in this category are databases maintained by public agencies, or databases that contain special categories of data. These special categories of data include, among others, medical or health information, genetic or biometric data, and information about an individual's political opinions, faith, religious beliefs or criminal convictions. Special categories of data also extend to information about a person's consumption habits that may be indicative of the abovementioned types of data. Additionally, special categories of data cover financial information about a person's financial obligations, solvency or financial status.
    • Databases subject to the high level of data security. Databases whose purposes include making information available to other parties, and in which either the number of data subjects are 100,000 or more or to which more than 100 people have access credentials. This category also includes databases with special categories of data and in which either the number of data subjects are 100,000 or more or to which more than 100 people have access credentials.

The triggering criteria relating to one hundred or more users with access credentials appears to capture many databases that will be subject to the highest level of data security requirements, if they include special categories of data. Since financial information is a special category of data, we anticipate that a growing number of databases will fall within this category.

Requirements applicable to all databases except those held by individuals

  • Drafting a database specification document. Database owners will be required to draft a specification document detailing, among other things, a general description of data collection and processing activities, description of the purposes of the database, details on the types of data processed, information about cross-border data transfers, and the identity of the database manager, its data security officer and its holders (which are defined as those who regularly possess a copy of the database and are entitled to use it). The specification must also include information about processing activities conducted by other processors and details on the primary data security risks and mitigating them.
  • Physical security. The database's computer systems shall be kept in a secured location safeguarded against unauthorized access.
  • Data security officer. The Protection of Privacy Law, 5741-1981 ("PPL") requires public agencies, financial institutions and companies maintaining five or more database to appoint a data security officer. In an effort to ensure the officer's independence, the Regulations require that the officer be directly subordinate to the database manager, or to the manager of the entity that owns or holds the database. The Regulations prohibit the officer from being in a position that raises a conflict of interests. They require the officer to establish data security protocols and an ongoing plan to review compliance with the Regulations. The officer must present findings from the review to the database manager and its supervisor.
  • Data security protocols. These protocols shall bind all employees and shall address, among other issues, instructions on physical and environmental security of the database's premises, administration and use of portable devices, access credentials, instructions applicable to those with access credentials, measures used to safeguard the database's computer systems and risks to which the database is exposed. The protocols shall also include a layered security incident response plan varying in accordance with the incident's severity and the database's degree of sensitivity.
  • Mapping the database's computer systems. A database owner shall compile an updated list of components and devices that comprise the database's computer systems. The list shall include hardware and software components detailed in the Regulations and a description of the architecture of the systems in which the database is installed.
  • Access credentials, authentication and user administration. A database owner shall employ in database-related positions only workers with an appropriate level of clearance in relation to the database's degree of sensitivity. The owner must maintain a list of those with access credentials and must take measures to ensure that access credentials are assigned in accordance with each user's duties and only to the extent necessary for them to perform their work.
  • Documenting information security incidents. Database owners shall maintain documentation for each incident that raises suspicion of a data breach. Automated logging tools shall be used to the greatest extent possible.
  • Portable devices. Restrictions shall be placed on using portable devices with database-related computer systems, in accordance with the database's degree of sensitivity. These include smartphones, laptops and memory sticks.
  • Segregation of systems. To the extent possible, database owners shall segregate database-related computer systems from other computer systems.
  • Communication security. To the extent that database-related computer systems are connected to the Internet, appropriate security measures shall be implemented to safeguard against unauthorized access and malware. Transmission of personal data over the Internet must be encrypted. Remote access to the database by employees shall be authenticated.
  • Outsourcing. Engaging an outsourced data processing provider requires pre-engagement due-diligence review of the risks entailed in the engagement. The contractual engagement shall address issues such as the purposes for which the data will be used, the type of data processing to be performed, the period of engagement and return of the data upon conclusion of the engagement.

Requirements applicable to databases subject to the basic level of data security

In addition to the above requirements applicable to all databases, the Regulations introduce the following requirements applicable to databases subject to the basic level of security:

  • Annual reviews. Database owners shall review the security protocol annually to determine whether updates are needed.
  • Training. Before granting access privileges or after changing the scope of access privileges, database owners shall provide training to users with access credentials with respect to the security protocols and security requirements under the PPL and the Regulations.
  • Recordkeeping. Information about compliance with the Regulations, including documentation of security incidents, information about communication security, access privileges and authentication measures, shall be retained for 24 months.

Requirements applicable to databases subject to the intermediate level of data security

The Regulations introduce additional requirements applicable to databases subject to the intermediate level of security. For databases subject to this intermediate level, the following requirements apply in addition to the requirements applicable to all databases and to those applicable under the basic level.

  • Physical and environmental security. Access to the database's premises shall be monitored. Equipment brought in or taken out of the database's premises shall also be monitored. These will be used in the event of a security breach.
  • Extended security protocol. The security protocol shall cover, among other issues, user authentication measures applicable to the database, backup procedures, access controls and periodic audits.
  • Authentication. Users with access privileges shall be authenticated with physical devices such as smart cards. A protocol shall be established for means of identification, frequency of password change and response to errors in access control.
  • Monitoring access. An automated mechanism for monitoring access to the database shall be established. The logs shall be maintained for at least two years.
  • Periodic audits. Either an internal or external audit shall be performed at least once in 24 months. The audit shall include a report addressing the security measures' compliance with the security protocol and identification of deficiencies and proposals for remediating them. The report shall be reviewed and assessment shall be made of the need to update the database's specification document and security protocols.
  • Backup and recovery. A backup and recovery plan shall be established.
  • Security incidents. Security incidents shall be reviewed at least once a year and an assessment shall be made of the need to update security protocols.
  • Data breach notifications. Prompt notification shall be provided to the privacy regulator (ILITA) regarding any severe data breach in which a material part of the database was access or used without authorization, or in the course exceeding authorized access, or where the database's integrity was compromised. A typical incident of this kind is an unauthorized intrusion into the database and theft of data therefrom. The regulator is authorized to order the database owner to notify all affected data subjects. The Regulations do not prescribe any sanctions for violating the breach notification requirement.

Requirements applicable to databases subject to the high level of data security

The Regulations introduce additional requirements applicable to databases subject to the high level of security. For databases subject to this level, the following requirements apply in addition to the requirements applicable to all databases and those applicable under the basic and intermediate level.

  • Risk assessment. The database owner shall perform an assessment of risks once every 18 months, using a qualified professional, in order to identify and review security risks and deficiencies. Database owners are required to remedy the deficiencies identified and update protocols accordingly. Risk assessment can also be leveraged to satisfy the requirement for periodic audits.
  • Penetration tests. The database's computer systems shall be subjected to penetration tests once in 18 months, in order to evaluate their robustness in the face of internal and external risks.
  • Security incidents. Security incidents shall be reviewed at least once every calendar quarter and an assessment shall be made of the need to update security protocols.
  • Data breach notifications. At this high level of data security, the breach notification requirement applies to any severe data breach in which any portion of the database was breached (not just a material part).

Requirements applicable to databases held by individuals

The requirements for these databases are more lenient. They consist of the following: drafting a database specification document; physical security; access credentials, authentication and user administration; documenting information security incidents; restrictions on using portable devices; segregation of systems; and communication security.

Take away

The potential ramifications of the Regulations are far reaching from legal, technological and business perspectives, for virtually anyone in Israel that handles personal data. They warrant preparation well in advance of their effective date, in areas such internal business protocols, training, technology procurement and outsourcing. They also raise complex questions on topics such as the use of cloud storage services where the cloud user's control over security measures may be more limited.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
Some comments from our readers…
“The articles are extremely timely and highly applicable”
“I often find critical information not available elsewhere”
“As in-house counsel, Mondaq’s service is of great value”

Mondaq Advice Centre (MACs)
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.