European Union and EEA

Article 29 Working Party Opinion 2/2017 on Data Processing at Work (WP249)

43 controls. 1 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

43 controls 1 frameworks share controls with it European Union and EEA verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

If you runShared controls
GDPR41measure it →

Every control

CodeControlAlso in
3.1(a)3.1(a) Specified, legitimate purposes and data that are adequate, relevant and not excessive1
3.1(b)3.1(b) Proportionality and subsidiarity, whatever the legal ground, tested before monitoring starts1
3.1(c)3.1(c) Let workers exercise access, rectification, erasure and blocking1
3.1(d)3.1(d) Accurate data kept no longer than needed, with a set retention period1
3.1(e)3.1(e) Security of monitoring data and staff awareness of data protection duties1
3.1.1(a)3.1.1(a) Consent is not the legal ground for most processing at work; default settings are not consent1
3.1.1(b)3.1.1(b) Contract and legal obligation as grounds, with workers fully informed of legally required processing1
3.1.1(c)3.1.1(c) Legitimate interest: a legitimate purpose, a necessary and least intrusive method, a demonstrated balance1
3.1.1(d)3.1.1(d) Limits on monitoring: places, data and time1
3.1.23.1.2 Tell workers that monitoring exists, why, and what else fairness requires1
3.1.33.1.3 No decision based solely on automated evaluation of work performance without a permitted ground1
3.2.13.2.1 Data protection by design and default in monitoring devices and tools1
3.2.23.2.2 Data protection impact assessment for high-risk monitoring and prior consultation if residual risk stays high1
44 No incompatible further use of monitoring data1
5.1(a)5.1(a) Recruitment: social media and public data only with a legal ground, when relevant to the job, and with prior notice1
5.1(b)5.1(b) Recruitment data deleted once no offer is made or it is declined1
5.2(a)5.2(a) No generalised screening of employees' social media during employment1
5.2(b)5.2(b) No demand for access to what employees or applicants share on social networks1
5.2(c)5.2(c) Employees keep a private profile; no compulsory employer-provided profile1
5.3(a)5.3(a) Network and TLS inspection tuned to prevent permanent logging of employee activity1
5.3(b)5.3(b) Exclude sensitive traffic from inspection and tell employees what is monitored1
5.3(c)5.3(c) Policy on who may access suspicious log data and when, reviewed at least annually1
5.3(d)5.3(d) Acceptable use and privacy policies implemented and communicated before monitoring1
5.3(e)5.3(e) Involve a representative sample of employees, and the works council where the law requires it1
5.3(f)5.3(f) Data loss prevention: transparent rules and a warning before an email is blocked1
5.3(g)5.3(g) Private spaces in employer-provided online applications1
5.3(h)5.3(h) Prefer prevention to detection: block rather than monitor1
5.4.15.4.1 Home and remote working: no keystroke, mouse, screen or webcam capture1
5.4.2(a)5.4.2(a) Bring your own device: separate private from business use and keep out of private areas1
5.4.2(b)5.4.2(b) Bring your own device: secure the employer's data, weigh monitoring during personal use, or bar private use1
5.4.35.4.3 Mobile device management: DPIA first, a specified purpose, tracking held back until a device is lost1
5.4.45.4.4 Wearables: health and activity data stay with the employee1
5.55.5 Time and attendance and access control: informed, necessary, and not reused for performance evaluation1
5.65.6 Video monitoring: no video analytics of expressions or movements, no facial recognition1
5.7(a)5.7(a) Vehicle tracking: necessary, proportionate, with a private-use opt-out and no evaluation of drivers1
5.7(b)5.7(b) Tell drivers a tracker is fitted and that movements, and possibly driving behaviour, are recorded; notice in the vehicle1
5.7(c)5.7(c) No location monitoring outside agreed working hours, save a proportionate theft safeguard1
5.7.15.7.1 Event data recorders and in-cab cameras: only where necessary and proportionate; no continuous recording of drivers1
5.85.8 Disclosure of employee data to customers only where proportionate1
5.95.9 International transfers of HR and monitoring data: adequacy preferred, minimum data, limited group access1
6.16.1 Owning the equipment does not remove employees' secrecy of communications; location tracking only where strictly necessary1
CONTEXTSections 2 to 4: why the Opinion was needed, the legal framework and the risks0
OPINIONOpinion 2/2017 (WP249): what it is and its status0

Tell me when Article 29 Working Party Opinion 2/2017 on Data Processing at Work (WP249) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for Article 29 Working Party Opinion 2/2017 on Data Processing at Work (WP249), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition