Legally compliant phishing simulation: Works Constitution Act, GDPR, works council
How phishing simulations become legally compliant: Co-determination under § 87 BetrVG, legal basis under GDPR, and what belongs in the works agreement.

Legally Compliant Phishing Simulation: BetrVG, GDPR, and the Works Council
In recent years, phishing simulations have evolved from a niche method into a standard component. NIS2 Art. 21 Para. 2 (g), the KBV IT Security Guideline pursuant to Section 390 SGB V, and virtually every cyber insurer require documented awareness work—and phishing simulation is the only method that reliably measures its effectiveness.
In Germany, however, implementation regularly fails due to the works council. Not because the works council is against security—but because phishing simulations must be presented cleanly so as not to be perceived as employee monitoring. This article outlines the applicable legal framework, what works agreement is recommended, and how you can objectively refute the most common objections.
The Legal Framework: BetrVG Section 87 Para. 1 No. 6
Phishing simulations reliably trigger co-determination rights in Germany. The legal basis is Section 87 Para. 1 No. 6 of the German Works Constitution Act (BetrVG): "Introduction and use of technical devices designed to monitor the conduct or performance of employees."
The simulation platform meets this criterion because it logs on a per-user basis who clicked, who entered credentials, who opened attachments, and who reported the email. This constitutes individualized performance monitoring within the meaning of the BetrVG. The Federal Labor Court has repeatedly clarified that an actual evaluation is not required to trigger co-determination—the mere technical capability for evaluation is sufficient.
Without a works agreement (or, in the public sector, a service agreement), a phishing simulation is unlawful. The works council can halt the rollout, and any data already collected would be deemed unlawfully obtained.
This is not a mere formality. Tolerating a "let's just do it without one" approach can prove costly for the employer in the event of a dispute.
The GDPR Dimension: What Is Processed and by Whom
Every phishing simulation processes personal data: email addresses, click timestamps, IP addresses, and potentially entered credentials. The GDPR roles must be clearly established.
Typically, you as the employer are the controller within the meaning of the GDPR, while the platform provider acts as a processor. A Data Processing Agreement (DPA) pursuant to Art. 28 GDPR is mandatory. The DPA must govern:
What data is processed
Where it is stored (EU context is critical)
How long it is retained
Who is authorized to access it
Which security measures apply
How deletion and return of data are handled
For US providers or providers with US infrastructure, standard contractual clauses and a documented Transfer Impact Assessment are also required. By 2026, this is no longer a theoretical topic—data protection authorities are actively auditing this.
The legal basis for processing is generally Art. 6 Para. 1 lit. f GDPR (legitimate interest in protecting IT security). Employee consent is not viable in an employment relationship, as voluntariness is typically lacking.
The Works Agreement: Essential Inclusions
A solid works agreement typically consists of eight to twelve sections. From our perspective, the following points are non-negotiable:
Purpose limitation. Explicit: The phishing simulation serves solely to improve security awareness and fulfill statutory obligations (NIS2, Sections 390, 391 SGB V, GDPR). It does not serve to monitor the performance or conduct of individual employees.
Prohibition of use for personnel measures. Clear stipulation: Simulation results may not serve as the basis for employment-related measures—neither for formal warnings, nor terminations, nor promotion decisions. Without this prohibition, the works council would retain its core objection.
Exclusively aggregated analysis. For management reports, data is evaluated solely on an aggregated basis (click rate per department, trend over time). Individual results are not evaluated or forwarded to the employer—only the affected individual can view them.
Retention periods. Raw data (who clicked and when) is deleted after a set deadline—in our case, at the latest 90 days after the campaign ends. For trend analyses, only aggregated statistics without personal reference remain.
Access permissions. Who within the company is permitted to view which evaluations? Our recommendation: Executive management and team leads only see aggregates (teams of 5 or more employees), HR receives no access—individual results are visible to no one in the company except the affected employee themselves.
Transparency toward employees. Once a year, all employees receive an advisory that phishing simulations are being conducted, without prior announcement of individual campaigns. Employees therefore know simulations take place, but not when.
Evaluation clause. The works agreement is evaluated jointly by the employer and the works council every 24 months. Amendments or modifications are adopted by consensus.
Employee rights. Every employee has the right to view their own simulation results and the right to supplementary training without disadvantage.
Five Common Works Council Objections and Objective Responses
"This is employee monitoring."
Fact: The simulation detects whether phishing emails are identified—not whether employees are working productively. The works agreement, featuring an explicit prohibition of use for personnel measures, structurally neutralizes this accusation. The goal is clear: The workforce should learn to identify attacks.
"This only causes anxiety among employees."
Fact: Realistic campaigns free of a blame culture, paired with immediate learning resources (a landing page with explanations rather than a reprimand email), have a de-escalating effect.
"We don't have phishing problems."
Fact: Undetected credential phishing is the most common initial vector for ransomware. The fact that no incidents are known does not mean none exist. Furthermore, starting in 2025–2026, insurers are increasingly demanding documented awareness measures as a prerequisite for coverage.
"External providers will receive our data."
Fact: Data processing pursuant to Art. 28 GDPR, EU data centers, data minimization—only names and corporate email addresses are transmitted. The Data Protection Impact Assessment is an integral part of the project.
"This is too expensive."
Fact: A professionally managed program typically costs only a fraction of what a single ransomware incident incurs in downtime, recovery, and reporting costs.
Executing the First Campaign
Once the works agreement is signed, we recommend the following approach for the initial campaign:
Weeks 1–2: Baseline campaign. Moderately difficult email (e.g., a spoofed Microsoft Teams invite), broad target audience. Purpose: Measure the current baseline, establish a realistic click rate. Typically observed in German hospitals without prior training: 20–35% click rate, 5–10% credential submission.
Weeks 3–4: Initial learning phase. Everyone who clicked automatically receives a brief educational resource (90-second video, 2-question quiz). No one is publicly exposed, and no one is disciplined.
Months 2–3: Differentiated campaigns. Distinct scenarios tailored to each functional role (medical vs. administrative vs. IT), increasing in difficulty.
Month 4: Initial evaluation with the works council. Present trends, derive measures (e.g., targeted training for departments with higher click rates), and secure shared commitment for ongoing rollout.
After 12 months, the click rate should typically fall below 10%, while the report rate (i.e., how many actively report the phishing attempt) should exceed 30%. That represents an awareness culture that holds up under an audit and before insurers.
Conclusion
In Germany, phishing simulations rarely fail due to technology. They fail due to projects that launch without a sound legal foundation and are consequently halted by the works council—or due to negotiations with the works council that stall because the security team cannot provide precise answers.
A sustainable works agreement is not an obstacle, but an accelerator: It creates trust, clarifies expectations, and enables the long-term runtime that makes awareness work effective.
At Entropy CS, we provide a works agreement template for hospitals and care facilities that serves as an effective starting point for negotiations. In our complimentary Risk Check, a quick look at your works council landscape is included in the discussion—so you know what effort to expect before the project begins.
Are you planning a phishing simulation? Our complimentary Risk Check takes 30 minutes and provides an assessment of regulatory requirements, works council preparations, and the appropriate campaign format.


