Chapter 7 — Network and communications security: organizational integration
Lesson map
Lesson 07 published. Map, example, EX031.
flowchart TD
N0["Learning outcomes"]
N1["7.1 Fitting changes into operations"]
N2["7.2 Roles and responsibilities"]
N3["7.3 The partner link"]
N4["7.4 Training and handover"]
N5["7.5 Measuring integration"]
N6["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6
N6 --> EX["Worked example"]
EX --> Q["Exercise EX031"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["7.1 Fitting changes into operations"]
N2["7.2 Roles and responsibilities"]
N3["7.3 The partner link"]
N4["7.4 Training and handover"]
N5["7.5 Measuring integration"]
N6["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> Q["EX031"]
[Learning outcomes]
|
v
[7.1 Fitting changes into operations]
|
v
[7.2 Roles and responsibilities]
|
v
[7.3 The partner link]
|
v
[7.4 Training and handover]
|
v
[7.5 Measuring integration]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX031]
Learning outcomes
You will (1) integrate changes into operations; (2) align processes and roles; (3) manage partner relationships.
7.1 Fitting changes into operations
New controls only last if they become part of daily work. Marta maps each change onto the operations team's existing processes. VPN migrations join the monthly maintenance schedule. Validation reports join the weekly network review. Ingress filter matches join the support queue as a ticket category. She avoids creating separate processes that only she understands, since her placement will end. Each addition is small, uses existing tools where possible and has a named owner within the team, which makes the changes durable after the project.
7.2 Roles and responsibilities
Marta drafts a simple responsibility table. Network engineers configure filters and VPNs; the operations lead approves changes; support staff contact customers; a director signs off enforcement stages. For route validation, one engineer is named as the contact for other networks about incorrect records. Clear roles prevent the common failure where everyone assumes someone else is watching. The table is reviewed with the team, who suggest that a second engineer shares the external contact role to cover holidays. The final table is posted in the operations wiki.
7.3 The partner link
The VPN with the partner provider needs joint work. Marta prepares a short proposal for the partner's engineers: migrate to IKEv2 with certificates, agree the certificate authority arrangement, schedule a joint maintenance window and define a test plan. The partner is cautious because a previous change caused an outage. She suggests building a parallel tunnel first and moving traffic only after both sides confirm it works, so the old tunnel remains as a fallback. The partner agrees to this lower-risk approach.
7.4 Training and handover
The operations team is skilled but has not used route validation tools before. Marta runs two short sessions: one on how validation works and what results mean, using the lab examples, and one on reading the weekly invalid-route report and deciding when to contact another network. She writes a runbook for each task with screenshots from the test environment. Training tied to actual tasks is more effective than general courses, and the runbooks let new staff learn the same tasks later without depending on her.
7.5 Measuring integration
Marta checks integration with simple indicators: are weekly reports being reviewed on time, are filter-match tickets being closed, are migrations proceeding to schedule? After two months, reports are reviewed every week, all tickets are closed within five days and four of five planned VPN migrations are complete. These indicators show the changes have become routine. Where an indicator slips, such as one late report during a holiday, the team adjusts the responsibility table rather than adding new process. The indicators are reviewed monthly by the operations lead.
Worked example
Marta's responsibility table names owners for five tasks; after two months, integration indicators show reviews on time and four of five migrations done.
Synthetic case. Organisation and indicators are synthetic.
Errors and limits
Controls owned only by a project member fade when the project ends.
Exercises
- EX031 — Process reuse. Why add tasks to existing processes rather than create new ones? Rubric: 3 = durability after placement, familiar to team;; 2 = durability;; 1 = speed;; 0 = none.
- EX032 — Shared contact role. Why name a second external contact for route validation? Rubric: 3 = cover holidays and absences;; 2 = cover;; 1 = vague;; 0 = none.
- EX033 — Parallel tunnel. How does a parallel tunnel reduce partner risk? Rubric: 3 = old tunnel remains as fallback until new confirmed;; 2 = fallback;; 1 = faster;; 0 = none.
- EX034 — Task-based training. Why base training on actual tasks? Rubric: 3 = more effective and supports runbooks for later;; 2 = practical;; 1 = cheaper;; 0 = none.
- EX035 — Integration indicator. Give one indicator that changes have become routine. Rubric: 3 = reports reviewed on time, tickets closed, migrations on schedule;; 2 = one;; 1 = vague;; 0 = none.
Synthesis
Changes endure when they fit existing processes, have clear owners and are measured as routine.
Continue studying — chapter 07 of 12
← Chapter 06 (draft) · Course chapter index · Chapter 08 (draft) →