
Reviewed by Christian Espinosa, MBA, CISSP · Founder & CEO
Published August 2025 · Last reviewed May 2026
The Med Device Cyber Podcast · August 31, 2025 This episode of The Med Device Cyber Podcast delves into the crucial distinctions between cybersecurity measures and metrics for medical devices, a topic often misunderstood yet vital for FDA submissions. Hosts Christian Espinosa and Trevor Slatterie clarify that measures are quantifiable attributes (e.g., time to patch), while metrics are derived calculations (e.g., percentage of systems patched within a timeframe). The discussion highlights the FDA's specific requirements in 510(k) and PMA submissions, focusing on vulnerability management, patch availability, and deployment durations. The hosts emphasize the importance of a risk-based approach to vulnerability remediation, aligning timelines with device architecture and potential impact on patient safety. They explore strategies for detecting incidents, designing effective alerting mechanisms, and the significance of a robust postmarket surveillance plan. The episode also touches on the applicability of these measures and metrics across different device lifecycle stages and environments, providing valuable insights for product security teams, regulatory leads, and engineers navigating the complexities of medical device cybersecurity compliance and beyond.
Key Takeaways
- Measures are quantifiable attributes like the time taken to apply a patch or the number of incidents, while metrics are calculations derived from these measures, often expressed as percentages, such as patch management efficiency.
- The FDA is specifically interested in measuring the percentage of identified vulnerabilities that are updated or patched, the duration from vulnerability identification to patch availability, and the duration from patch availability to deployment across all fielded products.
- A risk-based approach is crucial for vulnerability remediation, prioritizing critical vulnerabilities for faster patching while considering the device's architecture and the feasibility of over-the-air updates versus manual service technician deployments.
- Implementing effective alerting mechanisms directly into medical devices can compensate for the lack of real-time monitoring by traditional SOCs, notifying users of security events and guiding them on how to report anomalies to the manufacturer.
- While the FDA outlines minimum cybersecurity measures and metrics, manufacturers should strive to exceed these baselines to demonstrate a serious commitment to product security throughout the device's lifecycle and across various deployment environments.
- Understanding the applicability of these measures and metrics is essential, as new devices without predicate data may only need a plan for collection, while established devices or PMA annual reports require actual data.
- Beyond compliance, the ability to translate collected measures and metrics into actionable plans for risk reduction is paramount for effective medical device cybersecurity.
Listen on mdcpodcast.com · Watch on YouTube
Listen to this episode
Want help applying this to your own device program?
Blue Goat Cyber is a specialist medical device cybersecurity firm: 250+ FDA submissions, zero rejections. If anything in this conversation hit close to home, book a 30-minute strategy session - no cost, no obligation.
