Cybersecurity Basics for Connected Medical Products

Why healthcare products are different

A security breach in a connected medical product can affect patient safety, not just data confidentiality. Regulators and hospital customers now expect cybersecurity to be demonstrable — threat modelled, tested, and maintained across the product lifecycle.

This guide covers foundational practices for teams building connected devices, SaMD, remote monitoring platforms, and clinical integration software.

Threat modelling early

Start threat modelling when architecture is on the whiteboard, not when penetration testing is scheduled.

• System boundary diagram includes devices, mobile apps, APIs, cloud, third parties, and admin tools.
• STRIDE or similar methodology applied to each trust boundary.
• Clinical impact of each threat scenario is rated (data integrity, availability, confidentiality).
• Risk controls mapped to design decisions, not only operational policies.
• Threat model updated on every major architecture change.

Identity, access, and secrets

Weak authentication is the most common finding in healthcare software assessments.

• Role-based access control aligned to clinical roles (not generic admin/user).
• Multi-factor authentication for privileged and remote access.
• Service account and API key rotation procedures.
• Secrets not embedded in mobile binaries or firmware images.
• Session management with timeout appropriate to clinical environment.

Data protection in transit and at rest

Clinical data must be protected across every hop — device to app, app to cloud, cloud to EMR.

• TLS 1.2+ for all external communications with certificate validation.
• Encryption at rest for databases, backups, and mobile local storage.
• Key management approach documented (HSM, KMS, rotation).
• Data minimisation — collect only what the clinical function requires.
• Audit logs for access to sensitive patient data.

Vulnerability management and response

Cybersecurity is a lifecycle obligation, especially post-market.

• SBOM maintained for software components and SOUP.
• Patch and update cadence defined with severity-based SLAs.
• Coordinated vulnerability disclosure process documented.
• Penetration testing planned pre-release and periodically post-market.
• Incident response playbook includes clinical risk assessment steps.

Hospital deployment realities

Products must operate inside hospital networks with firewalls, proxies, and strict IT policies.

Design for hospital IT constraints: whitelisted endpoints, on-premise options, integration engine compatibility, and clear network port documentation. Products that assume open internet access often fail hospital security review before they reach a ward.