Chapter 10 — Network and communications security: quality and troubleshooting
Lesson map
Lesson 10 published. Map, example, EX046.
flowchart TD
N0["Learning outcomes"]
N1["10.1 Security changes and service problems"]
N2["10.2 The tablet"]
N3["10.3 The court filing forwarding"]
N4["10.4 Quality checks"]
N5["10.5 Learning from errors"]
N6["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6
N6 --> EX["Worked example"]
EX --> Q["Exercise EX046"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["10.1 Security changes and service problems"]
N2["10.2 The tablet"]
N3["10.3 The court filing forwarding"]
N4["10.4 Quality checks"]
N5["10.5 Learning from errors"]
N6["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> Q["EX046"]
[Learning outcomes]
|
v
[10.1 Security changes and service problems]
|
v
[10.2 The tablet]
|
v
[10.3 The court filing forwarding]
|
v
[10.4 Quality checks]
|
v
[10.5 Learning from errors]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX046]
Learning outcomes
You will (1) troubleshoot security-related service problems; (2) maintain quality of controls; (3) learn from errors.
10.1 Security changes and service problems
After the firm enables multi-factor authentication for email and blocks external forwarding, some users report problems. A partner cannot sign in on an old tablet; a support team's shared mailbox stops forwarding to a court filing service. Grace approaches each as a troubleshooting task: precise description, evidence from logs, hypothesis, test and narrow fix. The goal is to restore legitimate service without weakening the new controls. She also tracks how many users report problems in the first week, which shows whether the rollout communications were clear enough.
10.2 The tablet
Logs show the tablet uses an old mail app that does not support modern sign-in with a second factor. Options are to replace the app, replace the tablet or exempt the account. Exempting the account would leave a partner's mailbox without multi-factor authentication, which is not acceptable. Grace recommends installing the supported mail app, which takes ten minutes. Narrow fixes like this preserve the control for everyone while solving the user's real problem. She adds the old app to a list of unsupported software for the help desk.
10.3 The court filing forwarding
The shared mailbox legitimately forwards certain messages to a court filing service. Grace confirms the destination with the support team lead, and Priyanka adds an approved exception for that mailbox and that destination only, with an owner and a review date. The exception is documented in the change log. Approved, narrow exceptions are part of a mature control; a block that cannot accommodate legitimate needs will eventually be removed entirely under pressure. The court filing destination is also added to the email service's monitoring, so unusual volumes are noticed.
10.4 Quality checks
Grace adds quality checks to the weekly routine: count of accounts without multi-factor authentication, which should be zero; count and age of forwarding exceptions; and any new rules without owners. She also proposes a quarterly sample review of closed alert tickets, checking that conclusions were supported by evidence. Quality checks catch slow decay, such as exceptions accumulating or alerts being closed without investigation. The results are shown as a short table in the weekly report, with any non-zero values highlighted, so Priyanka can see at a glance whether controls are holding.
10.5 Learning from errors
During the rollout, a configuration error briefly blocked forwarding for an approved exception because the destination was mistyped. Grace records it in a lessons log: what happened, effect, cause and change made. The change is to copy addresses from the original request rather than retyping them. Small, recorded lessons accumulate into better practice. Teams that record errors openly improve faster than those that fix them quietly and forget. The lessons log is reviewed monthly by the IT team, and recurring causes are turned into checklist items or small process changes.
Worked example
Two service problems are resolved without weakening controls; weekly checks show zero accounts without MFA.
Synthetic case. Cases are synthetic.
Errors and limits
Exempting users from controls to fix device problems leaves the most exposed accounts unprotected.
Exercises
- EX046 — Tablet fix. How was the partner's tablet problem fixed? Rubric: 3 = install supported mail app;; 2 = new app;; 1 = exemption;; 0 = none.
- EX047 — Exception scope. What does the forwarding exception cover? Rubric: 3 = one mailbox to one destination, owner, review date;; 2 = narrow;; 1 = all;; 0 = none.
- EX048 — Quality check. Give one weekly quality check. Rubric: 3 = accounts without MFA, exceptions, rules without owners;; 2 = one;; 1 = vague;; 0 = none.
- EX049 — Mistyped lesson. What changed after the mistyped destination? Rubric: 3 = copy addresses from request, not retype;; 2 = copy;; 1 = vague;; 0 = none.
- EX050 — Exception necessity. Why are narrow approved exceptions necessary? Rubric: 3 = otherwise control removed under pressure;; 2 = usability;; 1 = weakness;; 0 = none.
Synthesis
Careful troubleshooting, narrow exceptions and quality checks keep controls effective and usable.
Continue studying — chapter 10 of 12
← Chapter 09 (draft) · Course chapter index · Chapter 11 (draft) →