Israeli Legislation.com

Privacy Protection (Information Security) Regulations, 5777-2017

תקנות הגנת הפרטיות (אבטחת מידע), תשע"ז-2017

Published: 2017-05-08Consolidated Hebrew text as of 2023-09-18 · Last amended 2021-09-14
Premium
Unofficial English translation — for reference only. It may contain errors or omissions and cannot be relied on as a legal text. Only the Hebrew text published in Reshumot is legally binding.More

This English text was translated from the official Hebrew using a range of translation tools, and it undergoes ongoing checks and updates. It is not a certified translation.

Despite these checks, it may contain errors, omissions, or imprecise renderings of legal terminology and cross-references, and it may not yet reflect the latest amendments. It cannot be relied upon as a legal text.

The Hebrew text as published in Reshumot (ספר החוקים) and on the Knesset website is the sole authoritative and legally binding version. In any discrepancy, the Hebrew text prevails.

This translation is provided for informational purposes only and does not constitute legal advice. For use in legal proceedings, request a certified Expert Legal Opinion.

By virtue of my authority under Section 36 of the Privacy Protection Law, 5741-1981 (hereinafter – the Law or the Privacy Protection Law), and with the approval of the Constitution, Law and Justice Committee of the Knesset, I hereby make these Regulations:

Definitions§

1.

In these Regulations –

"serious security incident" – any of the following:

(1)in a database to which a high level of security applies – an incident in which use was made of information from the database without authorisation or in excess of authorisation, or in which harm was caused to the integrity of the information;
(2)in a database to which a medium level of security applies – an incident in which use was made of a substantial part of the database without authorisation or in excess of authorisation, or in which harm was caused to the integrity of the information in respect of a substantial part of the database;

"authorised person" – an individual who has access to any of the following by virtue of the authorisation of the database owner or the holder:

(1)information from the database;
(2)the database systems;
(3)information or a component required for the purpose of operating the database or for the purpose of accessing it.

Notwithstanding the foregoing, a holder who is not an individual, or an individual who received access by virtue of the authorisation of a holder, shall not be regarded as an authorised person of the database owner;

"portable device" – any of the following:

(1)a computer designed for portable use, including a computer that is wireless terminal equipment as defined in the Wireless Telegraph Ordinance [New Version], 5732-1972;
(2)any other device used for the storage of computer material;

"computer material" and "computer" – as defined in the Computers Law, 5755-1995;

"database managed by an individual" – a database managed by an individual or by a corporation owned by an individual, in which only the individual and at most two additional authorised persons are entitled to make use of it and are able to make use of it, excluding the following databases:

(1)a database whose principal purpose is the collection of information for the purpose of transferring it to another as a course of business, including direct mailing services;
(2)a database containing information about 10,000 persons or more;
(3)a database that includes information in respect of which the database owner is subject to a duty of professional confidentiality by law or by the principles of professional ethics;

"databases to which the basic level of security applies" – databases that are not of the types listed in the First or Second Schedule and are not a database managed by an individual;

"databases to which the medium level of security applies" – databases of the types listed in the First Schedule that are not a database managed by an individual;

"databases to which the high level of security applies" – databases of the types listed in the Second Schedule;

"biometric information" – information used for the identification of a person, being a physiological, unique human characteristic that is amenable to computerised measurement;

"security officer" – as its meaning in Section 17b of the Law;

"database systems" – systems that serve the database and that are of importance from the perspective of information security;

"data subject" – the person about whom information exists in the database;

"Israel National Cyber Directorate" – the Israel National Cyber Directorate whose purpose is the protection of cyberspace, established pursuant to a Government decision and operating in accordance with its decisions;

"public network" – a communications network that also permits use by a person who is not an authorised person.

Database Definition Document§

2.
(a)A database owner shall define, in a database definition document (hereinafter – the database definition document), at least all of the following matters:
(1)a general description of the collection and use of information;
(2)a description of the purposes of the use of the information;
(3)the various types of information contained in the database, having regard to the list of types of information in item 1(3) of the First Schedule;
(4)particulars of the transfer of the database, or a substantial part thereof, outside the borders of the State, or the use of information outside the borders of the State, the purpose of the transfer, the destination country, the manner of transfer and the identity of the transferee;
(5)information processing operations by means of a holder;
(6)the principal risks of harm to information security, and the manner of dealing with them;
(7)the name of the database manager, of the database holder and of the information security officer appointed thereto, if one has been appointed.
(b)A database owner shall update the database definition document whenever a material change is made in the matters listed in sub-regulation (a), and shall examine the need for such an update, due to technological or organisational changes or security incidents as referred to in regulation 11, once a year by 31 December.
(c)A database owner shall examine, once a year, whether the information stored in the database is not greater than that required for the purposes of the database.

Information Security Officer§

3.

Where there is an obligation to appoint an information security officer, or where an information security officer has been appointed for the database, the following provisions shall apply:

(1)a security officer shall be directly subordinate to the database manager or to an active manager of the database owner or the holder, as the case may be, or to another senior office holder who is directly subordinate to the database manager;
(2)the security officer shall prepare an information security procedure and bring it for approval by the database owner;
(3)the security officer shall prepare a plan for ongoing monitoring of compliance with the requirements of these Regulations, shall implement it, and shall notify the database owner and the database manager of the findings;
(4)the security officer shall not fulfil an additional role that may place him in apprehension of a conflict of interests in the performance of his role under these Regulations;
(5)if the database owner has assigned to the security officer additional tasks beyond the duties enumerated in paragraphs (2) and (3), for the purpose of implementing these Regulations, the database owner shall define them clearly;
(6)the database owner shall allocate to the security officer the resources necessary for the performance of his role.

Security Procedure§

4.
(a)A database owner shall establish, in a document, an information security procedure (hereinafter – the security procedure) in accordance with the database definition document and these Regulations, which shall be binding on every authorised person in accordance with the particulars of the procedure to which that person is exposed pursuant to sub-regulation (b).
(b)A database owner shall keep the security procedure such that its particulars are conveyed to authorised persons only to the extent required for the performance of their roles.
(c)The security procedure shall include, inter alia, all of the following:
(1)provisions regarding the physical and environmental security of the database sites as referred to in regulation 6;
(2)access authorisations to the database and to the database systems in accordance with regulation 8;
(3)a description of the measures intended to protect the database systems and the manner of their operation for that purpose;
(4)instructions to persons authorised to access the database and the database systems for the purpose of protecting the information in the database;
(5)the risks to which the information in the database is exposed in the framework of the ongoing activity of the database owner, including those arising from the structure of the database systems as detailed in regulation 5(a), the manner of determining such risks, and the manner of dealing with them, including by means of accepted encryption mechanisms for the protection of information stored in the database or in the database systems;
(6)the manner of dealing with information security incidents as referred to in regulation 11, according to the severity of the incident and the degree of sensitivity of the information;
(7)provisions regarding the management and use of portable devices as referred to in regulation 12.
(d)In a database to which the medium or high level of security applies, the security procedure shall include, in addition to that stated in sub-regulation (c), reference to all of the following as well:
(1)the identification and authentication measures for access to the database and to the database systems, in accordance with regulation 9;
(2)the manner of monitoring the use of the database, including documentation of access to the database systems as referred to in regulation 10;
(3)provisions regarding the conduct of periodic audits to verify the existence and proper functioning of the security measures under the security procedure and under these Regulations as referred to in regulation 16;
(4)provisions regarding the backup of the data referred to in regulation 18(a)(1);
(5)provisions regarding the manner of carrying out development operations in the database and their documentation, including the manner of access by development personnel to the data in the database.
(e)A database owner shall examine, once a year, the need to update the procedure, and without derogating from the foregoing, shall examine whether the procedure needs to be updated in the following cases:
(1)material changes are made to the database systems or to information processing processes;
(2)new technological risks relating to the database systems become known.
(f)An organisation that owns several databases may establish a security procedure as referred to in this regulation, in a single document, in respect of all its databases that are at the same level of security.

Mapping of Database Systems and Conducting a Risk Survey§

5.
(a)A database owner shall maintain an updated document of the structure of the database as well as an updated inventory list of the database systems, including:
(1)infrastructure and hardware systems, types of communication and information security components;
(2)software systems used for the operation, management, maintenance, support, monitoring and security of the database;
(3)software and interfaces used for communication to and from the database systems;
(4)the network diagram within which the database operates, including a description of the connections between the various system components and the physical location of those components;
(5)the date of the last update of the document and of the inventory list.
(b)The updated document of the structure of the database and the inventory list shall be kept such that their particulars are conveyed to authorised persons only to the extent required for the performance of their roles.
(c)In a database to which the high level of security applies, the database owner is responsible for ensuring that a survey is conducted to identify information security risks (hereinafter – risk survey); the database owner shall discuss the results of the risk survey conveyed to him, shall examine the need to update the database definition document or the security procedure in consequence thereof, and shall act to remedy the deficiencies discovered in the framework of the survey, insofar as any were discovered; such a risk survey shall be conducted at least once every eighteen months.
(d)In a database to which the high level of security applies, the database owner is responsible for ensuring that penetration tests are conducted on the database systems to examine their resilience against internal and external risks, at least once every eighteen months; the database owner shall discuss the results of the penetration tests and shall act to remedy the deficiencies discovered, insofar as any were discovered.
(e)An organisation that owns several databases may establish the inventory list referred to in sub-regulation (a) in a single document in respect of all its databases at the same level of security, and may also fulfil the obligations prescribed in sub-regulations (c) and (d) by means of a single risk survey or penetration test, as the case may be, in respect of all its databases at the same level of security.

Physical and Environmental Security§

6.
(a)A database owner shall ensure that the systems listed in regulation 5(a)(1) are kept in a protected location that prevents unauthorised penetration and entry, and that is commensurate with the nature of the database's activity and the sensitivity of the information therein.
(b)A database owner to which the medium or high level of security applies shall take measures to monitor and document entry into and exit from the sites in which the systems listed in regulation 5(a)(1) are located, and the bringing in and taking out of equipment to and from the database systems.

Information Security in Personnel Management§

7.
(a)A database owner shall not grant access to information held in the database, nor change the scope of an authorisation granted, unless reasonable measures, accepted in employee screening and placement procedures, have been taken to ascertain that there is no concern that the authorised person is unsuitable to receive access to the information held in the database; such measures shall be taken having regard to the sensitivity of the information in the database and the scope of the access authorisations for the role for which the person concerned is intended, as referred to in regulation 8.
(b)Before receiving access to information from the database, or before a change in the scope of their authorisations, a database owner shall conduct training for authorised persons on the subject of the obligations under the Law and these Regulations, and shall provide them with information about their obligations under the Law and the security procedure.
(c)In a database to which the medium or high level of security applies, the database owner shall conduct periodic training for its authorised persons regarding the database definition document, the security procedure and the information security provisions under the Law and under these Regulations, to the extent required for the performance of their roles, and regarding the obligations of authorised persons thereunder; such training shall be conducted at least once every two years, and in respect of the authorisation of an authorised person to a new role – as soon as possible to the date of commencement of the authorisation.

Management of Access Authorisations§

8.
(a)A database owner shall determine access authorisations of authorised persons to the database and to the database systems, in accordance with role definitions; the access authorisation for each role shall be to the extent required for the performance of the role only.
(b)A database owner shall maintain an updated register of roles, the access authorisations granted to them, and the authorised persons fulfilling those roles (hereinafter – the valid authorisations list).

Identification and Authentication§

9.
(a)A database owner shall take measures that are accepted in the circumstances of the matter and in accordance with the nature and character of the database, in order to verify that access to the database and to the database systems is made only by an authorised person who is permitted to do so under the valid authorisations list.
(b)In a database to which the medium or high level of security applies –
(1)the manner of identification shall be carried out, as far as possible, on the basis of a physical means under the exclusive control of the authorised person;
(2)the security procedure shall also set out provisions regarding sub-regulation (a), including on the following matters:
(a)the manner of identification; if the manner of identification is based on passwords, the procedure shall also address the strength of the password, the number of failed attempts, and the frequency of password changes, which shall be carried out in accordance with the role of the access authorised person, and in any event for a period not exceeding six months;
(b)automatic disconnection after a period of inactivity;
(c)the manner of handling faults related to identity authentication.
(c)A database owner shall ensure the revocation of the authorisations of an authorised person who has concluded his role and, insofar as possible, the change of passwords to the database and to the database systems that the authorised person may have known, immediately upon the conclusion of the authorised person's role.

Monitoring and Documentation of Access§

10.
(a)In the systems of a database to which the medium or high level of security applies, an automatic documentation mechanism shall be maintained that will enable auditing of access to the database systems (in this regulation – the monitoring mechanism), including the following data: the identity of the user, the date and time of the access attempt, the system component to which the access attempt was made, the type of access, its scope, and whether the access was approved or declined.
(b)The monitoring mechanism shall, to the best of its ability, not permit the cancellation or modification of its operation; the monitoring mechanism shall detect changes or cancellations in its operation and shall distribute alerts to those responsible.
(c)A database owner shall establish a routine inspection procedure for the documentation data of the monitoring mechanism, and shall produce a report of the problems discovered and the steps taken in consequence thereof.
(d)The documentation data of the monitoring mechanism shall be retained for at least 24 months.
(e)A database owner shall inform the authorised persons in the database of the existence of the monitoring mechanism for the database systems.

Documentation of Security Incidents§

11.
(a)A database owner is responsible for documenting every case in which an incident is discovered that raises a concern of harm to the integrity of the information, of use thereof without authorisation, or of excess of authorisation (hereinafter – security incidents); as far as possible, such documentation shall be based on automatic recording.
(b)In the security procedure, a database owner shall also set out provisions regarding the manner of dealing with information security incidents, according to the severity of the incident and the degree of sensitivity of the information, including regarding the revocation of authorisations and other immediate steps required, as well as regarding reporting to the database owner on security incidents and on actions taken in consequence thereof.
(c)In a database to which the medium level of security applies, the database owner shall hold a discussion at least once a year on security incidents and shall examine the need to update the security procedure; in a database to which the high level of security applies, such a discussion shall be held at least once a quarter.
(d)If a serious security incident has occurred –
(1)the database owner shall notify the Registrar thereof immediately, and shall also report to the Registrar on the steps taken in consequence of the incident;
(2)the Registrar may instruct the database owner, except for a database owner from among those enumerated in Section 13(e) of the Law, after consulting the head of the Israel National Cyber Directorate, to notify a data subject who may be harmed by the incident of the security incident.

Portable Devices§

12.

The database owner shall restrict or prevent the possibility of connecting portable devices to the database systems in a manner commensurate with the level of information security applicable to the database, the sensitivity of the information, the particular risks to the database systems or to the information arising from the connection of the portable device, and the existence of appropriate protective measures against such risks; a database owner who permits the use of information from the database on a portable device or the copying thereof to a portable device shall take protective measures having regard to the particular risks associated with the use of a portable device in that database; for this purpose, the use of accepted encryption methods shall be regarded as the taking of reasonable measures for the protection of information copied to the portable device.

Secure and Updated Management of Database Systems§

13.
(a)A database owner shall ensure the proper management and operation of the database systems, in accordance with accepted practice in the operation of such systems.
(b)A database owner shall separate, to the extent and degree reasonably possible, between the database systems from which access to information is possible, and other computing systems used by the database owner.
(c)A database owner shall ensure that ongoing updates of the database systems are carried out, including computer material required for their operation; systems in respect of which the manufacturer does not provide security support shall not be used unless an appropriate security response has been provided.

Communication Security§

14.
(a)A database owner shall not connect the database systems to the internet or to another public network without installing appropriate protective measures against unauthorised penetration or against software capable of causing damage or disruption to a computer or to computer material.
(b)The transfer of information from the database via a public network or the internet shall be carried out using accepted encryption methods.
(c)In a database that can be accessed remotely by means of the internet or another public network, use shall be made, in addition to the security measures referred to in sub-regulations (a) and (b), of measures intended to identify the communicating party and to authenticate his authorisation to carry out the remote activity and its scope; for the purpose of access by an authorised person to a database at the medium or high level of security, a physical means under the exclusive control of the authorised person shall be used.

Outsourcing§

15.
(a)A database owner who enters into a contract with an external party for the purpose of receiving a service that involves granting access to the database –
(1)shall, before concluding the contract with that particular external party, examine the information security risks involved in the contract;
(2)shall stipulate expressly in the agreement with the external party (in this regulation – the agreement) all of the following, having regard to the risks under paragraph (1):
(a)the information that the external party is entitled to process and the permitted purposes of use thereof for the purposes of the contract;
(b)the database systems that the external party is entitled to access;
(c)the type of processing or operation that the external party is entitled to carry out;
(d)the duration of the contract, the manner of returning the information to the owner upon termination of the contract, its destruction from the possession of the external party and reporting thereof to the database owner;
(e)the manner of implementing the information security obligations that the holder is subject to under these Regulations, as well as additional instructions regarding information security measures determined by the database owner, if any were determined;
(f)the obligation of the external party to have its authorised persons sign an undertaking to maintain the confidentiality of the information, to use the information only in accordance with what is stated in the agreement, and to implement the security measures prescribed in the agreement as referred to in sub-paragraph (e);
(g)where the database owner has permitted the external party to provide the service by means of an additional party – the obligation of the external party to include in its agreement with the additional party all the matters set out in this regulation;
(h)the obligation of the external party to report, at least once a year, to the database owner on the manner of performance of its obligations under these Regulations and the agreement, and to notify the database owner in the event of a security incident;
(3)shall specify in the security procedure of the database the matters listed in paragraph (2)(a) to (e) as well, and shall make explicit reference therein to the agreement with the external party and to its security procedure;
(4)shall take control and supervision measures to ensure the compliance of the external party with the provisions of the agreement and with the provisions of these Regulations, to the extent required having regard to the risks referred to in paragraph (1).
(b)An organisation that is a database owner of several databases, which enters into a contract with an external party for the purpose of providing a service that involves access thereto by the external party, may fulfil the requirements of sub-regulation (a)(2) in a single agreement in respect of all the databases, provided that they are at the same security level.
(c)This regulation shall not apply to a contract of a database owner with an individual.

Periodic audits§

16.
(a)In respect of a database to which the medium or high level of security applies, the database owner is responsible for ensuring that an internal or external audit is conducted at least once every 24 months, by a party with appropriate training in information security auditing who is not the security officer of the database, in order to verify compliance with the provisions of these Regulations.
(b)In the audit report, the auditor shall report on the conformity of the security measures with the security procedure and with these Regulations, shall identify deficiencies and shall propose measures required for remedying the situation.
(c)The database owner shall discuss the audit reports transmitted to it and shall examine the need to update the database definition document or the security procedure in consequence thereof.
(d)A database owner to whom the high level of security applies may fulfil the obligation prescribed in this regulation within the framework of conducting a risk survey that meets the requirements of sub-regulation (b).
(e)An organisation that is a database owner of several databases may fulfil the obligation prescribed in this regulation within the framework of a single audit in respect of all the databases in its possession that are at the same security level.

Retention of security data§

17.
(a)A database owner shall retain the data accumulated in the course of implementing the provisions of regulations 6(b), 8 to 11, 14, 15(a)(4) and 16, to the extent that these Regulations apply to it, in a secure manner for a period of 24 months.
(b)In respect of a database to which the medium or high level of security applies, the database owner shall back up the data retained as referred to in sub-regulation (a), in a manner that ensures that it is possible, at any time, to restore the said data to its original state.

Backup and recovery of security data§

18.
(a)In respect of a database to which the medium or high level of security applies, the database owner shall set out in a document –
(1)procedures for performing backup as referred to in regulation 17(b), on a periodic routine basis;
(2)procedures for ensuring the recovery of data as referred to in regulation 17(b), provided that the performance of the recovery shall be with the approval of the database manager;
(3)that within the framework of documenting security incidents as referred to in regulation 11, the data recovery procedures shall also be documented, including the identity of the person who performed the recovery procedures and the details of the information that was recovered.
(b)In respect of a database to which the high level of security applies, the database owner is responsible for ensuring that a backup copy of the data referred to in regulation (a)(1) and of the procedures referred to in sub-regulation (a)(2) is retained, in a manner that ensures the integrity of the information and the possibility of recovering the information in the event of loss or destruction.

Obligations of database owner applying to database manager and holder, and documentation of performance of an act§

19.
(a)The obligations imposed by these Regulations on a database owner shall also apply to the database manager, and – except for the obligations prescribed in regulations 2 and 15(a) – they shall also apply to the database holder, with the necessary modifications and as the case may be.
(b)A person on whom an obligation or responsibility to perform an act that is not the creation of a document is imposed by these Regulations is required to document in a reasonable manner the manner of performance of the act as the case may be; the Registrar may give instructions regarding the manner of such documentation.

Powers of the Registrar§

20.
(a)
(1)The Registrar may, if the Registrar considers that there are reasons justifying it, exempt a particular database from information security obligations under these Regulations, or apply to a particular database obligations under these Regulations, all or some of them, according to the circumstances of the matter, having regard, inter alia, to the size of the database, the type of information contained therein, the scope of activity of the database or the number of authorised persons in it.
(2)An exemption from obligations or the application of obligations under paragraph (1) shall be effected by written notice to the database owner; in such notice the Registrar shall determine the date of commencement of the exemption or the application, as the case may be, and may determine different dates in respect of different regulations.
(b)The Registrar may instruct that a person who complies with the provisions of a guidance document on information security or with the instructions of a competent authority on information security that apply to that person shall be regarded as complying with the provisions of these Regulations, all or some of them, if the Registrar is satisfied that compliance with the provisions of the guidance document on information security or with the instructions of the competent authority, as the case may be, in the manner instructed under these Regulations, ensures the level of security prescribed in these Regulations in respect of that database; for this purpose –

"competent authority" – a public body empowered by law to issue instructions on information security;

"guidance document on information security" – an official standard, an Israeli standard or an international standard as their meaning in the Standards Law, 5713-1953, or a reference document that the Registrar has approved for this purpose.

Application and limitations on application§

21.

In these Regulations –

(1)to databases to which the high level of security applies – regulations 1 to 20 shall apply;
(2)to databases to which the medium level of security applies – regulations 1 to 4, 5(a), (b) and (e), 6 to 15, 16(a), (b), (c) and (e), 17, 18(a), 19 and 20 shall apply;
(3)to databases to which the basic level of security applies – regulations 1 to 3, 4(a), (b), (c), (e) and (f), 5(a), (b) and (e), 6(a), 7(a) and (b), 8, 9(a) and (c), 11(a) and (b), 12 to 15, 17, 19 and 20 shall apply;
(4)to a database managed by an individual – regulations 1, 2, 6(a), 9(a), 11(a), 12 to 14 and 20 shall apply.

Commencement§

22.

These Regulations shall commence one year from the date of their publication.

Transitional provision§

23.

Notwithstanding the provisions of regulation 7(a), with regard to those who are authorised persons on the date of commencement of these Regulations, a database owner to whom that regulation applies shall examine the degree of their suitability for access to the database by reasonable means customary in employee selection and placement procedures, all having regard to the sensitivity of the information and the type of access authorisation, and shall update the access authorisations accordingly as required.

Repeal§

24.

Regulations 2, 3, 9, 10, 12, 13, 14 and 15 of the Privacy Protection (Conditions for Holding and Maintaining Information and Procedures for the Transfer of Information between Public Bodies) Regulations, 5746-1986 – are repealed.

Relationship to other legislation§

25.

These Regulations shall apply in addition to provisions concerning information security in other legislation, unless there is a conflict between them.

Page 1 of 2

Read the entire law on one page — continuous text, no page breaks, plus formal citations.

RegulationsCivil LawCriminal Law

תקנות הגנת הפרטיות (אבטחת מידע), תשע"ז-2017

Privacy Protection Information Security Regulations 2017

PPIS Regulations

Takkanot Hganat Privatiyut

Israeli data protection regulations

Information security regulations Israel

Data protection law Israel

GDPR equivalent Israel

Israeli privacy law

Cybersecurity regulations Israel

Personal data security regulations