Security alerts for medical devices — Non-technical https://thesis.uya.no/proposals/beyond-the-security-alert/#nontechnical-track BACHELOR Final result: An incident checklist and clear escalation requirements. Task: Find what an IT responder needs before escalating an incident. Data: 12 incident cards based on CICIoMT2024 (mixed) Create 4 benign, 4 DoS and 4 reconnaissance cards, each with an explicitly fictional service impact. Requires: Recruit responders; the service context must be created. Method: Use the fictional incident cards in 4 responder interviews; organise evidence and escalation steps. STEPS Study and improve 1. Read the starting sources and write the exact information problem. 2. Prepare 12 incident cards based on CICIoMT2024 and a separate answer sheet or coding sheet. 3. Run one pilot and fix unclear questions. 4. Collect the named evidence with consent. 5. Group the findings with the stated categories and check the answer sheet. 6. Produce an incident checklist and clear escalation requirements. List the three most useful changes. MASTER Final result: A table linking evidence to each escalation decision, plus a revised incident-report form. 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. STEPS Study, compare and explain 1. Read the newest papers and write one exact research question. 2. State which people, cases or documents you will study and what you will compare. 3. Write the selection rules, questions and analysis steps for 12 incident cards + 12 cross-role interviews. 4. Run one pilot. Fix unclear questions or categories, then keep the guide unchanged. 5. Collect the named interviews, cases or documents with consent. 6. Analyse them with the stated comparison or coding method. Keep disagreements and missing data. 7. Report the answer, the evidence and the practical output named in the assignment. CURRENT PROJECT LITERATURE CICIoMT2024: A benchmark dataset for multi-protocol security assessment in IoMT (2024, peer-reviewed): https://doi.org/10.1016/j.iot.2024.101351 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): https://doi.org/10.1038/s41598-025-93404-8 Provides a current explainable baseline on CICIoMT2024 and motivates careful split auditing. IS THEORY STARTING POINTS Orlikowski & Gash (1994) — Technological Frames: https://dl.acm.org/doi/10.1145/196734.196745 Compare how roles interpret the purpose, operation and use of the same system. Vasconcelos et al. (2023) — Explanations Can Reduce Overreliance: https://doi.org/10.1145/3579605 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. PILOT QUESTION Which device and service facts do responders need before escalating an incident? EXAMPLE TOOLS LibreOffice Writer/Calc, audio recorder with consent; no programming required. Equivalent tools are fine. FIRST THREE ACTIONS 1. Prepare a pilot with 2 examples from: 12 incident cards based on CICIoMT2024. Write the task questions and a reference answer sheet. 2. Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact. 3. Pilot one session after approval; revise unclear questions, finalise the task sets and coding categories, then recruit the planned sample. INTERVIEW QUESTIONS - Would you investigate, monitor or escalate this report? - Which evidence supports that choice? - What service information is missing? LITERATURE SEARCH medical device security alert explanation analyst decisions qualitative scenario study DATA 12 incident cards + 12 cross-role interviews (mixed) 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. CICIoMT2024: https://www.unb.ca/cic/datasets/iomt-dataset-2024.html HOW TO TEST IT 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. FINAL RESULT A table linking evidence to each escalation decision, plus a revised incident-report form. ACCESS OR PEOPLE Recruit 6 security responders and 6 medical-device or service owners; create and independently review the fictional service context. TEMPLATES https://thesis.uya.no/starters/beyond-the-security-alert/nontechnical/study-plan.csv https://thesis.uya.no/starters/beyond-the-security-alert/nontechnical/coding-sheet.csv https://thesis.uya.no/starters/beyond-the-security-alert/nontechnical/literature-matrix.csv Use participant codes instead of names or email addresses.