Chapter 8 — Defense and publication plan
Lesson map
Lesson 08 published. Map, example, EX045.
flowchart TD
N0["Learning outcomes"]
N1["8.1 Preparing the defense"]
N2["8.2 Examiners' challenges"]
N3["8.3 Outcome"]
N4["8.4 Publication plan"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX045"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["8.1 Preparing the defense"]
N2["8.2 Examiners' challenges"]
N3["8.3 Outcome"]
N4["8.4 Publication plan"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX045"]
[Learning outcomes]
|
v
[8.1 Preparing the defense]
|
v
[8.2 Examiners' challenges]
|
v
[8.3 Outcome]
|
v
[8.4 Publication plan]
|
v
[Worked example] --> [Exercise EX045]
Learning outcomes
You will (1) defend a thesis with mixed results; (2) answer challenges about generalisation and ethics; (3) plan responsible publication.
8.1 Preparing the defense
Yusuf prepares a forty-minute presentation covering the gap, design, measures, results with intervals, critique and limits. He rehearses with colleagues who press him on the inconclusive patch result. He prepares a slide showing the patch estimate and interval beside the clearer excess privilege result, so examiners can see both without him emphasising the more favourable one. Prof. Hald advises him to state each claim in the same words used in the thesis to avoid drifting into stronger language under pressure. Rehearsals are timed.
8.2 Examiners' challenges
The external examiner asks whether one council can tell anything about risk-based security in general. Yusuf answers that it cannot establish general effects, but provides a tested measurement approach and an estimate that future pooled studies can use. A second examiner asks whether pseudonymised staff data posed risks. He explains the keyed pseudonyms, department-level reporting and destruction schedule. A third asks why he did not use incident counts; he explains that incidents are rare and inconsistently recorded, making them unreliable outcomes. Each answer is brief.
8.3 Outcome
The examiners pass the thesis with minor corrections: clarify the definition change made during the pilot and add a table comparing measures used in prior studies. They praise the pre-registration, independent validation and candid treatment of the inconclusive result. Yusuf makes the corrections within a month. He reflects that his most valuable contribution may be methodological, showing how operational logs can measure control effects, rather than any single estimate. The corrected thesis is approved by the internal examiner without further changes. Yusuf thanks Fernvale's security staff in his acknowledgements, naming no individual, as agreed in the original data sharing arrangement.
8.4 Publication plan
Yusuf plans three papers: the measurement method, the patch latency study with its power analysis and the access review study. Each will go to Fernvale's security lead for sensitivity review before submission, as agreed. He will publish synthetic data and code with each paper. He also plans a short practitioner note for council security teams. The next course in this area, data governance, examines how decision rights over data quality and use shape the evidence such security research relies on. Prof. Hald approves the plan.
Worked example
Yusuf presents mixed results side by side, answers challenges on generalisation, pseudonymisation and incident counts, passes with minor corrections and plans three papers and a practitioner note with sensitivity review.
Synthetic case. The defense is synthetic.
Errors and limits
Drifting into stronger language under questioning overstates the thesis.
Exercises
- EX045 — Side-by-side slide. What does the key slide show together? Rubric: 3 = the inconclusive patch result and the clearer privilege result;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX046 — Generalisation answer. What can one council's study provide? Rubric: 3 = a tested measurement approach and an estimate for pooling;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX047 — Incident counts. Why were incident counts not used? Rubric: 3 = rare and inconsistently recorded;; 2 = partly correct;; 1 = vague;; 0 = none.
- EX048 — Corrections required. Name one required correction. Rubric: 3 = clarify the pilot definition change or add a prior-measures table;; 2 = one;; 1 = vague;; 0 = none.
- EX049 — Paper count. How many papers does Yusuf plan? Rubric: 3 = three;; 2 = partly correct;; 1 = wrong;; 0 = none.
- EX050 — Key contribution. What may be Yusuf's most valuable contribution? Rubric: 3 = the methodological approach using operational logs;; 2 = partly correct;; 1 = vague;; 0 = none.
Continue studying — lesson 08 (chapter 08 of 08)
← Chapter 07 · Course chapter index · Next course via chapter index →
The chapter index leads to the next course in the study path.