Skip to main content
v2026.11,858 entries · CC-BY 4.0
LAC HealthMedical Supply Distributor100,000+ medical supplies. 48-hour critical dispatch.Ships from 8 regional U.S. hubs. Net-30 terms for verified institutional accounts.Shop lac.us CodeCASRAIlac.us

Healthcare Cybersecurity: Threats, HHS 405(d) HICP, and Network Segmentation

How hospitals and clinical research institutions defend electronic health records and connected medical devices using HHS 405(d) Health Industry Cybersecurity Practices, HPH Cybersecurity Performance Goals, and HIPAA Security Rule safeguards.

Written and maintained by CASRAI Editorial Board

Last updated

Healthcare cybersecurity encompasses the technical architectures, governance controls, and regulatory safeguards that protect clinical information systems, electronicProtected Health Information (ePHI), biomedical research repositories, and connected medical devices from unauthorized access, disruption, or extortion. Unlike standard enterprise information technology environments, hospital and clinical research networks operate continuous life-critical workflows where system downtime or data tampering directly threatens patient safety and trial data integrity.

In the United States, healthcare cybersecurity governance is anchored by mandatory federal standards under the Health Insurance Portability and Accountability Act (HIPAA) Security Rule (45 CFR Part 164, Subpart C) Alongside two primary federal operational frameworks developed by the U.S. Department of Health and Human Services (HHS): the HHS 405(d) Health Industry Cybersecurity Practices (HICP) and the Healthcare and Public Health (HPH) Sector Cybersecurity Performance Goals (CPGs).

What Are the Primary Cybersecurity Threats in Healthcare?

Established under Section 405(d) of the Cybersecurity Act of 2015, the joint HHS Administration for Strategic Preparedness and Response (ASPR) and Health Sector Coordinating Council (HSCC) task group publishes Health Industry Cybersecurity Practices: Managing Threats and Protecting Patients. The HICP framework organizes defensive engineering around the five most significant operational threats to clinical and research organizations:

  1. Email Phishing Attacks: Credential-harvesting and malicious payload delivery targeting clinicians, billing staff, and clinical research coordinators to compromise identity providers or deploy initial access trojans.
  2. Ransomware Attacks: Cryptographic extortion campaigns that encrypt EHR application servers, Picture Archiving and Communication Systems (PACS), laboratory information systems, and active Directory domain controllers, forcing clinical diversion and manual paper charting.
  3. Loss or Theft of Equipment or Data: Unencrypted mobile workstations, portable ultrasound units, or removable storage media containing unmasked 18 HIPAA identifiers or clinical trial source data.
  4. Insider, Accidental or Intentional Data Loss: Misconfigured cloud storage buckets, improper emailing of unencrypted participant rosters, or deliberate snooping and exfiltration of patient records by credentialed personnel.
  5. Attacks Against Connected Medical Devices: Exploitation of unpatched firmware or legacy operating systems in networked infusion pumps, patient monitors, and diagnostic imaging scanners that may alter therapy delivery or bridge attackers into core hospital networks.

Federal Frameworks: HIPAA, HHS 405(d) HICP, and HPH CPGs

Clinical delivery organizations, academic medical centers, and business associates align their security controls across three complementary regulatory and technical baselines:

Framework / Regulation Governing Authority Legal Status & Scope Core Technical & Administrative Mandates
HIPAA Security Rule HHS Office for Civil Rights (OCR) (45 CFR §§ 164.302–164.318) Mandatory federal regulation for covered entities and business associates handling ePHI Enterprise-wide risk analysis (§ 164.308(a)(1)), workforce access management, facility physical controls (§ 164.310), audit logging, unique user IDs, and transmission/storage encryption (§ 164.312).
HHS 405(d) HICP HHS ASPR & Health Sector Coordinating Council (Cybersecurity Act of 2015 § 405(d)) Recognized security practice benchmark (considered by OCR under HITECH Act § 13412 during enforcement audits) 10 mitigating cybersecurity practices scaled by organization size (Small, Medium, Large) covering email protection, endpoint protection, access management, data loss prevention, asset management, network management, vulnerability management, incident response, medical device security, and governance policies.
HPH Sector CPGs HHS & CISA (Published January 2024) Prioritized voluntary baseline mapped to NIST CSF and HICP Split into 10 Essential Goals (MFA, patching known exploited vulnerabilities, strong encryption, revoking departing credentials, vendor security) and 10 Enhanced Goals (network segmentation, centralized log collection, third-party vulnerability disclosure, configuration management).
FDA Section 524B U.S. Food and Drug Administration (FD&C Act § 524B) Mandatory statutory requirement for premarket cyber device submissions Requires medical device manufacturers to provide a Secure Product Development Framework (SPDF), a machine-readable Software Bill of Materials (SBOM), and coordinated postmarket vulnerability patching plans.

Under the 2021 amendment to the HITECH Act (Public Law 116-321), HHS OCR must consider whether a covered entity or business associate has adequately demonstrated that it had “recognized security practices”—specifically standards under NIST Cybersecurity Framework or Section 405(d) HICP—in place for at least the previous 12 months when determining audit results or mitigating civil monetary penalties following a breach.

How Do Hospitals Segment EHR and IoMT Networks Against Ransomware?

Flat clinical networks allow an attacker who compromises a single administrative workstation via phishing to move laterally using Server Message Block (SMB) or Remote Desktop Protocol (RDP) into core EHR databases and biomedical devices. To contain blast radius, HICP Practice #6 (Network Management) and the HPH Enhanced Cybersecurity Performance Goals specify strict microsegmentation across clinical zones:

  • Zone 1 — Corporate & Administrative IT: Standard user workstations, email clients, and internet-facing web browsers. Isolated from clinical production databases and restricted from initiating direct connections into biomedical VLANs.
  • Zone 2 — Core Clinical Informatics & EHR Tier: Production EHR application and database clusters, clinical data warehouses, and authentication servers. Accessible only via authenticated jump hosts, virtual desktop infrastructure (VDI), or strictly filtered application ports (such as TLS-encrypted HL7/FHIR endpoints) guarded by multifactor authentication.
  • Zone 3 — Internet of Medical Things (IoMT) & Biomedical VLANs: Networked infusion pumps, anesthesia machines, bedside telemetry monitors, and DICOM imaging modalities. Because medical devices often run embedded operating systems that cannot host conventional endpoint detection agents without invalidating FDA premarket cybersecurity configurations, hospitals deploy passive network traffic analysis and Network Access Control (NAC) to enforce device-specific Access Control Lists (ACLs). An MRI scanner, for example, is permitted to transmit DICOM traffic solely to the designated PACS server IP and port while all outbound internet and peer-to-peer workstation traffic is blocked at the switch level.
  • Zone 4 — Research & De-Identified Data Enclaves: High-performance computing clusters and secure research environments housing limited data sets or de-identified cohorts. Segmented from live clinical production so that analytical scripts and external academic collaborators never touch raw production ePHI.

What Are the Best Practices for Healthcare Cybersecurity Risk Management?

Operationalizing the 10 HICP mitigating practices and the HIPAA compliance checklist across clinical and research environments requires verifiable engineering controls across five core domains:

  1. Phishing-Resistant Identity and Access Management: Enforce multifactor authentication (MFA) across all remote access, VPNs, email gateways, and privileged administrative accounts (HPH Essential Goal 1C). Separate standard user accounts from domain administrator accounts (Essential Goal 1I) and enforce immediate automated credential revocation upon workforce termination.
  2. Asset Inventory and SBOM Vulnerability Tracking: Maintain a continuous, automated inventory of all IT and IoMT endpoints on the network, including MAC addresses, firmware versions, and manufacturer Software Bills of Materials (SBOMs). Prioritize remediation of vulnerabilities listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (Essential Goal 1A).
  3. Endpoint Detection and Immutable Backups: Deploy behavioral Endpoint Detection and Response (EDR) agents on all supported servers and workstations, and maintain 3-2-1 backup architectures with immutable, offline, or air-gapped copies tested regularly for rapid EHR restoration during ransomware drills.
  4. Encryption and Data Loss Prevention (DLP): Encrypt ePHI at rest (AES-256) on all servers, laptops, and removable media, and in transit (TLS 1.2/1.3) across external and internal clinical interfaces. Configure automated DLP rules to block unauthorized bulk exports of patient registries or clinical trial subject tables.
  5. Incident Response and Breach Notification Readiness: Maintain clinical downtime continuity playbooks alongside cyber incident response plans that coordinate technical containment with statutory data security incident notification requirements under the HIPAA Breach Notification Rule (45 CFR §§ 164.400–414).

Frequently Asked Questions

What are the primary cybersecurity threats in healthcare?

Under the HHS 405(d) Health Industry Cybersecurity Practices (HICP) publication, the five primary cybersecurity threats facing healthcare organizations are email phishing attacks, ransomware attacks, loss or theft of equipment or data, accidental or intentional insider data loss, and attacks against connected medical devices that can disrupt clinical operations or affect patient safety.

How do hospitals segment EHR and IoMT networks against ransomware?

Hospitals isolate electronic health record (EHR) databases and Internet of Medical Things (IoMT) clinical devices from general corporate IT traffic using Virtual Local Area Networks (VLANs), next-generation firewalls, and Network Access Control (NAC). Strict access control lists restrict lateral movement protocols such as SMB and RDP, allowing connected infusion pumps and imaging systems to communicate only with authorized clinical servers.

What are the best practices for healthcare cybersecurity risk management?

Healthcare cybersecurity risk management combines mandatory HIPAA Security Rule risk analyses (45 CFR § 164.308(a)(1)(ii)(A)) with the 10 HHS 405(d) mitigating practices and the 20 HHS Healthcare and Public Health Sector Cybersecurity Performance Goals (CPGs), including phishing-resistant multifactor authentication, vulnerability management, immutable offline backups, endpoint detection and response, and vendor Software Bill of Materials (SBOM) tracking.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about Healthcare Cybersecurity: Threats, HHS 405(d) HICP, and Network Segmentation

Ask your first 2 questions free below. Subscribers get 150 a day for $29 a month.

An AI assistant specialized in research administration. It cites the sources behind every answer, labels web answers and says when it can't answer.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays free to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →