This webinar addresses how medical device manufacturers maintain cybersecurity throughout the lifecycle of SaMD, SiMD , and AI-enabled devices, covering third-party software vulnerabilities, patches, security testing, change impact assessments, and decisions on when existing risk controls and regulatory evidence require reassessment.
Cybersecurity risks continue to evolve after medical device software is released. New vulnerabilities may emerge in third-party libraries, operating systems, communication interfaces, or embedded software components, even when the manufacturer's own code remains unchanged. Software as a Medical Device (SaMD), software in medical devices ( SiMD ), and AI-enabled medical devices introduce different dependencies and attack surfaces that manufacturers must address through ongoing cybersecurity risk management.
Responding to newly identified vulnerabilities requires more than deploying patches or updating software components. Manufacturers must assess exploitability, potential patient harm, the effectiveness of existing security controls, and whether proposed changes introduce additional risks. Security updates may also affect device functionality, verification evidence, or regulatory obligations. This webinar addresses how to prioritize vulnerabilities, justify remediation decisions, establish appropriate testing, and maintain defensible cybersecurity documentation throughout the device lifecycle.
Making Defensible Cybersecurity Decisions After Software Release
The session focuses on determining when newly discovered vulnerabilities, software dependencies, or security updates require additional risk assessment and verification. Particular attention is given to distinguishing cybersecurity maintenance from changes that may affect device safety, performance, intended functionality, or existing regulatory evidence.
Managing Vulnerabilities, Updates, and Cybersecurity Change Control
Practical scenarios follow vulnerabilities from initial detection through impact assessment, remediation planning, implementation, and verification. The session connects software bills of materials, third-party component monitoring, patch validation, residual risk assessment, and regulatory change evaluation, including additional considerations for AI-enabled device software.