◇ OpenCyber Academy
Bachelor's · Chapter 24 · English

Chapter 24 — Privacy and data protection: controls

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 24 — Privacy and data protection: controls

Lesson map

Lesson 24 published. Map, example, EX070.

flowchart TD
  N0["Learning outcomes"]
  N1["24.1 Control set"]
  N2["24.2 Retention schedule"]
  N3["24.3 Training"]
  N4["24.4 Owners"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5
  N5 --> EX["Worked example"]
  EX --> Q["Exercise EX070"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["24.1 Control set"]
  N2["24.2 Retention schedule"]
  N3["24.3 Training"]
  N4["24.4 Owners"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX070"]

[Learning outcomes]
    |
    v
[24.1 Control set]
    |
    v
[24.2 Retention schedule]
    |
    v
[24.3 Training]
    |
    v
[24.4 Owners]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX070]

Learning outcomes

You will (1) design organisational and technical controls for a school trust; (2) link controls to risks; (3) assign ownership.

24.1 Control set

Elena designs a control set for the trust. Organisational controls include the app vetting scheme, staff training, a records retention schedule and the central request inbox. Technical controls include role-based access, single sign-on, encryption, backups and small-cell suppression. She links each control to the risks it reduces and the principles it supports. The link makes it possible to explain to governors why each control exists and what would happen if it were removed. Each control lists its risk. The list fits on two pages.

24.2 Retention schedule

Elena drafts a retention schedule. Pupil records follow education law requirements; safeguarding records are kept according to statutory guidance; photographs for newsletters are kept for the current year; app data are deleted when a pupil leaves. She explains that retention schedules implement storage limitation and reduce what could be exposed in a breach. She notes that some periods are set by law and must be confirmed with the trust's legal adviser. The schedule covers every record type. Legal advice confirms them.

24.3 Training

Training is a control. Elena designs short sessions for different roles: teachers learn about app vetting and misdirected email; office staff learn about identity checks for requests; safeguarding leads learn about secure records. Each session uses school examples and ends with a short quiz. She measures completion and quiz scores. She notes that training changes behaviour only when combined with systems that support the right choices. Quiz scores rose, but incident counts tell a more useful story about behaviour. Incidents matter most.

24.4 Owners

Each control needs an owner. The data protection lead owns the record of processing and request inbox; the IT manager owns access, encryption and backups; head teachers own training completion in their schools. Elena writes a one-page description for each control. Dr. Asante points out that controls without owners decay quietly, and that ownership is the difference between a policy document and a working control. Each owner has a named deputy and a review date in the operations calendar. Reviews are termly.

Worked example

Elena designs organisational and technical controls linked to risks, drafts a retention schedule, creates role-based training with quizzes and assigns owners with one-page descriptions.

Synthetic case. Controls are synthetic.

Errors and limits

Training metrics measure attendance more than behaviour; combine with incident data.

Exercises

Synthesis

Chapter 24 designs controls. Chapter 25 is the first laboratory.

Continue studying — chapter 24 of 40

← Chapter 23 (draft) · Course chapter index · Chapter 25 (draft) →