Chapter 12 — Final review and transfer
Lesson map
Lesson 12 published. Map, example, EX056.
flowchart TD
N0["Learning outcomes"]
N1["12.1 Portfolio review"]
N2["12.2 Defence"]
N3["12.3 Transfer"]
N4["12.4 Continuing development"]
N5["12.5 Legacy"]
N6["12.6 Worked case"]
N7["12.8 Reflecting on judgment"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX056"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["12.1 Portfolio review"]
N2["12.2 Defence"]
N3["12.3 Transfer"]
N4["12.4 Continuing development"]
N5["12.5 Legacy"]
N6["12.6 Worked case"]
N7["12.8 Reflecting on judgment"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX056"]
[Learning outcomes]
|
v
[12.1 Portfolio review]
|
v
[12.2 Defence]
|
v
[12.3 Transfer]
|
v
[12.4 Continuing development]
|
v
[12.5 Legacy]
|
v
[12.6 Worked case]
|
v
[12.8 Reflecting on judgment]
|
v
[Worked example] --> [Exercise EX056]
Learning outcomes
You will (1) review your portfolio against course outcomes; (2) present and defend organization-scale choices; (3) transfer methods to other domains and future algorithm changes; (4) plan continuing professional development; and (5) leave a maintainable legacy.
12.1 Portfolio review
Assemble: the decision records from Chapter 1; state-of-practice brief (2); inventory design and metrics (3); risk and ethics analysis (4); design alternatives (5); evaluation (6); governance model (7); difficult-case plans (8); assurance design (9); research critiques (10); project deliverables (11). For each, note what evidence shows the outcome was met.
Present the portfolio in the same order as the course so that examiners can follow it. For each item, include a short note on what you would change now. Missing evidence should be named rather than hidden. Ask a peer to read it before submission.
12.2 Defence
Expect challenges on assumptions (timelines, harm horizons), values (scoring weights), evidence grades, residual-risk acceptance, and status of guidance. Defend with evidence and acknowledge uncertainty.
Prepare a short answer to each challenge with a pointer to evidence in the portfolio, such as the decision record for internal dates or the scoring weights approved by the board. Where you are uncertain, say what evidence would resolve it. Rehearse with someone who disagrees with your choices. Keep the answers short and specific. Note any question you could not answer.
12.3 Transfer
The methods transfer: robust decisions under uncertainty, evidence grading, controlled evaluation, policy-driven agility and assurance by re-observation apply to any future cryptographic transition — a break in a deployed algorithm, a new standard such as FN-DSA, or the eventual retirement of today's hybrids. They also transfer to other long-latency risks.
To show transfer, apply one method to a new case in the portfolio, such as using the canary gate for a planned change of signature algorithm. Note which parts of the method needed adapting and which did not.
12.4 Continuing development
Track standards (NIST, IETF), sector guidance, cryptanalysis and deployment research. Maintain your state-of-practice brief quarterly. Participate in professional communities and share anonymised lessons.
Write a plan with specific sources and a schedule, and review it each year. Keep a short log of what you read and what changed in your practice because of it. Share one anonymised lesson each year with a professional community, and invite comments from peers who work in other sectors, since their transitions may face similar problems and offer useful comparisons.
12.5 Legacy
Leave the organization with a living inventory, a cryptographic standard with a review cycle, decision records, an exception register with expiries and trained successors. Success is a programme that continues without you.
Check the legacy by asking a successor to run the quarterly review without you, and fix any step they could not complete. Record where each key document lives and who owns it. A test run by the successor before you leave is the best evidence that the legacy works, so schedule one and record what had to be fixed.
12.6 Worked case
At NRHT's final review the programme lead presents: tier-1 hybrid coverage 78 % with A/B evidence; unknown 5 %; ML-DSA internal root in place with 40 % of internal service certificates migrated; 12 accepted residual risks, all with expiry; agility test passed on four platforms. An examiner asks what happens if IR 8547 is finalised with earlier dates; the lead shows the decision record for setting internal dates and the governance trigger for review.
The final review shows progress with evidence grades and names the residual risks, each with an expiry. The examiner's question is answered with a governance mechanism rather than a prediction, which is the kind of answer a robust programme should be able to give.
12.7 Common errors and limits
- Portfolios without evidence of outcomes.
- Defences that overclaim certainty.
- Legacy that depends on the departing lead.
Each error has a guard. Attach evidence of outcomes to each portfolio item. In the defence, state assumptions and uncertainties plainly. Train successors and document processes so that the programme continues after you leave. At NRHT the final review presented coverage with evidence grades, residual risks with expiries and an agility test on four platforms. The examiner's question about IR 8547 was answered with a governance trigger. Use that structure: outcome, evidence, residual risk and the mechanism that will respond to change after you leave.
12.8 Reflecting on judgment
Close the portfolio with a reflective note on your own judgment: one decision you would make again, one you would change with what you now know, and one assumption you are least sure of. Specialists are trusted not because they are always right but because they show how they reason and update. The note also helps successors understand which parts of the programme rest on firm evidence and which on considered bets. At NRHT, for example, the infusion pump plan assumes that the vendor's 2027 hybrid firmware release arrives on time and passes clinical testing, and saying so plainly tells the next lead where to look first.
Exercises
- EX056 — Outcome evidence. For three course outcomes, name the portfolio evidence that demonstrates each. Rubric: 3 = specific artefacts.
- EX057 — Transfer. Explain how the programme would handle a new requirement to adopt FN-DSA. Rubric: 3 = policy, inventory, evaluation, rollout via agility.
- EX058 — Defence answer. Answer: "Why did you accept residual risk for infusion pumps?" Rubric: 3 = constraints, compensating controls, expiry, safety rationale.
- EX059 — CPD plan. Draft a one-year continuing development plan. Rubric: 3 = sources, cadence, outputs.
- EX060 — Legacy checklist. List six items that must exist for the programme to continue without you. Rubric: 3 = six concrete items.
Synthesis
The final review demonstrates outcomes with evidence, defends choices honestly, and transfers methods and capability so that future cryptographic changes find a prepared organization.
Continue studying — chapter 12 of 12
← Chapter 11 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →