Chapter 26 — Network and communications security: operational handoff
Lesson map
Lesson 26 published. Map, example, EX076.
flowchart TD
N0["Learning outcomes"]
N1["26.1 Runbooks"]
N2["26.2 Routines"]
N3["26.3 Ownership and support"]
N4["26.4 Handover meeting"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5
N5 --> EX["Worked example"]
EX --> Q["Exercise EX076"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["26.1 Runbooks"]
N2["26.2 Routines"]
N3["26.3 Ownership and support"]
N4["26.4 Handover meeting"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX076"]
[Learning outcomes]
|
v
[26.1 Runbooks]
|
v
[26.2 Routines]
|
v
[26.3 Ownership and support]
|
v
[26.4 Handover meeting]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX076]
Learning outcomes
You will (1) prepare operations for the long term; (2) write runbooks; (3) transfer ownership.
26.1 Runbooks
A runbook gives step-by-step instructions for a routine task. Tomás writes runbooks for adding a new device to the right zone, handling a blocked-service report, reviewing weekly alerts, restoring a switch from backup and running the termly account review. Each includes when to use it, steps, expected results and what to do if something goes wrong. He tests each runbook by having another student follow it in the lab without help, fixing unclear steps. Runbooks are stored with the network documentation and updated after every incident.
26.2 Routines
Gareth's weekly routine takes about thirty minutes: review alert summaries, check the drift report, confirm every device sent logs and check certificates expiring within sixty days. Termly tasks include the account review and the service comparison. Annual tasks include reviewing zones and flows with stakeholders. A written schedule makes the routines visible to the head teacher, who can check they are happening, and helps a replacement technician pick them up. Each completed routine is ticked off in a shared log, so missed weeks are easy to spot.
26.3 Ownership and support
Each part of the design has an owner: Gareth for network devices and rules, the business manager for administration zone access decisions, the safeguarding lead for filtering categories, and suppliers for their services under contract. Tomás records these in a responsibility table approved by the head teacher. He also arranges, with the school's agreement, a small support contract with a local provider for emergencies when Gareth is unavailable. Owners are reminded of their duties at the start of each school year.
26.4 Handover meeting
At the handover meeting, Tomás walks through the documentation, routines and open items with Gareth, the head teacher and Ms Okafor. Open items include replacing the old printers that need the raw printing port and reviewing the DNS exclusion in spring. Gareth signs acceptance of the documentation. A formal handover marks the point where responsibility clearly passes, so nothing falls between the end of the placement and normal operations. The signed acceptance is filed with the documentation, and Ms Okafor confirms the placement objectives were met.
Worked example
Five runbooks, a weekly thirty-minute routine and a responsibility table are handed over with two open items.
Synthetic case. Handover is synthetic.
Errors and limits
Runbooks never tested by someone else often contain steps only the author understands.
Exercises
- EX076 — Runbook test. How were runbooks tested? Rubric: 3 = another student followed them unaided in lab;; 2 = followed;; 1 = reviewed;; 0 = none.
- EX077 — Weekly routine items. List three weekly routine items. Rubric: 3 = alerts, drift report, log arrival or certificates;; 2 = two;; 1 = one;; 0 = none.
- EX078 — Open item. Name one open item at handover. Rubric: 3 = replace old printers or review DNS exclusion;; 2 = one;; 1 = vague;; 0 = none.
Synthesis
Tested runbooks, written routines and clear ownership let operations continue after the project.
Continue studying — chapter 26 of 30
← Chapter 25 (draft) · Course chapter index · Chapter 27 (draft) →