Chapter 29 — Network and communications security: operations | Bachelor's Network and communications security

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 29 — Network and communications security: operations

Lesson map

Lesson 29 published. Map, example, EX085.

flowchart TD
  N0["Learning outcomes"]
  N1["29.1 Routine checks"]
  N2["29.2 Change management"]
  N3["29.3 Responding to alerts"]
  N4["29.4 Supporting the IT lead"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5
  N5 --> EX["Worked example"]
  EX --> Q["Exercise EX085"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["29.1 Routine checks"]
  N2["29.2 Change management"]
  N3["29.3 Responding to alerts"]
  N4["29.4 Supporting the IT lead"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX085"]

[Learning outcomes]
    |
    v
[29.1 Routine checks]
    |
    v
[29.2 Change management]
    |
    v
[29.3 Responding to alerts]
    |
    v
[29.4 Supporting the IT lead]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX085]

Learning outcomes

You will (1) plan routine operations; (2) manage changes; (3) respond to alerts.

29.1 Routine checks

Security depends on small tasks done regularly. Priya drafts a weekly routine for the clinic IT lead: review denied connections from the guest group, check that every device sent logs, look at certificates expiring within sixty days and confirm backups of firewall configurations exist. Each item has a checklist and an expected time, totalling about forty minutes. Keeping the routine short makes it realistic for a part-time role. A routine that takes half a day would soon be skipped during busy weeks.

29.2 Change management

Changes to rules or wireless settings follow a simple process: a written request stating what and why, a check against the needed-flows list, a test in the lab where possible, a scheduled time outside clinic hours and a check afterwards. Emergency changes are allowed when patient care is affected but are recorded the same day and reviewed later. Priya keeps the process light enough that the IT lead will use it, since a process that is too heavy gets bypassed.

29.3 Responding to alerts

Priya defines what triggers an alert: repeated denies from one guest device towards internal groups, a configuration change outside a scheduled window, or a device that stops logging. Each alert type has a short response note: what to check first, when to disconnect a device and whom to contact. Alerts outside working hours go to email for review the next morning, since the clinics have no overnight staff, and clinical systems have separate supplier support for urgent faults. Each response note fits on one page.

29.4 Supporting the IT lead

A single part-time person cannot do everything. Priya suggests the clinics agree a support arrangement with a local provider for out-of-hours emergencies, and write down passwords and procedures in a sealed, controlled record so that someone else can act if the IT lead is unavailable. Documentation and backup arrangements reduce dependence on one person, a common weakness in small organisations that only becomes visible during illness, holidays or departures. Priya also recommends that a second staff member learns the weekly routine, so basic checks continue during absences and someone besides the IT lead can recognise when something looks wrong.

Worked example

The weekly routine has four checks and takes about forty minutes; two alert types are defined with response notes.

Synthetic case. Routines are synthetic.

Errors and limits

Routines too long for the staff available are skipped first when work is busy.

Exercises

EX085 — Routine length. Why keep the weekly routine around forty minutes? Rubric: 3 = realistic for part-time role, won't be skipped;; 2 = short;; 1 = arbitrary;; 0 = none.
EX086 — Emergency changes. How are emergency changes controlled? Rubric: 3 = recorded same day, reviewed later;; 2 = recorded;; 1 = not allowed;; 0 = none.
EX087 — Single-person risk. What reduces dependence on the single IT lead? Rubric: 3 = documentation, controlled credential record, external support;; 2 = documentation;; 1 = vague;; 0 = none.

Synthesis

Short routines, light change control and clear alert responses keep controls working over time.

Continue studying — chapter 29 of 40

← Chapter 28 (draft) · Course chapter index · Chapter 30 (draft) →