Chapter 13 — Security governance, risk and compliance: troubleshooting
Lesson map
Lesson 13 published. Map, example, EX049.
flowchart TD
N0["Learning outcomes"]
N1["13.1 The problem"]
N2["13.2 Testing hypotheses"]
N3["13.3 Fixing the cause"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX049"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["13.1 The problem"]
N2["13.2 Testing hypotheses"]
N3["13.3 Fixing the cause"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX049"]
[Learning outcomes]
|
v
[13.1 The problem]
|
v
[13.2 Testing hypotheses]
|
v
[13.3 Fixing the cause]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX049]
Learning outcomes
You will (1) troubleshoot a control that produces wrong results; (2) use evidence to test hypotheses; (3) fix causes rather than symptoms.
13.1 The problem
Fenwick's weekly backup report shows success, but a restore test from the online shop data fails. Amina is asked to troubleshoot. She lists hypotheses: the backup job covers the wrong folder, the backup is corrupted, or the restore procedure is wrong. She learns that troubleshooting starts with clear hypotheses and evidence for each, rather than changing settings at random and hoping the problem disappears. Each hypothesis points to a different check: the folder list, the backup file integrity or the restore steps.
13.2 Testing hypotheses
Amina checks the backup job's folder list and finds it points to an old location used before the shop platform was upgraded. The new data live elsewhere. The backup reports success because it successfully backs up the old, empty folder. She confirms by restoring the old folder, which works but contains outdated files. She learns that a success message only shows that a job ran, not that it protected the right data. The reliable success messages had hidden the gap since the shop platform upgrade.
13.3 Fixing the cause
Amina updates the folder path, runs a new backup and restores sample files successfully. She also adds a check to the change procedure: when a system is upgraded, backup coverage must be reviewed. She learns that fixing the immediate problem is not enough; the cause was a change process that did not consider backups, so the process must change too. The new check would have caught the old folder path when the shop platform was upgraded. Without the procedure change, the next platform upgrade could silently break backups again.
Worked example
Amina tests three hypotheses, finds the backup pointing to an old folder and fixes both the path and the change process.
Synthetic case. The troubleshooting case is synthetic.
Errors and limits
Hypothesis lists can miss causes. Success reports can mislead.
Exercises
- EX049 — Hypotheses. Name the three hypotheses Amina listed. Rubric: 3 = wrong folder, corrupted backup, wrong restore procedure;; 2 = three;; 1 = vague;; 0 = none.
- EX050 — Misleading success. Why did the backup report success? Rubric: 3 = it backed up an old, empty folder;; 2 = wrong target;; 1 = vague;; 0 = none.
- EX051 — Process fix. What process change did Amina add? Rubric: 3 = review backup coverage after system upgrades;; 2 = change process;; 1 = vague;; 0 = none.
- EX052 — Success meaning. What does a backup success message show? Rubric: 3 = a job ran, not that the right data were protected;; 2 = ran;; 1 = protected;; 0 = none.
Synthesis
Troubleshooting with hypotheses finds root causes, which often lie in processes.
Continue studying — chapter 13 of 18
← Chapter 12 (draft) · Course chapter index · Chapter 14 (draft) →