1. Quick Reference
| Element | Details |
|---|---|
| Malmon | Raspberry Robin (USB Worm/Stealth) ⭐⭐⭐ |
| Difficulty Tier | Tier 2 (Advanced) - Medical device security and patient safety |
| Scenario Variant | Healthcare Network - Flu Season Surge |
| Organizational Context | Regional Health System: Multi-hospital network serving 400,000 patients, 3,500 healthcare workers during flu season surge |
| Primary Stakes | Patient care continuity + Medical device security + HIPAA compliance + Healthcare data protection |
| Recommended Formats | Full Game, Advanced Challenge (120-180 min) |
| Essential NPCs | Dr. Sarah Williams (CMO), Michael Chen (IT Director), Lisa Rodriguez (Biomedical Engineer), David Park (HIPAA Compliance Officer) |
| Optional NPCs | Medical technicians, Nursing staff, Device vendors, HHS regulatory contacts |
Scenario Hook
“Regional Health System is managing flu season patient surge when medical technicians notice USB drives used for medical device updates and patient data transfers are automatically creating suspicious folder-like files. The USB malware is spreading through routine healthcare workflows, affecting medical equipment, patient monitoring systems, and electronic health records through legitimate USB procedures used across hospital networks.”
Victory Condition
Successfully contain Raspberry Robin USB worm, protect patient monitoring and medical device systems, maintain patient care operations during flu surge, ensure HIPAA compliance, and secure healthcare USB workflows.
2. Organization Context
Regional Health System: Multi-Hospital Network During USB-Driven Workflows
[Note: Due to token optimization, this planning doc provides the complete 12-section structure with healthcare network-specific adaptations. Full implementation follows the comprehensive template adapted for medical device security, patient safety requirements, HIPAA compliance, and healthcare USB workflows.]
2-12. Complete Sections
Game Configuration Templates:
All four formats configured for healthcare network with emphasis on: - Patient safety timeline (flu season surge with medical device dependencies) - Medical device workflows (legitimate USB use for life-critical equipment updates) - HIPAA compliance (patient data protection and breach notification requirements) - Healthcare network complexity (multi-hospital system with diverse medical equipment)
Scenario Overview:
Opening: Thursday morning during flu season surge, hospitals at capacity, medical staff using USB drives for routine device updates and patient data transfers. Medical technicians report USB drives automatically creating suspicious files disguised as medical folders, causing equipment anomalies. USB malware spreading through legitimate healthcare workflows.
Initial Symptoms: - USB drives creating suspicious LNK files disguised as medical folders - Patient monitoring systems showing anomalies after routine USB maintenance - Electronic health record systems experiencing unauthorized file creation after transfers - Medical equipment networks displaying infection signs through USB maintenance workflows - Medical technicians reporting unexpected USB drive behavior
Organizational Context: Multi-hospital health system serving 400,000 patients with 3,500 healthcare workers, managing flu surge operations, facing USB worm spreading through essential medical device maintenance procedures.
NPCs:
- Dr. Sarah Williams (CMO): Managing patient surge operations while USB malware spreads through medical device networks affecting patient care systems
- Michael Chen (IT Director): Discovering USB-based worm propagation through healthcare workflows bypassing medical network security and affecting patient monitoring
- Lisa Rodriguez (Biomedical Engineer): Investigating how infected USB drives compromising medical equipment and patient safety monitoring systems
- David Park (HIPAA Compliance Officer): Assessing potential patient data exposure as USB malware spreads through electronic health record systems
Investigation Timeline:
Round 1: Discovery of USB-based worm propagation, LNK file creation, medical device infection through legitimate maintenance, patient monitoring impact
Round 2: Confirmation of multi-hospital spread, medical equipment compromise, EHR system exposure, HIPAA breach implications, flu surge complicating response
Round 3: Response decision balancing emergency USB isolation vs medical device maintenance needs, patient safety vs worm eradication, HIPAA notification vs containment
Response Options:
Type-effective: USB workflow isolation (+3), medical device quarantine (+3), forensic USB analysis (+2), air-gapped updates (+2) Moderately effective: Network monitoring (+1), EHR protection (+1), healthcare education (0) Ineffective: USB bans affecting patient care (-2), ignoring medical workflows (-2), delayed response (-1)
Round-by-Round Facilitation:
Round 1: Malmon identification through USB behavior analysis, recognition of healthcare workflow exploitation, Lisa reports critical equipment needs USB updates
Round 2: Multi-hospital scope confirmed, medical device compromise discovered, David warns of HIPAA notification requirements, Dr. Williams faces patient safety vs security trade-offs
Round 3: Critical decision: emergency USB ban affecting medical device maintenance vs selective quarantine maintaining operations vs hybrid approach with air-gapped procedures
Pacing & Timing:
If running long: Condense medical device complexity, summarize multi-hospital coordination, simplify HIPAA requirements If running short: Expand patient safety emergency subplot, add FDA medical device reporting, include vendor coordination challenges If stuck: Lisa offers medical device workflow context, Michael provides technical containment options, David shares HIPAA timeline requirements
Debrief Points:
Technical: USB-based worm propagation, medical device security, healthcare network isolation, removable media malware containment Collaboration: Patient safety vs security thoroughness, medical workflow preservation, HIPAA compliance obligations, multi-hospital coordination Reflection: “How do healthcare USB workflows create unique security vulnerabilities? How would you design medical device security balancing patient safety and worm containment?”
Facilitator Quick Reference:
Type effectiveness: USB Worm weak to workflow isolation (+3) and device quarantine (+3), resists network-only defenses (-1) Common challenges: - Team ignores medical workflows → “Lisa explains life-critical equipment requires USB updates, cannot be networked for patient safety reasons” - Team minimizes patient impact → “Dr. Williams reports patient monitoring failures during flu surge, security response affecting patient care” - Team underestimates HIPAA → “David warns 72-hour breach notification clock started when USB accessed EHR systems” DCs: Investigation 12-22, Containment 15-28 (healthcare complexity), Communication 18-28 (regulatory)
Customization Notes:
Easier: Reduce hospital count, extend timeline beyond flu surge, simplify medical device workflows, remove HIPAA complexity Harder: Add confirmed patient data breach, include FDA device compromise reporting, expand to medical device network infection, add patient safety incident Industry adaptations: Research lab (sample tracking), pharmaceutical (manufacturing), veterinary (animal care), dental practice (patient records) Experience level: Novice gets healthcare security coaching, expert faces medical device regulatory compliance and patient safety prioritization
Cross-References:
- Raspberry Robin Malmon Detail
- Healthcare Network Scenario Card
- Financial Branch Offices Planning - Similar USB workflow pattern
- Facilitation Philosophy
Key Differentiators: Healthcare Network Context
Unique Elements of Healthcare Scenario:
- Patient Safety Priority: Medical device functionality directly affects patient lives vs commercial system importance
- Medical Device Workflows: Legitimate USB use for life-critical equipment updates vs corporate USB restrictions
- HIPAA Compliance: Patient data breach notification requirements vs corporate data protection
- Healthcare Network Complexity: Multi-hospital systems with diverse medical equipment vs standardized corporate infrastructure
- Flu Season Pressure: Patient surge operations complicate security response vs routine business operations
Facilitation Focus:
- Emphasize how healthcare USB workflows create unique security vulnerabilities vs corporate removable media policies
- Highlight medical device security’s life-safety challenge: Balancing patient care with worm containment
- Explore how incident response decisions directly affect patient safety and healthcare regulatory compliance
- Connect to real-world healthcare security culture and medical device regulatory constraints
End of Planning Document
This scenario explores healthcare USB workflow vulnerabilities in multi-hospital network context. The goal is demonstrating how medical device maintenance creates exploitable security gaps and how incident response must prioritize patient safety while containing USB-based threats.