Chapter 40 — Thesis and presentation
Lesson map
Lesson 40 published. Map, example, EX118.
flowchart TD
N0["Learning outcomes"]
N1["40.1 Thesis"]
N2["40.2 Presentation"]
N3["40.3 Questions"]
N4["40.4 Reflection"]
N5["40.5 Next"]
N6["Looking back"]
N7["Career reflections"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX118"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["40.1 Thesis"]
N2["40.2 Presentation"]
N3["40.3 Questions"]
N4["40.4 Reflection"]
N5["40.5 Next"]
N6["Looking back"]
N7["Career reflections"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX118"]
[Learning outcomes]
|
v
[40.1 Thesis]
|
v
[40.2 Presentation]
|
v
[40.3 Questions]
|
v
[40.4 Reflection]
|
v
[40.5 Next]
|
v
[Looking back]
|
v
[Career reflections]
|
v
[Worked example] --> [Exercise EX118]
Learning outcomes
You will (1) write and present the capstone; (2) reflect on learning; (3) plan next steps.
40.1 Thesis
Problem, baseline, design, implementation, evaluation, limits.
The thesis follows the project's own path: the stolen laptop as the problem, the baseline of 32 of 45 encrypted, the layered design, the staged implementation, the before-and-after evaluation and the stated limits. Each chapter of the dissertation points to the evidence files and lab outputs behind its figures, which sit in the appendices with the synthetic data. The limits chapter names non-reporting devices as the weakness that most worried her, and explains how each table counts them.
40.2 Presentation
Aisha presents to Thornbury and Bramley.
The presentation is given twice, once to examiners at Thornbury and once to Bramley's staff and managers. For Bramley, Aisha uses the one-page board summary and the bar chart of four before-and-after measures. For Thornbury, she adds the method, the reminder study and the limits, because examiners will test how the figures were produced. She rehearses with Gareth playing a sceptical board member, which leads her to add a line showing staff hours. Both audiences receive the same figures, with different levels of detail.
40.3 Questions
About cost, staff acceptance and sustainability.
On cost, Aisha points to roughly 60 hours of Gareth's time over the project and about one hour a week afterwards. On staff acceptance, she cites the falling help requests during rollout and the survey, while noting its few responses. On sustainability, she shows the routine running every week at the six-week check after handover. Asked what happens if Gareth leaves, she points to the documented routine and the trained colleague. Each answer uses figures already reported in the evaluation chapter.
40.4 Reflection
She learned that small organisations need simple, well-run controls more than advanced tools.
Aisha's evidence supports this reflection: most gains came from encrypting all laptops, removing local admin rights, forcing restarts and reconciling the inventory, using tools Bramley already had. The update failure analysis showed that a new patch tool would not have fixed the main causes. She also notes what she would change: involving staff earlier and allowing more time to check with users. Simple controls, run every week, did most of the work at Bramley.
40.5 Next
She plans graduate study in systems security.
Her interest in graduate study comes from the topics her capstone left open, such as firmware integrity, which she read about through NIST SP 800-193. She also wants to study how small organisations keep routines running without specialist staff. Before leaving, she confirms the deletion of her copies of Bramley's exports, as the agreement requires. She also leaves Bramley a short list of the follow-ups she proposed, with phone management at the top. Gareth keeps her contact details for questions about the labs.
Looking back
At the end, Aisha reviews the journey from the stolen laptop to a measured, maintained fleet. The key lessons are simple: know your devices, set and keep a baseline, update in time, encrypt, keep only needed services, review logs lightly and test recovery. None of these is new, but doing them consistently in a small organisation takes planning and patience.
She credits Gareth and Bramley's staff, whose cooperation made the changes stick. She also notes what she would do differently: involve staff earlier and plan more time for checking with users.
The dissertation is submitted on time, and Bramley keeps the routine running after she leaves.
Career reflections
Aisha considers roles in IT operations and security, and notes the value of being able to explain technical work to boards.
Future work
Extending management to phones is the top recommendation.
Thanks
She thanks her tutor, Gareth and the staff.
Final message
The final message to Bramley is that security is maintained, not finished. The routine, owners and review dates keep the work alive, and the board update keeps it visible. Aisha closes by noting that the stolen laptop, painful at the time, became the reason Bramley's endpoints are now well managed.
Project log entry
At the presentation, examiners ask what she would recommend to an organisation with no IT officer. She suggests a managed service with the same routine written into the contract, so the checks still happen and are still reported.
Worked example
Gareth says the weekly routine is now part of his job description.
Synthetic case. Synthetic.
Errors and limits
Reflection should be specific.
Exercises
- EX118 — Structure. Give the thesis structure. Rubric: 3 = problem, baseline, design, implementation, evaluation, limits; 2 = four; 1 = two; 0 = none.
- EX119 — Questions. What topics were asked? Rubric: 3 = cost, acceptance, sustainability; 2 = two; 1 = one; 0 = none.
- EX120 — Lesson. What did Aisha learn? Rubric: 3 = simple well-run controls over advanced tools; 2 = partial; 1 = vague; 0 = none.
Synthesis
Present results and reflect specifically.
Continue studying — chapter 40 of 40
← Chapter 39 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →