Chapter 7 — Identity and access foundations | Technologist Human factors and cyber policy

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 7 — Identity and access foundations

Lesson map

Lesson 07 published. Map, example, EX019.

flowchart TD
  N0["Learning outcomes"]
  N1["7.1 Least privilege"]
  N2["7.2 Multi-factor authentication"]
  N3["7.3 Joiners, movers, leavers"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX019"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["7.1 Least privilege"]
  N2["7.2 Multi-factor authentication"]
  N3["7.3 Joiners, movers, leavers"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX019"]

[Learning outcomes]
    |
    v
[7.1 Least privilege]
    |
    v
[7.2 Multi-factor authentication]
    |
    v
[7.3 Joiners, movers, leavers]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX019]

Learning outcomes

You will (1) apply least privilege to clinic roles; (2) introduce multi-factor authentication usably; (3) manage joiners, movers and leavers.

7.1 Least privilege

Lucas reviews access in the practice management system. Every receptionist can export all patient records, though they need only to view and update appointments. He proposes roles: receptionists can manage bookings; clinicians can view clinical notes for their patients; managers can run reports. Exports require manager approval. Least privilege limits what an attacker can do with a stolen receptionist password and reduces the damage of honest mistakes, such as sending a full export to the wrong address. Managers agree the roles in one meeting.

7.2 Multi-factor authentication

Brightwell decides to add a second factor for email and the practice management system. Lucas compares options for receptionists who share desks and may not have work phones. He recommends security keys on badge holders for staff who access patient data, and an app for managers. He plans a pilot at one clinic, measuring login time and support calls, and prepares simple instructions with pictures, because a confusing rollout would create workarounds that undo the benefit. The pilot clinic is chosen by the manager.

7.3 Joiners, movers, leavers

Lucas finds accounts belonging to staff who left months ago. He sets up a simple process: HR notifies IT on the last day, IT disables the account the same day, and managers review access for staff who change roles. He creates a monthly report listing accounts not used for sixty days. Account management depends on routine communication between people, so he designs the process around a checklist that HR already uses. The first report finds nine unused accounts, which are disabled after managers confirm that none are needed.

Worked example

Lucas defines clinic roles, plans a security key pilot and builds a leaver process into HR's existing checklist.

Synthetic case. Roles are synthetic.

Errors and limits

Role changes need updates. Keys can be lost.

Exercises

EX019 — Receptionist export. What change applies to exports? Rubric: 3 = they require manager approval;; 2 = approval;; 1 = vague;; 0 = none.
EX020 — Key choice. Why recommend keys for receptionists? Rubric: 3 = they share desks and may lack work phones;; 2 = no phones;; 1 = vague;; 0 = none.
EX021 — Leaver step. When is a leaver's account disabled? Rubric: 3 = the same day HR notifies IT;; 2 = same day;; 1 = vague;; 0 = none.

Synthesis

Least privilege, usable second factors and routine account management protect patient data.

Continue studying — chapter 07 of 30

← Chapter 06 (draft) · Course chapter index · Chapter 08 (draft) →