A provider with access to your database: what the agreement must contain under Regulation 15
A software company, cloud provider, bookkeeping firm or technical support company with access to a business’s database is an “external party” under the Israeli Data Security Regulations. Regulation 15 sets out what the database owner must check before the engagement, what the agreement must say, and how the provider is supervised after signing.
When the regulation applies
Regulation 15 of the Privacy Protection (Data Security) Regulations, 5777-2017, applies to a database owner that engages an external party to receive a service involving access to the database. The access need not be active processing: under the Law as amended by Amendment 13, “processing” includes storage, viewing and granting access, so a provider that hosts the database or accesses it for technical support falls within the regulation. The regulation does not apply to an engagement with an individual. An organisation with several databases at the same security level may sign a single agreement with the provider covering all of them.
In the terms of the Law, such a provider is a “holder” and the database owner is the “controller”. On the distinction, see Controller or processor.
Before the engagement
Before engaging a particular provider, the database owner examines the data security risks involved in the engagement. The examination concerns that provider and that service: what data the provider will see, from which systems, by what means of access, and the security level of the database. Its results determine the scope of the provisions in the agreement and the extent of supervision afterwards.
What the agreement contains
Under Regulation 15, the agreement with the external party must expressly set out, having regard to the risks identified:
| Element | Content |
|---|---|
| Data and purposes | The data the provider may process, and the permitted purposes of use for the engagement |
| Systems | The database systems the provider may access |
| Type of processing | The type of processing or action the provider may carry out |
| Term and termination | The term of the engagement, how the data is returned to the owner at the end, its destruction by the provider, and reporting on this |
| Security | How the security obligations applying to the provider under the regulations are implemented, and any further security instructions set by the database owner |
| Provider’s staff | The provider’s duty to have its authorised users sign an undertaking of confidentiality, to use the data only under the agreement and to apply the security measures |
| Subcontractors | Where the owner permits the service to be provided through another party, the provider’s duty to include all these matters in its agreement with that party |
| Reporting | An annual report, at least, from the provider on how it performs its obligations, and notice to the owner of any security incident |
A software provider’s standard terms sometimes include some of these elements, but not all of them, and in particular not the annual report or the prohibition on using subcontractors without permission.
After signing
The database owner sets out in the database’s security procedure the data, systems, type of processing, term and implementation of the security obligations, and refers expressly to the agreement with the provider and to the provider’s own security procedure. It also takes measures to monitor and supervise the provider’s compliance with the agreement and the regulations, to the extent appropriate to the risks. The data accumulated in this supervision is kept securely for 24 months.
Supervision is linked to incident reporting: under Regulation 11, for a database at the medium or high security level, a severe security incident must be reported to the Privacy Protection Authority immediately. The owner can meet this duty only if the provider notifies it of the incident in time, which makes the notice provision in the agreement particularly important.
The provider’s own obligations
Under Regulation 19, the obligations the regulations place on a database owner also apply to the holder, with the necessary changes, except for the duty to prepare a database definitions document (Regulation 2) and the obligations under Regulation 15 itself. The provider therefore needs its own security procedure, access management, incident records and the other requirements according to the database’s security level.
Under Section 8(c) of the Law, no person may process personal data from a database without the controller’s authorisation or beyond it. The Regulation 15 agreement is in practice that authorisation. A provider that exceeds it, for example by using the data to develop its own product, is exposed to an administrative fine, and Section 23NH of the Law sets a penalty of three years’ imprisonment for the offence. A provider whose main business is processing data of special sensitivity on a significant scale may also need to appoint its own privacy protection officer; see Privacy Protection Officer under Amendment 13.
Comparison with Article 28 of the GDPR
Article 28(3) of the GDPR sets out the elements of the contract between a controller and a processor. Most of them are similar to Regulation 15, with some differences:
| Topic | Regulation 15 | GDPR, Article 28 |
|---|---|---|
| Instructions | Data, purposes and type of processing defined in the agreement | Processing only on the controller’s documented instructions |
| Subcontractors | Only with permission, under an agreement covering the same matters | Only with prior written authorisation, with the same obligations |
| Data subject rights | Not expressly provided in the regulation | The processor assists the controller in responding to requests |
| Supervision | Monitoring and supervision measures, and an annual report from the provider | The processor makes information available and allows audits |
| Termination | Return and destruction of the data, and reporting on this | Deletion or return, at the controller’s choice |
A GDPR data processing addendum (DPA) covers much of Regulation 15. It is worth adding what is missing: the annual report, the staff undertakings and the reference to the database’s Israeli security level. Conversely, a good Israeli agreement will also include the provider’s assistance in responding to inspection and correction requests; see Data subject access requests.
