Chapter 8 — Human factors and cyber policy: difficult cases
Lesson map
Lesson 08 published. Map, example, EX036.
flowchart TD
N0["Learning outcomes"]
N1["8.1 Repeated clickers"]
N2["8.2 Executives"]
N3["8.3 Whistleblowing and reporting"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX036"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["8.1 Repeated clickers"]
N2["8.2 Executives"]
N3["8.3 Whistleblowing and reporting"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX036"]
[Learning outcomes]
|
v
[8.1 Repeated clickers]
|
v
[8.2 Executives]
|
v
[8.3 Whistleblowing and reporting]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX036]
Learning outcomes
You will (1) handle cases involving repeated clickers, executives and whistleblowing; (2) balance accountability with support; (3) apply consistent principles.
8.1 Repeated clickers
A small number of Calloway staff click simulated emails repeatedly. The old programme sent them to remedial training. Daniel reviews the cases with HR and finds that most work in roles receiving very high volumes of external email, such as claims handling. He proposes support rather than sanction: workload review, extra filtering for their inboxes and phishing-resistant authentication so that a click causes less harm. He notes that labelling people as repeat offenders is likely to reduce their willingness to report mistakes.
8.2 Executives
Senior executives are frequent targets yet often exempt themselves from the programme. Daniel proposes that executives follow the same verification rules, have assistants trained in callback procedures and receive short personal briefings on impersonation of themselves. He explains that attackers impersonate executives precisely because staff hesitate to question them. An executive who publicly welcomes verification calls gives staff permission to check, which strengthens the whole organisation. The CEO agrees to record a short message saying so. Assistants receive the briefing as well.
8.3 Whistleblowing and reporting
A staff member reports that a manager has been asking colleagues to share passwords to cover absences. This is a policy breach but also a symptom of understaffing. Daniel ensures the report is handled confidentially through the whistleblowing route, that the reporter is protected and that the underlying workload issue is raised. He applies consistent principles across cases: protect reporters, look for system causes, apply sanctions only for deliberate harmful acts and keep decisions documented and fair. The manager receives support too.
Worked example
Daniel reframes repeated clicking as a workload and design issue, brings executives under the same rules and handles a password-sharing report through whistleblowing with system fixes.
Synthetic case. Cases are synthetic.
Errors and limits
Support may be seen as leniency. Executive buy-in may fade.
Exercises
- EX036 — Clicker roles. Where did most repeated clickers work? Rubric: 3 = high-volume external email roles such as claims;; 2 = claims;; 1 = vague;; 0 = none.
- EX037 — Clicker support. What support did Daniel propose for repeated clickers? Rubric: 3 = workload review, extra filtering and phishing-resistant authentication;; 2 = support;; 1 = remedial training;; 0 = none.
- EX038 — Executive message. What did the CEO agree to do? Rubric: 3 = record a message welcoming verification calls;; 2 = permission;; 1 = vague;; 0 = none.
- EX039 — Password sharing cause. What underlying issue did the password-sharing report reveal? Rubric: 3 = understaffing;; 2 = workload;; 1 = malice;; 0 = none.
- EX040 — Sanction rule. When do sanctions apply under Daniel's principles? Rubric: 3 = only for deliberate harmful acts;; 2 = deliberate;; 1 = any mistake;; 0 = none.
Synthesis
Difficult cases call for consistent principles that protect reporters and fix system causes.
Continue studying — chapter 08 of 12
← Chapter 07 (draft) · Course chapter index · Chapter 09 (draft) →