OpenCyber AcademyLesson map
Lesson 12 published. Map, example, EX056.
flowchart TD
N0["Learning outcomes"]
N1["12.1 What changed"]
N2["12.2 Transfer to a new domain"]
N3["12.3 Continued development"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX056"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["12.1 What changed"]
N2["12.2 Transfer to a new domain"]
N3["12.3 Continued development"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX056"]
[Learning outcomes]
|
v
[12.1 What changed]
|
v
[12.2 Transfer to a new domain]
|
v
[12.3 Continued development]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX056]
Learning outcomes
You will (1) review what the course changed in practice; (2) transfer methods to a new domain; (3) plan continued professional development.
12.1 What changed
Priya reviews the two years. Corvane now has decision records, a fast review board, segmented clinical devices in all clinics, a hybrid access design rolling out in stages, and assurance reports based on verified controls. She lists what did not change: the identity provider remains a concentration of risk, and two legacy devices remain as dated exceptions. She separates results she can attribute to the programme from those that might have happened anyway, such as reduced outages from a vendor's own improvements.
12.2 Transfer to a new domain
Dr Voss asks Priya to apply her methods to a different setting: a fictional water utility's control network. Priya finds that decision records, attribute criteria, reachability models and staged rollouts transfer directly. What changes is the weight of attributes: safety and availability dominate even more, and change windows are rarer. She would consult NIST SP 800-82 Rev. 3 for operational technology, which she notes she has not yet studied in depth. Transfer works for methods; domain knowledge must be acquired fresh each time.
12.3 Continued development
Priya plans her next two years: deepen operational technology knowledge, mentor a junior architect, publish an anonymised case study with Corvane's permission, and present the pilot method at a health informatics meeting. She keeps a learning log and schedules a yearly review of her decision records to see which ones aged well. Dr Voss's final comment is that the course aimed to build judgement, and judgement grows by reviewing past decisions honestly, not by collecting more frameworks. She shares the log with her mentor.
Worked example
Priya reviews programme outcomes and limits, transfers methods to a water utility with domain caveats and plans two years of development.
Synthetic case. Outcomes, the utility and plans are synthetic; SP 800-82 Rev. 3 is real.
Errors and limits
Attribution of outcomes is uncertain. Transfer claims need testing in the new domain.
Exercises
- EX056 — Remaining risk. What concentration of risk remained at Corvane?
Show marking criteria
Rubric: 3 = the identity provider;; 2 = identity;; 1 = vague;; 0 = none. - EX057 — Attribution care. Which outcome might have happened anyway?
Show marking criteria
Rubric: 3 = reduced outages from a vendor's own improvements;; 2 = vendor;; 1 = vague;; 0 = none. - EX058 — Methods that transfer. Name two methods that transfer to the water utility.
Show marking criteria
Rubric: 3 = decision records, attribute criteria, reachability models, staged rollouts;; 2 = one;; 1 = vague;; 0 = none. - EX059 — What changes in transfer. What changes when moving to the utility?
Show marking criteria
Rubric: 3 = attribute weights and rarer change windows;; 2 = weights;; 1 = vague;; 0 = none. - EX060 — Growing judgement. How does judgement grow, according to Dr Voss?
Show marking criteria
Rubric: 3 = by honestly reviewing past decisions;; 2 = review;; 1 = frameworks;; 0 = none.
Synthesis
The course ends by reviewing outcomes honestly, transferring methods with domain caution and planning to grow judgement.
Continue studying — chapter 12 of 12
← Chapter 11 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →