Chapter 49 — Engineering thesis | Engineering Information security

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 Argument"]
  N2["49.2 Structure"]
  N3["49.3 Evaluation"]
  N0 --> N1 --> N2 --> N3
  N3 --> EX["Worked example"]
  EX --> Q["Exercise EX145"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["49.1 Argument"]
  N2["49.2 Structure"]
  N3["49.3 Evaluation"]
  N0 --> N1 --> N2 --> N3 --> Q["EX145"]

[Learning outcomes]
    |
    v
[49.1 Argument]
    |
    v
[49.2 Structure]
    |
    v
[49.3 Evaluation]
    |
    v
[Worked example] --> [Exercise EX145]

Learning outcomes

You will (1) write an engineering thesis around a central argument; (2) present design, evidence and evaluation; (3) reflect on contribution and limits.

49.1 Argument

Lindiwe's thesis argues that a small organisation can achieve verifiable ransomware recovery within business objectives by combining immutable backups, checksum verification, scripted rebuilds and regular trials. The argument rests on her capstone and dossier. Prof. Hale asks her to state the argument in the first paragraph and to make every chapter contribute to it, so readers can follow why each part exists. She writes a one-page outline listing each chapter and the part of the argument it supports, and Prof. Hale uses it to guide his reading of the drafts.

49.2 Structure

The thesis has chapters on context and requirements, related work, dependency analysis, design and review, implementation, trials and results, evaluation and limitations. Related work draws on Anderson's Security Engineering, NIST SP 800-30 Revision 1 for risk assessment and ISO/IEC 27001:2022 for management system context. She cites each source for specific points rather than as decoration, and paraphrases standards rather than quoting long passages. Each chapter begins with a short paragraph stating its purpose and ends with a summary of what it has shown. Prof. Hale finds this structure helpful.

49.3 Evaluation

Lindiwe evaluates the work against the objective: trials met four hours repeatedly, with the final unannounced trial at three hours and thirty-five minutes. She also evaluates against cost, showing the recovery environment uses existing hardware. She compares with the situation before the project, when no full rebuild had ever been attempted. She is careful to describe results as applying to Saltmarsh's environment and data volumes. She presents all trial times in one table with the changes made between trials, so examiners can see how the result was reached.

49.4 Contribution and limits

Lindiwe identifies her contribution as a tested, documented recovery method with a measured timeline, plus the finding that recovery environments must be isolated from production credentials. Limits include one organisation, an isolated trial environment and growing data volumes threatening the objective. Prof. Hale approves the thesis for submission, noting that its honesty about limits strengthens rather than weakens it. She also suggests future work: testing recovery for payroll, measuring how database growth affects restore time and repeating the trial with a real incident team from another organisation.

Worked example

Lindiwe argues for verifiable small-organisation ransomware recovery, structures chapters around the argument, evaluates against the four-hour objective and states contribution and limits.

Synthetic case. The thesis is synthetic.

Errors and limits

Citing sources as decoration rather than for specific points weakens a thesis.

Exercises

EX145 — Thesis argument. What does the thesis argue? Rubric: 3 = small organisations can achieve verifiable recovery;; 2 = partly correct;; 1 = vague;; 0 = none.
EX146 — Risk source. Which source supports risk assessment? Rubric: 3 = NIST SP 800-30 Revision 1;; 2 = partly correct;; 1 = other;; 0 = none.
EX147 — Key finding. What key finding concerns recovery environments? Rubric: 3 = must be isolated from production credentials;; 2 = partly correct;; 1 = vague;; 0 = none.

Continue studying — lesson 49 (chapter 49 of 50)

← Chapter 48 · Course chapter index · Chapter 50 →

Continue to the next authored lesson.