IoMT Risk Education Platform — v3.0

Digital
First
Responder
Lab

Where connected medical systems, clinical AI, and athlete biometric technology actually fail — not in theory, but in the moment when the decision still has to be made. Built from 28 years of clinical reality and lived device dependency.

9
Failure Scenarios
0
Hypothetical Cases
28+
Years Clinical Experience
2
Sectors: Health + Sports Tech
Health Technology Education — Student Edition

Can You
Keep the
Patient
Safe?

Hospitals and homes are full of connected devices that keep people alive. What happens when those devices fail — or get hacked? Explore real scenarios and make real decisions.

3
Real Scenarios to Explore
4
Choices Per Scenario
Things to Learn
Scroll to explore
Core Philosophy

Welcome, Future Health Tech Defenders 👋

This lab was built by Ms. Chaunda — a real healthcare cybersecurity consultant who spent 28 years working in emergency rooms, and who also depends on connected medical devices every single day to stay healthy. The scenarios you're about to explore are REAL situations. Your job is to think like both a clinician and a security analyst. Are you ready?

At 2am in the ER, I'm not waiting on a dashboard. Healthcare doesn't pause for data validation. Our security frameworks need to stop assuming it does.

Imagine you're a nurse at 2am. A patient needs help right now. You don't have time to wait for a computer to tell you what to do. You have to make a decision in seconds. That's why health technology security matters — people's lives depend on it working correctly.

Most healthcare cybersecurity focuses on protecting data. This lab focuses on what happens when the technology keeping a person alive fails — in real time, under real conditions, with real consequences that no framework fully accounts for.

I never left healthcare. I learned to defend it. I teach it, I live it, I build it, and I'm learning how attackers see it — so I can protect patients better than anyone who only knows one side.

First — What Are Connected Medical Devices?

🫙
Oxygen Concentrators
Machines that pull oxygen from the air and deliver it to patients who can't breathe well on their own. Some connect to WiFi so doctors can check on them remotely.
💉
Infusion Pumps
Devices that deliver medication directly into a patient's bloodstream at a precise rate. Many are now connected to hospital networks — which means they can be hacked.
🧠
AI Decision Systems
Computer programs that help doctors and nurses make decisions by analyzing patient data. But what happens when the AI gets it wrong?
Wearable Monitors
Smartwatches and fitness trackers that measure heart rate, oxygen levels, and sleep. Some hospitals use this data to make medical decisions.
😴
CPAP Machines
Devices that help people breathe while they sleep. Modern CPAPs connect to the internet and can receive software updates remotely — just like your phone.
🏥
Hospital Networks
All of these devices connect to hospital WiFi networks. If a hacker gets into the network, they could potentially reach every connected device in the building.
Failure Scenarios Real-World Scenarios — Click to Explore
01 / SCENARIO
Silent Battery Failure
Portable O₂ Concentrator
Critical

Battery indicator reports full charge. Device loses power within minutes. No backup source. Power infrastructure unstable.

A machine that helps someone breathe says its battery is full — but it's not. When the power goes out, the machine stops working after less than 3 minutes. What went wrong?

🫙 About This Device

A portable oxygen concentrator pulls oxygen from the air and delivers it through a tube to someone who needs help breathing. People with pulmonary hypertension (PAH) depend on these 24/7. The device this scenario is based on is real — it belongs to the person who built this lab.

What Went Wrong — Step by Step

1
False state reporting. Battery shows full. Actual runtime: 2–3 minutes.
The battery lied. It said it was full, but it was actually almost dead.
2
No verification protocol. Patient trusts the indicator. No alert threshold configured.
There was no system to double-check the battery or send an alert.
3
Power outage occurs. Grid failure. AC disconnected.
A storm knocked out the electricity. The device switched to battery — which only lasted about 2 minutes.
4
No backup exists. No second device. No escalation path.
There was no backup oxygen tank and no second device.
5
Oxygen deprivation begins silently. PAH + hypoxia. Cascading failure.
Without oxygen, the patient's condition got worse quickly at night with no one knowing.

Framework Gaps

NIST 800-53 SI-13NIST AI RMF MANAGE 2.2HIPAA §164.310(a)(2)(i)FDA 21 CFR Part 820IEC 62443-4-2 CR 3.1Home Care Redundancy Gap

Think About It

If this were a smartphone, we'd expect a low battery warning at 20%, 10%, and 5%. Why don't life-critical medical devices have the same protections?

What Should Exist

Real-time battery health telemetry with verified discharge testing. Mandatory backup protocols for single-source oxygen-dependent patients. Infrastructure dependency mapping for high-risk home medical devices. Emergency registry enrollment at local utility and fire department level.

The device should send a real warning when battery health is low. Patients who depend on oxygen 24/7 should always have a backup plan. Local fire departments should know which homes have oxygen-dependent patients.

02 / SCENARIO
AI Triage Override
Emergency Department
Critical

AI triage scores patient low acuity. Clinician overrides based on observation. System flags the override as anomalous.

A computer program says a patient isn't very sick. But the nurse can see something is wrong. She overrides the computer — and turns out to be right. But then the computer marks her decision as a mistake. Who was actually wrong?

🧠 About AI Triage Systems

Hospitals use AI programs to help decide which patients need care the fastest. The AI reads structured data — like test results and typed symptoms. But it can't see what a trained nurse sees: skin color, work of breathing, whether a patient looks scared. That's called clinical intuition — and it takes years to develop.

What Went Wrong — Step by Step

1
Model scores low risk. Misses nonverbal cues: skin color, work of breathing, diaphoresis.
The AI said the patient was fine — but couldn't see the patient was pale, sweating, and struggling to breathe.
2
Clinician escalates immediately. Patient is actually critical.
The nurse trusted what she saw and got the patient help right away.
3
System flags override as deviation. Algorithm treats expert judgment as error.
The computer marked the nurse's correct decision as a "mistake."
4
Override used for retraining. Model learns wrong lesson.
The computer "learned" from the override — the wrong lesson, making it worse at catching sick patients.

Framework Gaps

NIST AI RMF GOVERN 1.1NIST AI RMF MAP 3.5FDA AI/ML Action PlanONC HTI-1 RuleHuman Oversight Gap

Big Question

Should a computer ever be able to overrule a trained medical professional? What should the relationship between AI and human experts look like in healthcare?

What Should Exist

Override logging that distinguishes expert judgment from error. Model retraining governance requiring human review. Mandatory human-in-the-loop thresholds for high-acuity clinical AI. Regular red-team exercises against experienced clinician baseline.

The computer should recognize when an experienced nurse overrides its decision and treat that as valuable information — not a mistake. AI in healthcare should always support human experts, never replace them.

03 / SCENARIO
Infusion Pump
Network Compromise
High

Networked pump receives unauthorized parameter update during active medication delivery. Nurse managing four other patients simultaneously.

A hacker gets into the hospital's network and changes the settings on a machine giving a patient medicine. The nurse is too busy to notice right away.

💉 About Infusion Pumps

An infusion pump delivers medicine directly into a patient's bloodstream at a precise rate. Getting the rate wrong by even a small amount can be dangerous. Modern pumps connect to hospital networks so nurses can update settings centrally. That convenience also creates a security risk.

What Went Wrong — Step by Step

1
Pump on clinical network. Update mechanism lacks authentication. Lateral movement from prior breach.
The pump was connected to the hospital's network, but there was no security checking who was allowed to change its settings.
2
Unauthorized parameter pushed. Change within acceptable range. No alarm fires.
A hacker changed the medicine delivery rate. The change was small enough that the alarm didn't go off.
3
Nurse managing four patients. Visual check interval 20+ minutes.
The nurse was caring for four other patients and couldn't check for over 20 minutes.
4
Wrong dose delivered over time. Subtle deterioration.
By the time anyone noticed, the patient had been receiving the wrong amount of medicine for a long time.

Framework Gaps

NIST 800-82 Rev 3FDA Cyber Guidance 2023HIPAA §164.312(b)IEC 80001-1Network Segmentation Gap

Connect the Dots

This is why healthcare cybersecurity isn't just about protecting data — it's about protecting people's lives. A hacker in a hospital network could change how medicine is delivered to patients.

What Should Exist

Mutual TLS authentication for all pump updates. Real-time anomaly detection on rate changes. Clinical workflow-aware alerting. Mandatory FDA MedWatch reporting integration.

The pump should require a verified key before anyone — or any computer — can change its settings. Any change should immediately alert the nurse at the bedside.

04 / SCENARIO
OSINT Recon on
Hospital Infrastructure
High

Before attackers touch a network, they watch it. What they find in 30 minutes would surprise most security teams.

In Development
05 / SCENARIO
Wearable Data Spoofing
Athlete & Patient Dual Perspective
High

Your Apple Watch says you're fine. The clinical system believes it. The coach clears you to play. You are not fine. Two perspectives — same failure, different stakes.

Smartwatches and fitness trackers measure your heart rate, oxygen levels, and activity. But what if someone could fake that data? What decisions would get made based on wrong information?

🏈 Sports Tech Bridge Scenario

This is the scenario that bridges healthcare and sports technology. Same device. Same biometric data. Two entirely different contexts — both with life-threatening stakes. The gap between consumer wearable and clinical medical device is where attackers operate, and where no current framework draws a clear line. See the full Sports Tech lane →

⏰ About Wearable Health Devices

Consumer wearables like the Apple Watch now include medical-grade sensors — ECG, blood oxygen (SpO2), heart rate variability, fall detection, and irregular rhythm notifications. These devices are increasingly used in clinical decision-making and athlete performance monitoring. The data they generate is trusted. That trust is the attack surface.

Failure Chain — Perspective 1: The Clinician

1
Patient enrolled in remote monitoring program. Apple Watch syncs health data to EHR via HealthKit. Clinician reviews wearable data between appointments.
The patient's Apple Watch automatically sends health data to their doctor.
2
Data transmission intercepted. Spoofed biometric values injected — falsely normal heart rate, falsely normal SpO2.
An attacker intercepts the data and replaces it with fake normal numbers.
3
Clinical decision made on false baseline. Medication adjusted downward. Follow-up deferred. Warning signs masked.
Based on fake data, the doctor reduces medication and pushes back the next appointment.
4
Patient deteriorates without clinical awareness. No alert fires. Emergency presentation follows.
The patient keeps getting worse. The doctor doesn't know because the data looks fine.

Failure Chain — Perspective 2: The Athlete

1
Elite athlete uses wearable for performance monitoring. Data feeds team health management system. Clearance decisions based on biometric thresholds.
A college or pro athlete wears a health tracker. Their coach and team doctor use the data to decide if they're healthy enough to play.
2
Wearable data spoofed to show false fitness. Recovery metrics falsified. System clears athlete for full competition.
The wearable data is manipulated to make it look like the athlete is fully recovered — even though they're not ready.
3
Athlete competes while physiologically compromised. Underlying cardiac stress undetected. No human override occurs.
The athlete plays while their body isn't ready. The technology said they were fine.
4
Cardiac event during competition. Spoofed data masked the warning signs that should have kept this athlete off the field.
The athlete collapses during the game. Technology that was supposed to save lives contributed to the harm.

Framework Gaps

FDA Digital Health Policy (Consumer Wearables)NIST AI RMF MAP 3.5HIPAA §164.312 (Transmission Security)No Wearable Data Integrity StandardHealthKit API Security GapSports Medicine Technology GapConsumer Device to Clinical Use Boundary Gap

What Should Exist

Data integrity verification at every point in the wearable-to-EHR pipeline — not just transmission encryption, but authenticity verification of the data itself. Clear regulatory boundaries on when consumer wearable data can be used for clinical decision-making. Anomaly detection that compares wearable data against in-person vitals. Sports medicine protocols that require human clinical confirmation before automated clearance decisions. The gap between consumer wellness device and clinical medical device is where attackers live — and no current framework addresses it adequately.

Any data used to make medical decisions needs to be verified as real — not just transmitted securely, but confirmed as authentic. A doctor or athletic trainer should never rely solely on wearable data without a human check. This is a career opportunity for the next generation of health technology professionals.

06 / SCENARIO
Ransomware in the ER
The 2am Decision
Critical

The EHR is locked. The patient is crashing. 90 seconds. No medication history. This is not a drill.

In Development
07 / SCENARIO
CPAP Firmware Vulnerability
ResMed AirSense 11
Critical

Connected to the internet. Receives automatic firmware updates via the myAir remote monitoring platform. Documented CVEs exist on this exact device. The patient depending on it is also the analyst who built this lab.

A CPAP machine that helps someone breathe at night connects to the internet to send sleep data to doctors. But that same connection can also receive software updates — and if an attacker gets in, they could change how the device works while the patient is asleep.

😴 About This Device

The ResMed AirSense 11 AutoSet is a CPAP machine that connects to ResMed's myAir cloud platform via cellular or WiFi. It transmits nightly sleep therapy data and can receive remote configuration changes from clinicians. It also receives automatic firmware updates. This scenario is built from the actual device used by the person who created this lab.

Failure Chain

1
Device connected to myAir cloud platform. Cellular modem embedded. Remote monitoring active. Automatic firmware update channel open.
The CPAP connects to the internet every night to send sleep data. That same connection can receive updates.
2
Firmware update channel lacks robust authentication. Documented CVEs on ResMed ecosystem. Update accepted without patient notification or consent.
Researchers have found security weaknesses in how ResMed devices accept updates. An attacker could push a fake update silently.
3
Malicious firmware pushed during sleep window. Patient asleep. Device behavior altered silently — pressure settings, therapy modes, alarm thresholds.
The attack happens at 2am while the patient is asleep. The device quietly changes how it works. No alarm.
4
Therapy degraded without clinical detection. myAir data still transmits normally. Clinician sees clean data.
The sleep data being sent to the doctor looks normal — but the actual therapy has changed.
5
PAH patient with compromised nightly therapy. Degraded CPAP therapy directly impacts cardiovascular strain and oxygen saturation.
For someone with pulmonary hypertension, even one night of wrong therapy can cause real health consequences.

Framework Gaps

FDA Cybersecurity Guidance 2023IEC 62443-4-2 CR 3.4NIST 800-53 SI-7NIST 800-53 SA-10HIPAA §164.312(a)(2)(iv)No Patient Consent Standard for Remote UpdatesHome Device Monitoring Gap

The Personal Connection

The person who built this lab uses a ResMed AirSense 11 every night. She also has pulmonary hypertension that makes breathing more difficult. This scenario isn't theoretical — it's personal. That's what makes healthcare cybersecurity different from any other security work.

What Should Exist

Mandatory patient notification and consent before any remote firmware update on a home medical device. Cryptographic code signing with independent verification before update acceptance. Anomaly detection on therapy parameter changes post-update. FDA-mandated Software Bill of Materials (SBOM) for all connected home medical devices. Patient-accessible audit log of all remote device interactions.

Before any medical device gets a software update while a patient is using it, the patient should be notified and agree — just like how your phone asks before installing updates. The update should be verified as coming from the real manufacturer.

08 / SCENARIO
Dementia Home Health
Technology Failure Chain
Critical

A cognitively impaired patient living at home relies on a connected ecosystem of smart sensors, GPS tracking, automated medication dispensers, and telehealth platforms. Each device is a lifeline. Each connection is a potential failure point. The patient cannot self-advocate when the system fails.

More people with memory conditions like Alzheimer's can live at home with connected devices. But what happens when those devices fail, get hacked, or stop working? The patient often can't tell anyone something is wrong.

🧠 The Connected Dementia Care Ecosystem

According to the 2025 WHO report on dementia and digital health, AI-powered diagnostic tools, smart home monitoring sensors, GPS tracking devices, telehealth platforms, automated medication dispensers, and robotic companion devices are now core components of modern dementia home care. These technologies are almost entirely unsecured from a cybersecurity standpoint.

Failure Chain

1
Ecosystem dependency established. Smart sensors, GPS, automated dispenser, telehealth. All connected. All networked. None secured.
The patient's whole safety system runs on connected devices — all on WiFi.
2
Single network compromise cascades across all devices. Home router exploited. Sensor data manipulated. Medication schedule altered. GPS spoofed.
If a hacker gets into the home WiFi, they can reach every device at once.
3
Patient cannot self-report the failure. Short-term memory impairment. No self-advocacy. No internal alarm system.
Someone with dementia may not realize something is wrong — or may forget to tell someone even if they do notice.
4
Remote caregiver receives false normal data. Clean dashboards. No alerts. No anomalies. No reason to intervene.
The family members checking in remotely see everything looks fine — because devices are showing false data.
5
Delayed detection. Preventable harm. Fall not detected. Medication missed or doubled. Wandering event not caught.
By the time someone realizes something is wrong, it may have been hours.

Framework Gaps

FDA Digital Health Policy (Home Devices)NIST 800-53 SC-3HIPAA §164.308 (Admin Safeguards)NIST AI RMF GOVERN 6.1No Home IoMT Security StandardCaregiver Alert Integrity GapWHO 2025 Digital Dementia Care GapVulnerable Population Protection Gap

Why This Matters

According to the WHO, over 55 million people worldwide live with dementia. This is one of the most important unsolved problems in healthcare cybersecurity today — and almost nobody is working on it.

What Should Exist

A dedicated security framework for connected home care ecosystems serving cognitively impaired patients — distinct from hospital IoMT frameworks because the patient cannot self-advocate. Mandatory network segmentation between home care devices and general household WiFi. Caregiver alert integrity verification. The 2025 WHO report on digital dementia care identified connected monitoring as transformative — but makes no mention of cybersecurity. That gap is the problem.

Home care devices for people with dementia need their own security rules — because the patient can't tell anyone when something goes wrong. Right now, very few people are working on this problem. That could be you.

09 / SCENARIO
CGM Signal Compromise
Dexcom G7
Critical

A compromised continuous glucose monitor transmits falsely normal readings. An endocrinologist makes an insulin dosing decision on manipulated data. The patient never knew the signal was wrong.

Coming Fall 2026
Decision Mode Your Turn — Make the Call

You Are The Responder.

What Would You Do?

Select a scenario — read the situation — make the call.

Read the situation carefully. Pick the best response. Learn from every answer.

0
Correct Decisions
Your Response
Healthcare Ransomware Intelligence

Healthcare Ransomware
Incident Tracker

Real incidents. Real patient impact. Real framework gaps. Ransomware attacks on hospitals are attacks on human life — not just data.

● LIVE INTELLIGENCE
Updated: June 11, 2026
⚠ TRACKER REFRESHED — 2025/2026 INCIDENTS
Source: HHS OCR + HIPAA Journal + Comparitech
OrganizationDateAttack VectorPatient ImpactRecoveryFramework GapSeverity
NOTE: All incidents sourced from public disclosures, HHS breach portal, and verified media reporting. Every incident here represents patients whose care was disrupted. Ransomware attacks on healthcare organizations are attacks on human life.
Career Pathways Your Future in Health Technology

Careers That
Protect People

Healthcare cybersecurity is one of the fastest-growing and most underpopulated fields in security. These are the roles that sit at the intersection of clinical knowledge and technical skill — where the real work happens.

Did you know you can have a career that combines healthcare, technology, and protecting people — all at the same time? Which one sounds like you?

🛡
Healthcare Cybersecurity Analyst
$85K – $130K / year
Great paying career
Monitors hospital networks, investigates security incidents, and ensures medical devices and systems are protected from threats.
This person watches over hospital computer systems to make sure hackers can't get in. They're like a security guard — but for technology.
Network SecurityHIPAAIncident ResponseIoMT
🏥
Clinical Informatics Specialist
$80K – $120K / year
Great paying career
Bridges clinical workflows and health IT systems. Ensures electronic health records and clinical technology work safely and effectively for patient care.
This person makes sure that computer systems in hospitals work well for doctors and nurses. They understand both medicine AND technology.
EHR SystemsClinical WorkflowsHealth IT
🔬
Biomedical Technology Engineer
$75K – $115K / year
Great paying career
Manages and secures medical devices throughout a healthcare organization. Responsible for device inventory, vulnerability assessment, and lifecycle management.
This person takes care of all the medical devices in a hospital — making sure they work correctly, are safe, and can't be hacked.
Medical DevicesFDA ComplianceVulnerability Mgmt
🤖
Healthcare AI Risk Analyst
$100K – $160K / year
One of the fastest growing careers
Evaluates AI systems used in clinical settings for bias, safety, and reliability. Ensures AI tools meet regulatory requirements and don't harm patients.
As hospitals use more AI to help doctors make decisions, someone needs to make sure those AI systems are fair, accurate, and safe.
NIST AI RMFAI GovernanceClinical AIRisk Assessment
🚨
Digital First Responder
$120K – $200K+ / year
Elite career — combines clinical + cyber
The rarest role in healthcare security — someone who understands both clinical emergency response and cyber incident response. Built from experience on both sides of a crisis.
The rarest and most powerful combination — someone who has worked in emergency medicine AND cybersecurity. They respond to both physical and cyber emergencies in hospitals.
Clinical ExperienceIncident ResponseIoMT SecurityLeadership
🏃
Sports Technology Security Analyst
$90K – $140K / year
Fast-growing career in sports + tech
Secures connected athlete performance systems — wearables, biometric sensors, GPS trackers, and team analytics platforms. Protects athlete data from unauthorized access and manipulation.
Sports teams use technology to track athlete performance, heart rate, speed, and recovery. This person makes sure that data stays private and can't be hacked or manipulated.
IoT SecurityWearablesData PrivacyBiometrics
📊
Health Data Scientist
$95K – $150K / year
One of the highest paying health tech careers
Analyzes large volumes of clinical data, wearable telemetry, and patient records to find patterns that improve care outcomes.
This person uses math, computers, and healthcare knowledge to find hidden patterns in patient data that help doctors make better decisions.
Machine LearningPythonClinical DataAI
Wearable Technology Engineer
$100K – $160K / year
Builds the devices athletes and patients depend on
Designs and secures wearable devices used in clinical and athletic settings — from Apple Watch health integrations to medical-grade biosensors.
This person builds and secures wearable devices like Apple Watches — making sure they accurately measure what they're supposed to and can't be hacked.
Hardware SecurityIoTFirmwareBiometrics
🤖
Clinical AI Engineer
$120K – $180K / year
The future of healthcare technology
Builds and validates AI systems used in clinical decision support, medical imaging, and patient monitoring. Ensures AI models are accurate, fair, and safe before deployment.
This person builds AI systems that help doctors diagnose diseases and monitor patients — making sure the AI is accurate and safe before it's used on real patients.
Machine LearningNIST AI RMFClinical ValidationPython

How Do You Get There From Here?

Right Now (Middle School)

Take health classes seriously. Learn basic coding (Scratch, Python). Explore biology and computer science. Ask questions about how technology works.

High School

AP Computer Science. Biology and health science courses. Cybersecurity clubs and competitions (CyberPatriot). Volunteer at hospitals or clinics to understand the environment.

College & Beyond

Health Informatics, Cybersecurity, or Biomedical Engineering degrees. Internships at hospitals or health tech companies. Certifications like CompTIA Security+ and HCISPP.

About This Lab

Built from
Lived
Reality.

This lab was created by Chaunda C. Dallas, MSIT — healthcare professional and cybersecurity strategist specializing in IoMT risk, medical device security, and clinical AI. She never left healthcare. She learned to defend it.

The scenarios here are not theoretical. They are built from the intersection of clinical expertise and daily device dependency — managing pulmonary hypertension on a portable oxygen concentrator, with a CPAP connected to the internet, and no insurance safety net.

The expansion into sports technology security follows the same logic: wearables worn by athletes carry the same biometric intimacy as medical devices — and face none of the same regulatory scrutiny. That gap is the next frontier. See the full Sports Tech lane →

Featured Defender in the Semperis documentary 'Midnight in the War Room' — premiering at Black Hat USA 2026.

Ms. Chaunda is a healthcare cybersecurity consultant who mentors 200+ women in cybersecurity through WiCyS, and will be featured in a documentary about hospital ransomware attacks at Black Hat USA 2026.

MS Information Technology / Cybersecurity — Kennesaw State University
Healthcare Cybersecurity Consultant | Chaunda C. Dallas LLC
CAGE: 18D81 | UEI: KV2BR8QU36J7 | SAM.gov Registered
WiCyS Technical Mentor — 3rd Consecutive Year (2026)
Featured on Halcyon 'Last Month in Security' Podcast
Featured Defender — Semperis 'Midnight in the War Room' | Black Hat USA 2026
Biohacking Village Volunteer | WiSP DEF CON Lead Liaison
Semperis HIP Conference — Nashville, TN | September 2026
connect@chaundacdallas.com | chaundacdallas.com
28+
Years Clinical Emergency Medicine
9
IoMT Failure Scenarios (v3.0)
200+
Women Mentored Through WiCyS
0
Hypothetical Scenarios — All Built from Reality
6+
Regulatory Frameworks Per Scenario
2
Sectors: Healthcare + Sports Tech
Key Resources Learn More
FDA Guidance
Cybersecurity in Medical Devices
FDA's 2023 guidance on cybersecurity requirements for medical device submissions. The baseline for IoMT security compliance.
The US government's rules for making sure medical devices are safe from hackers.
FDA.gov →
NIST Framework
AI Risk Management Framework
NIST AI RMF 1.0 — governance framework for trustworthy AI. Directly applicable to clinical AI decision support tools.
A framework that helps organizations make sure their AI systems are safe, fair, and trustworthy — especially important when AI is used in healthcare.
NIST AIRC →
HHS Resource
405(d) Cyber Performance Goals
HHS Healthcare Cybersecurity Performance Goals — the healthcare-specific security baseline from the federal government.
The US Department of Health and Human Services' guide to what every hospital should do to protect itself from cyberattacks.
405d.HHS.gov →
Threat Intelligence
HHS Breach Portal
Official HHS portal tracking healthcare data breaches affecting 500+ individuals. Primary source for incident intelligence.
A public database of every major healthcare data breach in the US.
HHS OCR Portal →
For Students
CyberPatriot Program
National youth cyber education program. Entry point for students pursuing cybersecurity careers.
A national competition for middle and high school students to learn cybersecurity skills by defending virtual computer networks.
CyberPatriot →
Community
Women in CyberSecurity (WiCyS)
Primary community for women in cybersecurity. Scholarships, mentoring, and career development resources.
An organization dedicated to bringing more women into cybersecurity careers. Offers scholarships, mentoring, and community.
WiCyS.org →