A weak root of trust, an incomplete update strategy, or an overlooked communication path may not become visible until testing, or an FDA submission is already underway.
In this technical webinar, we’ll follow a connected medical device from threat analysis through architecture, implementation, validation, and postmarket support. You’ll see how early decisions about device trust, protected communications, software updates, and key management affect both security and regulatory evidence later.
Using practical medical use cases, the webinar connects potential attack paths and current regulatory expectations to the technical decisions engineers must make before the architecture becomes difficult to change.
You’ll learn how to:
– Identify attack paths across the device, communications, and connected services
– Translate threats and regulatory expectations into architecture requirements
– Establish trust across boot, software updates, and network communications
– Protect data and device operation without disrupting clinical use
– Validate security controls and prepare for vulnerabilities after deployment
Choose the Session That Fits Your Time Zone
Europe Session
Date: August 4, 2026
Time: 14:00 CET (5:00 PST)
Register for Europe-Friendly Time
APAC Session
Date: August 5, 2026
Time: 15:00 JST (August 4, 23:00 PST)
Register for APAC-Friendly Time
Ask the Expert: Answers Key Questions
Our experts answer key questions about what attendees will learn
Where can trust break in a connected medical device?
Attack paths can cross the device, its communication channels, and connected services. Mapping those paths reveals which trust boundaries and interfaces require protection.
Which security decisions must be made before the architecture is finalized?
Engineers must define the root of trust, authenticated update process, key storage, and protected communication paths early. Changing these foundations after implementation can require significant redesign.
How should the architecture support validation and postmarket security?
During validation, engineers must be able to demonstrate that security controls work as intended. After deployment, the device must support authenticated updates and responses to newly discovered vulnerabilities.
Register now to make the critical security decisions before testing and submission expose the gaps.
As always, our webinar will include Q&A throughout. If you have questions about any of the above, please contact us at facts@wolfssl.com or call us at +1 425 245 8247.
Download wolfSSL Now