Chapter 12 — Practice portfolio and final review
Lesson map
Lesson 12 published. Map, example, EX056.
flowchart TD
N0["Learning outcomes"]
N1["12.1 The portfolio"]
N2["12.2 What changed"]
N3["12.3 Continued practice"]
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 The portfolio"]
N2["12.2 What changed"]
N3["12.3 Continued practice"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX056"]
[Learning outcomes]
|
v
[12.1 The portfolio]
|
v
[12.2 What changed]
|
v
[12.3 Continued practice]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX056]
Learning outcomes
You will (1) assemble a portfolio of professional work; (2) review what changed at Thornbury; (3) plan continued practice.
12.1 The portfolio
Owen assembles his portfolio: the service and stakeholder map, the repairs threat model and ranking, the contractor workflow, requirements with verification results, the refund case analysis, the leadership report, the exception path design and the lab report. Each item has a short note explaining what he did, what he learned and what he would do differently. Personal data is removed or replaced with synthetic examples. The portfolio shows employers and assessors evidence of applied skill rather than course attendance alone.
12.2 What changed
Owen reviews outcomes. Contractor accounts fell from two hundred and ten to one hundred and thirty-five, key safe codes are now visible only to assigned contractors on visit days, bank changes need confirmation, and refunds after changes are held with a safe exception. No refund fraud has been reported since. He is careful to say that the absence of fraud over a few months does not prove the risk has gone, and he recommends continued monitoring and an annual review of the repairs threat model.
12.3 Continued practice
Thornbury creates a security architect role and offers it to Owen. He plans to deepen his knowledge of identity and cloud security, join a professional community, and ask Kwame for a mentor from a partner organisation. He keeps his referral list from chapter 1 and notes which items he can now handle himself. Ines's final feedback is that Owen's project management background became a strength, because security architecture is largely about coordinating people, decisions and evidence across an organisation. He also schedules a six-month review with Ines.
Worked example
Owen assembles an annotated portfolio, reviews measured changes at Thornbury with caution and plans continued development in a new role.
Synthetic case. Portfolio items and outcomes are synthetic.
Errors and limits
Portfolios can overstate individual contribution. Short-term outcomes may not last.
Exercises
- EX056 — Portfolio notes. What note accompanies each portfolio item? Rubric: 3 = what he did, what he learned and what he would change;; 2 = three;; 1 = vague;; 0 = none.
- EX057 — Fraud caution. Why is no reported fraud not proof of success? Rubric: 3 = a few months without fraud does not prove the risk has gone;; 2 = short period;; 1 = proof;; 0 = none.
- EX058 — Next learning. What will Owen study next? Rubric: 3 = identity and cloud security;; 2 = identity;; 1 = vague;; 0 = none.
- EX059 — Background strength. Why did Owen's background become a strength? Rubric: 3 = architecture is largely coordinating people, decisions and evidence;; 2 = coordination;; 1 = vague;; 0 = none.
- EX060 — Data in portfolio. How is personal data handled in the portfolio? Rubric: 3 = removed or replaced with synthetic examples;; 2 = removed;; 1 = vague;; 0 = none.
Synthesis
A portfolio of annotated work, an honest review of outcomes and a plan for growth complete professional preparation.
Continue studying — chapter 12 of 12
← Chapter 11 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →