Chapter 49 — Engineering thesis
Lesson map
Lesson 49 published. Map, example, EX145.
flowchart TD
N0["Learning outcomes"]
N1["49.1 Claim"]
N2["49.2 Body"]
N3["49.3 Citations"]
N4["Practice note"]
N5["49.1b Related work honesty and reproducibility"]
N6["Field note — claim on page one"]
N7["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX145"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["49.1 Claim"]
N2["49.2 Body"]
N3["49.3 Citations"]
N4["Practice note"]
N5["49.1b Related work honesty and reproducibility"]
N6["Field note — claim on page one"]
N7["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX145"]
[Learning outcomes]
|
v
[49.1 Claim]
|
v
[49.2 Body]
|
v
[49.3 Citations]
|
v
[Practice note]
|
v
[49.1b Related work honesty and reproducibility]
|
v
[Field note — claim on page one]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX145]
Learning outcomes
You will (1) structure a thesis around a programme claim; (2) defend measures and limits; (3) cite SP 800-82, 62443, ATT&CK for ICS and evaluation papers correctly.
49.1 Claim
One sentence: what you built/measured and for whom. Example: Signed allow-list distribution with fail-closed semantics reduces unauthorized writes forwarded in synthetic trials.
Lena's own claim was about her compiler: for ABP's nine-conduit model, generated rules matched the design's reachability and caught three errors manual review missed. Her sentence names what she built, which plant model it was tested on and what it showed, so an examiner can check each part against the evidence. She rewrote it several times until every clause pointed to a specific result in the body.
49.2 Body
Related work, design, verification, results with intervals and attack classes, limitations, ethics.
Lena's thesis follows this order. Related work cites the standards behind her methods, each with a how-used note. Design explains how the compiler turns ABP's zone model into rules. Verification shows the equivalence check and conformance vectors, results report the three errors found, limitations state that a flawed zone model would be compiled faithfully, and the ethics chapter explains why no live plant was touched. Each part points to evidence.
49.3 Citations
Use verified URLs/DOIs from the source policy; do not invent papers. Note access dates. Giraldo et al. CSUR 2018 doi 10.1145/3203245; Urbina et al. CCS 2016 doi 10.1145/2976749.2978388.
Synthetic case — Ashford Batch Plant. Thesis draft used only synthetic trial data and cited SP 800-82 Rev. 3 correctly.
Lena checked every reference in her thesis against its DOI or official URL and recorded the access date. Each citation has a note saying how the work was used, so none is listed without being read. Her advisor checked the notes.
49.4 Errors and limits
A thesis that evaluates exploitation skill is out of programme scope.
Lena's thesis measures whether her compiler produces correct rules, not whether she can break into a plant. Her ethics chapter states that the work used only synthetic exports of ABP's zone model and the bench firewall, and it gives an example of a request she refused: testing generated rules against a live plant firewall. Examiners judge the engineering and evidence, so attack skill is neither demonstrated nor assessed in the defense.
Practice note
Threats-to-validity page is graded. Examiners read that page first. Length is not rigor; structured limits are.
49.1b Related work honesty and reproducibility
Cite frameworks you actually used. Padding related work with unread papers is discovered in defense. Ship enough to replay synthetic trials: fixture hashes, tool SHAs, scripts. Available on request is not a reproducibility appendix. Put the claim sentence in bold on page one.
How-used notes stop citation padding cold in advisor review. Leaving the threats-to-validity page blank fails the thesis gate regardless of implementation quality.
Lena's threats page lists the compiler's reliance on a correct zone model as its first threat, the same limitation she names at her defense.
Field note — claim on page one
Examiners and advisors share the same target when the claim sentence is bold on page one. Thin, accurate related work with how-used notes beats a padded bibliography that collapses under the first question.
Lena's appendix lets an examiner replay the equivalence check in under ten minutes.
Each related-work entry states whether the cited method was used, compared against, or only discussed.
49.5 Worked example — a thesis claim with its evidence (synthetic ABP)
Lena's thesis claim, on page one: "For ABP's nine-conduit model, a compiler that generates firewall rules and conformance vectors from a zone model produced rules equivalent in reachability to the design and caught three rule errors that manual review missed." The body supports each clause: the equivalence check, the three errors with their vectors, and the manual review's results on the same rule set. Related work cites IEC 62443-3-2 for the zone-and-conduit method and NIST SP 800-82r3 for segmentation guidance, and states plainly that formal verification tools exist that the thesis did not compare against.
Exercises
- EX145 — Claim. One-sentence thesis claim for dual-approval of conduits. Rubric: 3 = measurable+scoped; 2 = vague; 1 = exploit claim; 0 = none.
- EX146 — Limit. One limitation paragraph (3 sentences). Rubric: 3 = external validity clear; 2 = partial; 1 = none; 0 = overclaim.
- EX147 — Cite. Give the DOI for Urbina et al. CCS 2016. Rubric: 3 = 10.1145/2976749.2978388; 2 = title only; 1 = wrong; 0 = none.
Synthesis
One claim, honest limits, real citations.
Continue studying — chapter 49 of 50
← Chapter 48 (draft) · Course chapter index · Chapter 50 (draft) →