Security alerts for medical devices
Compare a readable security classifier with a random forest using medical-device network traffic.
Technical
Bachelor’s · applied project
Final result
A documented classifier demo with specific performance and usability results.
Dataset · access required
CICIoMT2024: WiFi/MQTT attack CSVs
Use the publisher’s train/test split. Keep benign, DoS and reconnaissance traffic; remove labels and identifying fields from inputs.
What to do
- Implement a reproducible decision-tree classifier and an alert replay screen.
How it is tested
After securing CICIoMT2024 access, retain the publisher split; report benign/DoS recall and false alarms, then check basic responder tasks. Plan 4 participant sessions.
Before you start
Example tools · Python, pandas, scikit-learn, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Provider download form requires registration and currently reports a server error. Confirm access before selecting; recruit IT responders for the user study.
Research method · Build and test · 6 steps
- Read the starting sources and choose one established implementation method.
- Write the requirements, data fields, system diagram and test cases.
- Prepare CICIoMT2024: WiFi/MQTT attack CSVs. Make the answer key and pass criteria before testing.
- Build a working version of a documented classifier demo with specific performance and usability results.
- Run function, integration and failure-case tests. Record each result.
- Run the practical evaluation and list the changes the system still needs.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
Reproducible classifier comparison and alert viewer.
Dataset · access required
CICIoMT2024: WiFi/MQTT attack CSVs
Use the publisher’s train/test split. Keep benign, DoS and reconnaissance traffic; remove labels and identifying fields from inputs.
What to do
- Use a leakage-audited scikit-learn Pipeline with majority baseline, depth-5 balanced decision tree and a fully recorded 100-tree random forest.
- Enumerate excluded identifiers, hash duplicate rows and group splits by capture where metadata permits; replay fixed tree decisions with/without decision paths.
- Report macro-F1, per-class recall, benign false-positive rate, Brier/ECE and latency separately from responder escalation correctness, confidence and time.
How it is tested
Fit preprocessing on training data only; audit duplicates/leakage and report macro-F1, per-class recall, benign false-positive rate, Brier/ECE and preprocessing/prediction latency for majority, depth-5 tree and 100-tree forest. Replay fixed tree outputs with/without decision paths to 6 responders; score rubric-based interpretation, escalation, confidence and time.
Before you start
Example tools · Python, pandas, scikit-learn, Streamlit These are suggestions; equivalent tools are fine.
Access or people · Provider download form requires registration and currently reports a server error. Confirm access before selecting; recruit 6 IT responders for the user study.
Start with these three actions
- Open the CICIoMT2024 source link and obtain WiFi/MQTT attack CSVs and their published split.
- Inventory labels, identifiers, duplicates and class counts separately in training and test data.
- Fit a training-only preprocessing pipeline and benchmark one classifier before building the alert view.
Files, questions and sources
Pilot question: Do explanations of fixed security alerts improve responders’ interpretation and escalation reasoning?
Literature search: medical device security alert explanation analyst decisions
Empty CSV templates: data-plan.csv · evaluation.csv · literature-matrix.csv
Download starter instructionsResearch method · Design, build and test (DSR) · 7 steps
- Read the newest papers and list the closest existing systems.
- Write down the versions, fields, data split, case assignment, random seeds and correct answers for CICIoMT2024: WiFi/MQTT attack CSVs.
- Draw the user workflow, data model and system architecture. List the requirements and pass criteria.
- Build a working version of reproducible classifier comparison and alert viewer.
- Test every function, connection and failure case. Save the failed tests as well as the passed tests.
- Compare the system with the named alternative. Then run the user task or decision task in the assignment.
- Report the measured result, the failed cases and the design lessons another team can reuse.
Research question and sources
Research question: Separate classifier performance from responder usefulness. Audit the published split for leakage, compare tree/forest baselines, then test fixed-tree explanations under differing service impacts. A higher F1 alone is not the thesis contribution.
Research result: A reproducible table linking classifier evidence, analyst decisions and escalation outcomes.
Current project literature
- CICIoMT2024: A benchmark dataset for multi-protocol security assessment in IoMT (2024) peer-reviewed
Defines the exact contemporary dataset, attack taxonomy and benchmark context. - An interpretable dimensional reduction technique with an explainable model for detecting attacks in Internet of Medical Things devices (2025) peer-reviewed
Provides a current explainable baseline on CICIoMT2024 and motivates careful split auditing.
IS theory starting points
- Buçinca et al. (2021) — To Trust or to Think — Derive a competing explanation based on verification effort and overreliance.
- Vessey & Galletta (1991) — Cognitive Fit — Test whether a representation helps one kind of task more than another.
Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points.
Search terms: medical device security alert explanation analyst decisions
Non-technical
Bachelor’s · applied project
Final result
An incident checklist and clear escalation requirements.
Dataset + material
12 incident cards based on CICIoMT2024
Create 4 benign, 4 DoS and 4 reconnaissance cards, each with an explicitly fictional service impact.
What to do
- Find what an IT responder needs before escalating an incident.
How it is tested
Use the fictional incident cards in 4 responder interviews; organise evidence and escalation steps.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit responders; the service context must be created.
Research method · Study and improve · 6 steps
- Read the starting sources and write the exact information problem.
- Prepare 12 incident cards based on CICIoMT2024 and a separate answer sheet or coding sheet.
- Run one pilot and fix unclear questions.
- Collect the named evidence with consent.
- Group the findings with the stated categories and check the answer sheet.
- Produce an incident checklist and clear escalation requirements. List the three most useful changes.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
A table linking evidence to each escalation decision, plus a revised incident-report form.
Dataset + material
12 incident cards + 12 cross-role interviews
Create 4 benign, 4 DoS and 4 reconnaissance cards with explicitly fictional service impacts. Recruit 6 security responders and 6 medical-device or service owners; each reviews 6 balanced cards.
What to do
- Turn published attack categories into paper incident reports.
- Interview IT responders about which evidence they need before escalating.
How it is tested
Compare per-person escalation, requested evidence and uncertainty across roles and incident types. Code technical evidence, service impact, verification cost and the technological-frame domains nature, strategy and technology-in-use.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit 6 security responders and 6 medical-device or service owners; create and independently review the fictional service context.
Start with these three actions
- Prepare a pilot with 2 examples from: 12 incident cards based on CICIoMT2024. Write the task questions and a reference answer sheet.
- Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact.
- Pilot one session after approval; revise unclear questions, finalise the task sets and coding categories, then recruit the planned sample.
Files, questions and sources
Pilot question: Which device and service facts do responders need before escalating an incident?
Literature search: medical device security alert explanation analyst decisions qualitative scenario study
Interview prompts
- Would you investigate, monitor or escalate this report?
- Which evidence supports that choice?
- What service information is missing?
Empty CSV templates: study-plan.csv · coding-sheet.csv · literature-matrix.csv
Download starter instructionsResearch method · Study, compare and explain · 7 steps
- Read the newest papers and write one exact research question.
- State which people, cases or documents you will study and what you will compare.
- Write the selection rules, questions and analysis steps for 12 incident cards + 12 cross-role interviews.
- Run one pilot. Fix unclear questions or categories, then keep the guide unchanged.
- Collect the named interviews, cases or documents with consent.
- Analyse them with the stated comparison or coding method. Keep disagreements and missing data.
- Report the answer, the evidence and the practical output named in the assignment.
Research question and sources
Research question: Explain why security evidence sufficient for one role is insufficient for another. Contrast technical and service-impact reasoning, using identical incidents to examine role interpretations and verification costs.
Research result: A specific evidence-to-escalation framework with cross-role exception cases.
Current project literature
- CICIoMT2024: A benchmark dataset for multi-protocol security assessment in IoMT (2024) peer-reviewed
Defines the exact contemporary dataset, attack taxonomy and benchmark context. - An interpretable dimensional reduction technique with an explainable model for detecting attacks in Internet of Medical Things devices (2025) peer-reviewed
Provides a current explainable baseline on CICIoMT2024 and motivates careful split auditing.
IS theory starting points
- Orlikowski & Gash (1994) — Technological Frames — Compare how roles interpret the purpose, operation and use of the same system.
- Vasconcelos et al. (2023) — Explanations Can Reduce Overreliance — Compare verification cost with trust as explanations of observed decisions.
Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points.
Search terms: medical device security alert explanation analyst decisions qualitative scenario study
Your degree, track and shortlist are saved in this browser.