◇ OpenCyber Academy
Engineering · Chapter 50 · English

Chapter 50 — Final defense

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 50 — Final defense

Lesson map

Lesson 50 published. Map, example, EX148.

flowchart TD
  N0["Learning outcomes"]
  N1["50.1 Preparing to defend"]
  N2["50.2 Answering challenges"]
  N3["50.3 After the defense"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX148"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["50.1 Preparing to defend"]
  N2["50.2 Answering challenges"]
  N3["50.3 After the defense"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX148"]
[Learning outcomes]
    |
    v
[50.1 Preparing to defend]
    |
    v
[50.2 Answering challenges]
    |
    v
[50.3 After the defense]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX148]

Learning outcomes

You will (1) defend an engineering thesis before examiners and practitioners; (2) answer challenges with evidence and acknowledged limits; (3) plan professional development after graduation.

50.1 Preparing to defend

Sofia prepares a twenty-minute presentation focused on the problem, key decisions, evidence and limits, rather than on everything she did. She anticipates questions: why not move everything to the cloud, how the design handles a stolen tariff-signing key, whether the red-team finding means the design failed and how her patterns apply to smaller operators. For each she prepares an answer pointing to a section of the thesis or a piece of evidence in the dossier. She rehearses with Daniel and classmates, timing herself and practising short, direct answers.

50.2 Answering challenges

An examiner asks whether the signed-tariff design is pointless if the signing key is stolen. Sofia explains the layered design: the independent publication list maintained by finance would reveal unpublished versions, and rollback limits damage; she concedes that a coordinated compromise of both the key and finance's list would defeat the controls. A practitioner asks whether the red-team success shows failure. She answers that it validated the specification by revealing a requirement gap, which was fixed. Conceding precisely where the design stops is more convincing than claiming it cannot fail.

50.3 After the defense

The examiners pass the thesis with minor corrections: clarify the assurance case notation and add a paragraph on post-quantum migration timing. Sofia completes them and archives the thesis and dossier with their manifest. Daniel offers her a junior architect position at Corvia. Her development plan includes leading a full threat-modelling programme, studying the NIST post-quantum standards in depth and mentoring next year's placement student. Her reflection notes that five years taught her that security architecture is the discipline of making trade-offs explicit, evidenced and owned.

Worked example

Sofia defends her thesis, concedes the joint key-and-list compromise limit, frames the red-team finding as validation success, completes corrections and plans her first professional year.

Synthetic case. Examiners, questions and the job offer are synthetic.

Errors and limits

Defense performance is not the same as design quality. Corrections should not change claims without new evidence.

Exercises

Synthesis

A final defense shows mastery by explaining decisions, conceding limits precisely and turning study into professional practice.

Continue studying — chapter 50 of 50

← Chapter 49 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →