◇ OpenCyber Academy
Engineering · Chapter 49 · English

Chapter 49 — Engineering thesis

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 49 — Engineering thesis

Lesson map

Lesson 49 published. Map, example, EX145.

flowchart TD
  N0["Learning outcomes"]
  N1["49.1 Thesis structure"]
  N2["49.2 The argument"]
  N3["49.3 Contribution"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX145"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["49.1 Thesis structure"]
  N2["49.2 The argument"]
  N3["49.3 Contribution"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX145"]
[Learning outcomes]
    |
    v
[49.1 Thesis structure]
    |
    v
[49.2 The argument]
    |
    v
[49.3 Contribution]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX145]

Learning outcomes

You will (1) write the engineering thesis; (2) present the argument from problem to evidence; (3) state contribution and limits.

49.1 Thesis structure

Sana's thesis follows the engineering story: problem and context, requirements, threat and failure analysis, architecture alternatives and choice, control design, implementation, verification, measurement, validation, applied research and conclusions. Each chapter opens with its purpose and ends by linking to the next. Tables carry key numbers, with references to dossier evidence. She writes the method and results chapters first, while details are fresh, and the introduction last, once she knows exactly what the thesis shows. Signposting helps examiners follow the argument across chapters.

49.2 The argument

The argument runs: Linmouth had fragmented identities, slow leaver removal and weak authentication; requirements were derived from audit findings and threats; a cloud identity provider with HR-driven lifecycle was chosen against agreed criteria; controls were designed, implemented in phases and verified; and measurements show leaver removal falling from weeks to hours and phishing-resistant authentication becoming the norm. Each step cites evidence. Sana avoids claiming more than the evidence shows, such as a reduction in attacks, which she did not measure.

49.3 Contribution

Sana states her contribution clearly: an engineered and verified identity programme for a mid-sized public body, a reusable requirements set and test catalogue, a measured lifecycle improvement, and a small randomised study suggesting that last-use dates improve access reviews. Saltzer and Schroeder's principles and the NIST guidance cited throughout provide the foundations; her contribution is showing how they can be applied, measured and evidenced in a real setting with limited staff and budget. Each part is linked to its evidence in the dossier.

49.4 Limits and future work

Limits include one organisation, a measurement period of under a year after rollout, and some applications still on interim controls. Future work includes measuring whether access drifts back over several years, extending the review study across more cycles, and evaluating supplier access patterns. Stating limits clearly helps examiners trust the thesis and helps the council decide what to do next. Sana also notes what she would do differently: involve HR earlier, since feed reliability became central. Each limit is linked to its likely effect.

Worked example

The thesis follows the engineering story from problem to evidence, claims a verified programme, reusable artefacts, measured lifecycle improvement and a small review study, and states limits and future work.

Synthetic case. The thesis and its claims are synthetic.

Errors and limits

Claiming a reduction in attacks that was never measured overstates the evidence.

Exercises

Synthesis

A clear engineering thesis links problem, design, evidence and limits into one credible argument.

Continue studying — chapter 49 of 50

← Chapter 48 (draft) · Course chapter index · Chapter 50 (draft) →