Chapter 14 — Privacy foundations
Lesson map
Lesson 14 published. Map, example, EX040.
flowchart TD
N0["Learning outcomes"]
N1["14.1 Personal data"]
N2["14.2 Minimisation"]
N3["14.3 Breach duties"]
N4["14.4 Encryption effect"]
N5["14.5 Retention"]
N6["Breach response basics"]
N7["Data inventory"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX040"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["14.1 Personal data"]
N2["14.2 Minimisation"]
N3["14.3 Breach duties"]
N4["14.4 Encryption effect"]
N5["14.5 Retention"]
N6["Breach response basics"]
N7["Data inventory"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX040"]
[Learning outcomes]
|
v
[14.1 Personal data]
|
v
[14.2 Minimisation]
|
v
[14.3 Breach duties]
|
v
[14.4 Encryption effect]
|
v
[14.5 Retention]
|
v
[Breach response basics]
|
v
[Data inventory]
|
v
[Worked example] --> [Exercise EX040]
Learning outcomes
You will (1) identify personal data on endpoints; (2) apply data minimisation; (3) understand breach obligations.
14.1 Personal data
Laptops hold tenant names, addresses and support notes. Some notes are sensitive.
Aisha learns this from staff interviews and folder names, not by opening tenant files, which the agreement forbids. Housing officers keep copies of tenancy letters and support notes for visits, and some notes record health or family circumstances. Those sensitive notes are what made the stolen laptop serious, and they decide which laptops are treated as highest risk. Aisha records this as a type of data held, not as a list of tenants, so the breach procedure knows what a lost laptop could contain without anyone opening files.
14.2 Minimisation
Staff should keep tenant data on the file server rather than locally. Less local data means less exposure when a laptop is lost.
Aisha's survey shows that many staff keep local copies "in case the network is slow", so minimisation must make the file server easy to use. Gareth's improved offline sync keeps a managed, encrypted copy that is removed when the file server version changes. Staff no longer need private copies on the desktop, and the copies that remain are known.
14.3 Breach duties
Data protection law requires organisations to assess and often report personal data breaches. The stolen laptop was reported because it was unencrypted.
For the stolen laptop, Bramley's assessment found that tenant names, addresses and support notes could be read by anyone with the disk. That made the loss reportable and led to the letters sent to affected tenants. Aisha records the timeline from the theft to the report, because the breach procedure must make the same decisions faster next time.
14.4 Encryption effect
If a lost laptop is encrypted and the key not compromised, the data are unreadable, which usually changes the breach assessment.
This is why the mock report checks encryption status first: in the mock, the console confirms it within 20 minutes. If the laptop is shown encrypted and its recovery key is held only in the directory, the data protection lead can record a much lower risk. Encryption does not remove the duty to assess the loss, but it changes what the assessment is likely to find.
14.5 Retention
Old local copies are deleted.
Aisha adds a check to the baseline routine for tenant files stored outside the managed sync folder on each laptop. Files older than the retention period are deleted by the owner after Gareth confirms the file server holds the current version. Staff are told before the first clean-up, and the deletion is recorded as a count per laptop, not as file names. After the first clean-up, the weekly check asks one yes or no question: does any laptop hold tenant files outside the managed sync folder?
Breach response basics
When a device is lost, staff report it to Gareth immediately. Gareth checks whether it was encrypted, what data it held and whether it can be wiped remotely. The data protection lead decides whether the regulator must be told. Aisha writes this as a one-page procedure and tests it with a mock report.
During the mock, it takes 20 minutes to confirm encryption status from the management console, which is fast enough for the reporting deadline.
Data inventory
Aisha also helps list which systems hold tenant data, so the procedure can quickly identify what a lost device might contain.
Staff guidance
Guidance tells staff never to email tenant data to personal accounts.
Turning it into a check
Aisha writes a single yes or no question that Gareth can answer each week to show this control is still working, and adds it to the routine.
Project log entry
Privacy also shapes what Gareth may collect. Device reports carry hostnames and user names, so Aisha agrees with Bramley's manager that reports stay inside IT, are kept for ninety days and are summarised as counts whenever they leave the team, for example in board papers or her dissertation appendices.
Worked example
Aisha surveys staff and finds many keep local copies "in case the network is slow". Gareth improves offline sync from the file server so local copies are managed and encrypted.
Synthetic case. Synthetic.
Errors and limits
Privacy controls that ignore staff needs lead to shadow copies.
Exercises
- EX040 — Minimisation. What minimisation step applies to laptops? Rubric: 3 = keep tenant data on server; 2 = partial; 1 = vague; 0 = none.
- EX041 — Encryption effect. How does encryption affect breach assessment? Rubric: 3 = data unreadable, changes assessment; 2 = partial; 1 = vague; 0 = none.
- EX042 — Shadow copies. Why did staff keep local copies? Rubric: 3 = slow network; 2 = partial; 1 = vague; 0 = none.
Synthesis
Reduce personal data on endpoints and protect what remains.
Continue studying — chapter 14 of 40
← Chapter 13 (draft) · Course chapter index · Chapter 15 (draft) →