Chapter 8 — Network and communications security: failure modes
Lesson map
Lesson 08 published. Map, example, EX029.
flowchart TD
N0["Learning outcomes"]
N1["8.1 How controls fail"]
N2["8.2 Expiry failures"]
N3["8.3 Silent failures"]
N4["8.4 Workarounds"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5
N5 --> EX["Worked example"]
EX --> Q["Exercise EX029"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["8.1 How controls fail"]
N2["8.2 Expiry failures"]
N3["8.3 Silent failures"]
N4["8.4 Workarounds"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX029"]
[Learning outcomes]
|
v
[8.1 How controls fail]
|
v
[8.2 Expiry failures]
|
v
[8.3 Silent failures]
|
v
[8.4 Workarounds]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX029]
Learning outcomes
You will (1) identify how network controls fail; (2) plan safe failure; (3) prevent workarounds.
8.1 How controls fail
Controls fail through misconfiguration, expiry, hardware faults, overload and human workarounds. Amina lists Castleford's controls and asks how each might fail: the firewall might be misconfigured, a VPN certificate might expire, the log collector's disk might fill, the guest wireless passphrase might be shared widely, and staff might connect an unauthorised device to bypass a block. For each failure she notes how it would be noticed and how harm would be limited. Failures that would go unnoticed get priority. She reviews the table with Rosa.
8.2 Expiry failures
Certificates expire on a set date. If the VPN gateway certificate expires, field officers cannot connect and the help desk is flooded. If a website certificate expires, users see warnings and may learn to click through them. Expiry failures are entirely predictable, yet they are common because nobody tracks dates. Amina adds every certificate to an expiry list with an owner and plans a weekly check that warns sixty days ahead, which turns a predictable failure into routine maintenance. Each owner confirms renewal steps.
8.3 Silent failures
The most dangerous failures are silent. If logging stops, nothing obviously breaks, but evidence disappears. If a backup job fails, nobody notices until a restore is needed. Amina recommends checks that alert on absence: no logs from a device for an hour, no backup completed in twenty-four hours, no configuration export overnight. Monitoring for things that should happen but did not is as important as monitoring for things that should not happen. These checks run automatically and email Rosa when something expected does not happen.
8.4 Workarounds
When controls get in the way, people find ways around them. If field officers find the VPN too slow, they might email files to personal accounts. If a printer stops working after segmentation, someone might move it to the staff network. Amina recommends a simple process for reporting blocked work, fast fixes for genuine needs and periodic checks for devices in the wrong zone. Reducing friction keeps controls in place and keeps people from creating hidden risks. Staff are told why the controls exist and how to ask for changes.
Worked example
Amina's failure table covers eight controls; three silent failures get absence alerts.
Synthetic case. The table is synthetic.
Errors and limits
Assuming a control still works because nothing has complained ignores silent failures.
Exercises
- EX029 — Predictable failure. Why are certificate expiries predictable yet common? Rubric: 3 = dates known but not tracked;; 2 = tracking;; 1 = random;; 0 = none.
- EX030 — Absence alert. Give one absence-based alert. Rubric: 3 = no logs for an hour, no backup in 24h, no export;; 2 = one;; 1 = vague;; 0 = none.
- EX031 — Workaround example. Name a workaround a slow VPN might cause. Rubric: 3 = emailing files to personal accounts;; 2 = workaround;; 1 = vague;; 0 = none.
- EX032 — Workaround reduction. How can workarounds be reduced? Rubric: 3 = reporting process and fast fixes;; 2 = fix fast;; 1 = punish;; 0 = none.
Synthesis
Planning for expiry, silent failure and workarounds keeps controls effective over time.
Continue studying — chapter 08 of 18
← Chapter 07 (draft) · Course chapter index · Chapter 09 (draft) →