Menora Mivtachim fined ILS 256,000: it knew about exposed data on 138 policyholders and reported to the Authority fifteen days later.
A properly appointed DPO took 10% off the fine.
A named Data Protection Officer for your organisation, appointed in writing and working with you every month under Amendment 13 and, where it applies, GDPR.
DPO as a Service (DPOaaS) is a formally appointed, outsourced Data Protection Officer, provided to your organisation as an ongoing service. You get a named DPO on the appointment letter who carries the Amendment 13 duties month after month, without opening an internal position.
We usually start with a short project phase for gap work and database mapping, then move to a monthly retainer. We work alongside your CISO, or bring GRC support if you don't have one. When the organisation needs someone physically in the building, we add on-site days.
Led by Ofir Srusi, DPO (Bar-Ilan University certification). A boutique firm covering privacy counsel, CISO/GRC support and Authority-facing work under one roof.
DPO as a Service (DPOaaS) is an outsourced Data Protection Officer appointment run as a continuing service. An external privacy specialist is formally named as your DPO, reports to management and carries the legal duties of the role: advice, training, compliance monitoring, making sure data subject requests are handled, and acting as contact person with the Privacy Protection Authority.
Both laws that matter to Israeli companies allow this. Section 17B3 of the Privacy Protection Law says the DPO can be someone who isn't an employee of the organisation, and GDPR Article 37(6) allows a DPO to work under a service contract. So when people search for the DPOaaS meaning, the short version is an outside DPO with the full legal role, paid as a service.
Signing the appointment letter takes a day. Most of the work comes after it, and this is what the retainer covers.
Ongoing oversight. We build a plan for checking compliance across your databases, test it against what really happens in the organisation, and report findings and fixes to management. This is the heart of the DPO duties in section 17B2, and it's usually the first thing to disappear when the role exists only on paper.
Records and data mapping. Every database needs a database definition document under regulation 2 of the 2017 Security Regulations, and the DPO has to make sure it exists, together with the security procedure, and that management has approved both. We map the systems, the vendors with access and the data flows, then write or fix those documents. Where GDPR applies we also help you maintain the Article 30 records of processing, a duty that sits with the company as controller or processor. Our guide to the database definition document shows what goes into one.
DPIA. Before a new product, AI feature or major system goes live. The Authority recommends a DPIA, especially before new projects or technologies that involve personal data, and publishes a methodology for it, but Israeli law doesn't require one. Under GDPR Article 35 it's required when processing is likely to result in high risk. You can see how we run one in the DPIA guide.
Work with the Israeli Privacy Protection Authority. By law the DPO is your contact person with the Authority. We're copied on correspondence and attend meetings, and we prepare the answers with you.
Data subject requests. Access, correction and deletion requests, logged and answered on time. The DPO's contact details have to be published, so people will write to us directly.
Breach and incident response. A leaked file, or a vendor writing to say it was breached. We help you work out fast whether it's a severe security incident that has to be reported under the Security Regulations, and we stay with it through notification, communications and the post-mortem. More on our incident response service.
Training. A yearly training plan, with short sessions by role. Managers, HR and the support team each get the parts that apply to them.
Vendors. Questionnaires and processing agreements (DPAs) for suppliers who touch personal data, and transfer checks when data leaves Israel.
Behind the appointment there is a signed professional bench: privacy counsel, CISO/GRC, a DPIA analyst and a PMO. NDAs and conflict-of-interest declarations are ready from day one.
Formal DPO appointment under Amendment 13, in tiers that match your size.
Risk analysis for new products and AI systems that process personal data.
Real-time support, Authority notification when a severe incident requires it, communications, post-mortem.
Mapping, GDPR Article 30-style records where relevant, and database definition documents under the 2017 Regulations.
Vendor questionnaires, processing agreements, transfer impact assessments for cross-border vendors.
Combined CISO and DPO support, ISO 27001/27701 readiness, SOC 2 support. See GRC + privacy.
Ready packet: CV, SLA, conflict declarations for municipalities, CHE, regional clusters. See public tender response.
Start with the workload. A mid-sized company with an HR system, a CRM, a few databases and a list of vendors has real DPO work, but rarely enough to fill the week of a senior privacy specialist who also understands technology. Hiring one means a full senior salary, a long search for a profile that is still hard to find in Israel, and starting over when that person leaves. With DPOaaS you pay for the scope you actually have, and the documents and history stay with the service.
Independence is the second reason, and the law is specific here. The DPO reports directly to the CEO, or to someone who reports directly to the CEO. The DPO also can't hold another role, or report to an officer, in a way that could create a conflict of interest. The Authority's final opinion says the DPO can't hold, or report to, a role that sets policy on processing personal data. It names marketing, customer, finance and CTO roles as frequent conflicts, and says the head of information systems (IT) is conflicted as a rule, along with anyone who reports to them. An outside DPO has no budget or roadmap of their own to defend, so it's easier to raise the awkward point in a management meeting.
Then the CISO question, which comes up in a lot of first calls. Israeli law doesn't ban the CISO from also being the DPO. The Authority's final opinion says the two roles are different in substance, that combining them raises real questions, and that an organisation that does it needs a case-by-case assessment with documented reasoning. It points to three issues: the DPO needs deep knowledge of privacy law, which a security officer doesn't necessarily have; in large organisations the security role alone demands full attention; and the DPO must report to the CEO or someone directly under the CEO, which a CISO often doesn't. Our usual setup is your CISO on security and us on privacy, working from the same risk list. There's a longer comparison in DPO vs CISO.
To be fair to the other side, the Authority's final opinion says there is usually an advantage in a full-time in-house DPO, and that the employment model and scope should be decided for each organisation. Where you process a lot of data across many databases, an internal DPO may be the right call, and we'll tell you. We can also support that person instead of replacing them.
| Topic | DPOaaS | In-house DPO |
|---|---|---|
| Scope and cost | You pay for the scope you actually have. | A full senior salary, and a long search for a profile that is still hard to find in Israel. |
| When someone leaves | The documents and history stay with the service. | You start over when that person leaves. |
| Independence | An outside DPO has no budget or roadmap of their own to defend. | The DPO can't hold another role, or report to an officer, in a way that could create a conflict of interest. The Authority names marketing, customer, finance and CTO roles as frequent conflicts, and says the head of information systems (IT) is conflicted as a rule. |
| Workload | A mid-sized company rarely has enough DPO work to fill the week of a senior privacy specialist. | Where you process a lot of data across many databases, an internal DPO may be the right call. |
| What the Authority says | The employment model and scope should be decided for each organisation. | There is usually an advantage in a full-time in-house DPO. |
Amendment 13 to the Privacy Protection Law came into force on 14 August 2025. Section 17B1 makes a DPO mandatory for four groups:
"Large scale" has no fixed number. The law points to how many people are involved (or their share of a given population), the amount and types of data, how long and how often it's processed, how long it's kept, and the geographic reach. The Authority's final opinion on DPO appointment, published in July 2026, is the document it says it will rely on in enforcement, so read it if you're close to the line.
Outside these groups, appointing a DPO is voluntary. Some organisations appoint one anyway because a customer, a tender or an investor asks for it. Our guide on who must appoint a DPO goes through each category with examples, or tick the boxes in the check below.
GDPR reaches Israeli companies with no EU office when they offer goods or services to people in the EU, or monitor their behaviour there (Article 3(2)). That alone doesn't mean you need a DPO. Article 37(1) requires one only for public authorities, for organisations whose core activities involve regular and systematic monitoring of people on a large scale, and for those whose core activities involve large-scale processing of special categories of data or data about criminal convictions. A B2B SaaS company can be fully under GDPR and still meet none of those tests.
When a DPO is required, Articles 37 to 39 let you use an external one on a service contract, as long as the DPO has expert knowledge, is involved early, gets the resources needed, takes no instructions on how to do the tasks, and reports to the highest management level. The DPO's contact details are published and sent to the supervisory authority.
A separate role often gets mixed up with this. Under Article 27, a company covered by Article 3(2) usually has to appoint an EU representative, established in an EU member state where its data subjects are. The exemption is narrow: it covers processing that is occasional, does not include large-scale processing of special-category or criminal-offence data, and is unlikely to result in a risk to people's rights and freedoms. The representative and the DPO are two different appointments.
Tick what applies. The answer updates from Amendment 13 categories. No form, no email.
Want more depth? The full calculator (2 min) or the who must appoint a DPO guide.
Initial indication only, not a legal opinion.
We don't publish a single price for DPOaaS, because two organisations with the same headcount can need very different amounts of work. These are the things that move it:
Our outsourced DPO packages show how these usually group together, from a small organisation with a few main databases up to a local authority or a healthcare body. After the first call we send a written proposal for your actual scope.
I'd ask these questions before signing with anyone, us included.
Who is actually named? The appointment letter should carry one person's name, and that person should be the one who shows up to your management meetings. Ask what happens when they're on holiday, and what happens if they leave the firm.
Ask to see real output. A redacted quarterly report, a database definition document, a DPIA. If all you're shown is a slide deck, that's probably what you'll get each quarter.
Check the Israeli depth. Many DPO offerings are built on GDPR templates. Amendment 13, the 2017 Security Regulations and the way the Authority works day to day (in Hebrew) are different, and your documents have to match them.
Look for conflicts. A provider that also sells you the security tools, or audits the controls it built for you, is checking its own work. We prepare clients for ISO and SOC 2 audits and leave the audit itself to someone independent.
Ask how they would handle a letter from the Authority arriving tomorrow morning. You'll hear quickly whether they have done it before.
And check the exit. The documents, logs and database map are yours, and they should be handed over cleanly if you move on.
Outsourced DPO work for organisations that process personal data under Amendment 13, across sectors with different pressure points:
Initial mapping of personal-data assets and organisation-specific regulatory needs. 30 minutes, free, no commitment.
Appointment documentation, core policies, SLA for ongoing response. Typically within about 30 days, depending on the organisation's pace.
Audits, employee training, support on incidents and regulatory contact. Quarterly and annual reporting as agreed.
Intro call. Tell us what the organisation does with personal data; we will say whether a DPO appointment is on the table and what a sensible first step looks like.
Book a free 30-minute intro callKibbutz Gevaram Israel
Sun-Thu 09:00-18:00
Hebrew and English
Free 30-minute intro call