Chapter 43 — Industry or public-service practice
Lesson map
Lesson 43 published. Map, example, EX127.
flowchart TD
N0["Learning outcomes"]
N1["43.1 The placement"]
N2["43.2 Change control"]
N3["43.3 Professional reflection"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX127"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["43.1 The placement"]
N2["43.2 Change control"]
N3["43.3 Professional reflection"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX127"]
[Learning outcomes]
|
v
[43.1 The placement]
|
v
[43.2 Change control]
|
v
[43.3 Professional reflection]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX127]
Learning outcomes
You will (1) apply course knowledge during a placement at a utility; (2) work within governance and change control; (3) reflect on professional practice.
43.1 The placement
Aiyana spends a term on placement in Ridgeway's security operations team, now as a supervised junior engineer. Her tasks include triaging verification alerts, assisting with a quarterly key rotation and updating runbooks. Marcus Webb supervises and signs off her work. She learns that most days are routine and that the value of good design shows in uneventful operations. She also learns how much context engineers need before acting on an alert, such as recent changes and known faulty meters. She keeps a log of each task and what she learned from it.
43.2 Change control
Every production change at Ridgeway goes through change control: a written request, risk assessment, approval and a rollback plan. Aiyana submits her first change, adjusting an alert threshold, and is asked to show evidence from the baseline data. She initially sees the process as slow, then sees its value when another team's unreviewed change to the gateway configuration briefly disables client certificate checks in staging, caught before reaching production. Cryptographic configurations are especially sensitive to small changes, so disciplined change control protects them.
43.3 Professional reflection
At the end of the placement Aiyana writes a reflection. She notes that her academic designs underestimated the time needed for coordination with vendors and field teams, that clear runbooks reduced stress during a minor incident, and that she was tempted once to bypass a slow approval to fix an alert, but didn't. She identifies skills to develop: negotiating with vendors about security requirements and explaining risk to managers. Reflection turns experience into deliberate learning. She shares the reflection with Marcus and agrees two goals for her first year.
Worked example
Aiyana triages alerts, assists a rotation and updates runbooks under supervision, follows change control, and writes a reflection identifying vendor negotiation as a skill gap.
Synthetic case. The placement and events are invented.
Errors and limits
Placements can become passive observation; set concrete tasks and reviews. Change control can become bureaucratic if it ignores risk levels.
Exercises
- EX127 — Placement tasks. Name two tasks Aiyana performed on placement. Rubric: 3 = two of alert triage, assisting rotation, updating runbooks;; 2 = one;; 1 = vague;; 0 = none.
- EX128 — Change-control lesson. What event showed the value of change control? Rubric: 3 = an unreviewed gateway change disabled client certificate checks in staging, caught before production;; 2 = event;; 1 = vague;; 0 = none.
- EX129 — Skill gap. Which skills did she identify to develop? Rubric: 3 = negotiating security requirements with vendors and explaining risk to managers;; 2 = one;; 1 = vague;; 0 = none.
Synthesis
Practice shows that disciplined change control, clear runbooks and reflection matter as much as design knowledge.
Continue studying — chapter 43 of 50
← Chapter 42 (draft) · Course chapter index · Chapter 44 (draft) →