Blue Goat CyberBlue Goat CyberSMMedical Device Cybersecurity
    Start here
    Services
    • Medical Device Cybersecurity Consulting
    • FDA Premarket Cybersecurity Package
    • Medical Device Penetration Testing Services
    • FDA Deficiency Response
    • FDA Postmarket Cybersecurity
    • Medical Device Threat Modeling
    • eSTAR Cybersecurity Documentation Support
    See all services
    Products

    Blue Goat products

    • GoatWatch logoGoatWatchSBOM risk management for medical devices
    About
    Resources

    Learn

    • Blog
    • Podcast
    • Webinars
    • Talks & workshops
    • Glossary
    • FAQs

    Playbooks & Tools

    • Guides
    • Playbooks (PDF)
    • Infographics
    • Interactive Tools

    Signals & Proof

    • Goat FeedNew
    • News
    • Medical Device Security News
    • The Goat's Weekly
    • Case Studies
    • Proof / Receipts
    All resources, topic hubs, & collections →
    ⌘K
    Book Strategy SessionHow to prepare →
    Blue Goat Cyber

    Full-service medical device cybersecurity. We protect patients by securing connected medical devices from design through postmarket.

    275+ FDA submissions supported, zero cybersecurity rejections · Mission: 1,000 by 2028

    SDVOSB · Service-Disabled Veteran-Owned Small Business

    We sponsor 10 community projects →

    Services

    • FDA Premarket Cybersecurity Package
    • FDA Deficiency Response
    • Medical Device Threat Modeling
    • Medical Device Penetration Testing Services
    • FDA Postmarket Cybersecurity
    • All services →
    Services
    • FDA Premarket Cybersecurity Package
    • FDA Deficiency Response
    • Medical Device Threat Modeling
    • Medical Device Penetration Testing Services
    • FDA Postmarket Cybersecurity
    • All services →

    Company

    • About
    • Core values
    • Manifesto
    • Leadership
    • Why Us
    • Partners
    • Careers
    • Press
    • Press kit
    • Contact
    • Company overviewPDF
    Company
    • About
    • Core values
    • Manifesto
    • Leadership
    • Why Us
    • Partners
    • Careers
    • Press
    • Press kit
    • Contact
    • Company overviewPDF

    Resources

    • Blog
    • Guides
    • Podcast
    • Case studies
    • Monthly Pulse newsletter
    • All resources →
    Resources
    • Blog
    • Guides
    • Podcast
    • Case studies
    • Monthly Pulse newsletter
    • All resources →

    Get in touch

    • info@bluegoatcyber.com
    • 844-939-GOAT
    • Book a strategy session →
    • 1776 N Scottsdale Rd, Unit 727
      Scottsdale, AZ 85257Serving clients worldwide

    Follow

    © 2026 Blue Goat Cyber. All rights reserved.

    • Privacy
    • Terms
    • Cookies
    • Sitemap
    • Accessibility
    • CVD

    MedTech Cybersecurity · Since 2022

    Newsroom · Regulatory Tracker

    Medical device cybersecurity regulatory tracker.

    A dated, structured log of FDA, CISA, AAMI, EU, and supply-chain changes that move the cybersecurity bar - with what changed and what to do about it.

    25 of 25 tracked changes

    Last updated Oct 22, 2026RSS
    Agency
    Status
    Impact

    Upcoming deadlines

    soonest first · 1
    • Dec 11, 2027·in 13 months·EU Commission · Regulation (applies)ScheduledHigh impact

      EU Cyber Resilience Act becomes fully applicable

      The CRA's core obligations - secure-by-design, SBOM, vulnerability handling, and 24-hour incident reporting - apply to products with digital elements placed on the EU market. Devices regulated under the MDR or IVDR are excluded.

      Applies to:Products with digital elements sold in the EUCompanion products and accessories not regulated as medical devices
      Read details

    Change log

    newest first

    2026

    • Jun 30, 2026·4 months ago·Red Hat · End-of-support clockScheduledHigh impact

      RHEL 7 Extended Life Support ends: legacy fleets need a memo

      RHEL 7 ELS reaches end of support on 30 June 2026. Devices that still ship or service with RHEL 7 need a compensating-controls memo in their postmarket file.

      Applies to:Legacy devices running RHEL 7
      Read details
    • Apr 22, 2026·6 months ago·CISA · KEV updateActiveHigh impact

      CISA adds Linux netfilter flaw to KEV (CVE-2026-0511)

      A use-after-free in Linux kernel netfilter (CVE-2026-0511) was added to the Known Exploited Vulnerabilities catalog, affecting many embedded Linux device platforms.

      Applies to:Devices on Linux kernelEmbedded Linux platforms
      Read details
    • Apr 15, 2026·7 months ago·CISA · KEV updateActiveHigh impact

      CISA adds widely embedded BLE pairing bypass to the KEV

      CISA added a BLE pairing bypass affecting an embedded Bluetooth stack used across consumer and medical wearables to the Known Exploited Vulnerabilities catalog.

      Applies to:WearablesConnected devicesBluetooth-enabled SaMD
      Read details
    • Mar 31, 2026·7 months ago·AAMI · Standards draftDraftMedium impact

      ANSI/AAMI SW96 Amendment 1 draft circulated for member review

      Draft amendment clarifies threat modeling traceability, security risk evaluation, and the relationship between SW96 and AAMI TIR57.

      Applies to:All cyber devices
      Read details
    • Feb 3, 2026·9 months ago·FDA · Final GuidanceActiveHigh impact

      FDA finalizes 2026 premarket cybersecurity guidance

      The FDA's February 3, 2026 final guidance distinguishes nonbinding cybersecurity evidence recommendations from Section 524B statutory duties. Covered cyber-device submissions require an SBOM; VEX is optional, and an SPDF is encouraged rather than mandated.

      Applies to:510(k)De NovoPMASection 524B
      Read details
    • Feb 3, 2026·9 months ago·FDA · Guidance supersededWithdrawnMedium impact

      FDA 2023 premarket cybersecurity guidance superseded

      The September 2023 premarket cybersecurity guidance is superseded by the February 3, 2026 final guidance. Citing the 2023 document in new submissions is now a stale reference.

      Applies to:Premarket submissions
      Read details
    • Feb 2, 2026·9 months ago·FDA · Final RuleActiveHigh impact

      FDA Quality Management System Regulation (QMSR) takes effect

      The QMSR formally aligns 21 CFR Part 820 with ISO 13485:2016. Cybersecurity design controls, risk management, and supplier controls must now be documented under the harmonized framework.

      Applies to:All medical device manufacturers
      Read details
    • Jan 8, 2026·10 months ago·CycloneDX · Specification errataActiveMedium impact

      CycloneDX 1.6.1 errata clarifies VEX status semantics

      1.6.1 errata clarifies how to express 'not_affected' justifications and how VEX statements should reference SBOM components by bom-ref or PURL.

      Applies to:SBOM / VEX producers
      Read details

    2025

    • Oct 31, 2025·12 months ago·ISO/IEC · Standard transitionActiveMedium impact

      ISO/IEC 27001:2022 transition deadline passes

      Organizations still certified to ISO/IEC 27001:2013 lost certification on 31 October 2025. Hospitals expect the 2022 control set (including A.8 secure development, A.5.7 threat intelligence) in procurement.

      Applies to:MedTech vendors holding ISO 27001 certification
      Read details
    • Oct 21, 2025·13 months ago·CISA · Pledge expansionActiveMedium impact

      CISA Secure by Design pledge now expects VEX publication

      CISA expanded the Secure by Design pledge so signatories are expected to publish VEX statements alongside SBOMs for shipped products.

      Applies to:Pledge signatories
      Read details
    • Jul 1, 2025·16 months ago·MDCG (EU) · GuidanceActiveHigh impact

      MDCG 2019-16 Rev. 2: MDR/IVDR cybersecurity expectations

      Revised MDCG cybersecurity guidance details security risk management, IT environment assumptions, and basic UDI/postmarket cybersecurity expectations for Notified Body review.

      Applies to:EU MDREU IVDR
      Read details
    • Apr 1, 2025·2 years ago·HHS 405(d) · Practices updateActiveMedium impact

      HHS 405(d) HICP 2025 edition updates medical device practices

      Health Industry Cybersecurity Practices (HICP) 2025 refresh expands medical device practices and adds AI-specific considerations, raising the bar hospitals use during vendor risk reviews.

      Applies to:Health Industry vendorsMedTech providers selling into hospitals
      Read details
    • Jan 7, 2025·2 years ago·FDA · Draft GuidanceDraftMedium impact

      FDA draft guidance on AI-enabled device software functions (2025)

      This draft covers lifecycle management and what to include in marketing submissions for AI-enabled device software, including a section on cybersecurity risks specific to AI, such as tampered training data and attacks on model inputs.

      Applies to:AI/ML-enabled SaMD
      Read details

    2024

    • Dec 4, 2024·2 years ago·FDA · Final GuidanceActiveHigh impact

      FDA finalizes Predetermined Change Control Plans (PCCP) guidance

      Final PCCP guidance lets manufacturers pre-authorize specified modifications to AI/ML-enabled device software functions without a new submission, provided cybersecurity impacts are scoped up front.

      Applies to:AI/ML-enabled SaMD
      Read details
    • May 30, 2024·2 years ago·NIST · Special PublicationActiveMedium impact

      NIST SP 800-216 - federal CVD recommendations finalized

      NIST SP 800-216 finalizes recommendations for federal vulnerability disclosure programs. While federal in scope, MedTech CVD programs are increasingly being benchmarked against it.

      Applies to:Vendors with CVD programs
      Read details
    • Apr 15, 2024·3 years ago·SPDX (Linux Foundation) · SpecificationActiveMedium impact

      SPDX 3.0 final published - adds AI and dataset profiles

      SPDX 3.0 introduces profiles (Software, Security, AI, Dataset) that align directly with SaMD and PCCP cybersecurity expectations.

      Applies to:SBOM producersAI/ML SaMD
      Read details
    • Mar 13, 2024·3 years ago·FDA · Draft GuidanceWithdrawnLow impact

      FDA Draft Section 524B Guidance Updates (2024)

      In March 2024 the FDA published a draft explaining how it reads Section 524B, including what counts as a cyber device. That content has since been brought into the final premarket cybersecurity guidance.

      Applies to:Cyber devices
      Read details
    • Feb 26, 2024·3 years ago·NIST · FrameworkActiveMedium impact

      NIST Cybersecurity Framework 2.0 published

      CSF 2.0 adds the Govern function and broadens scope beyond critical infrastructure, becoming the de facto baseline hospitals reference in MDS2 / HSCC procurement questionnaires.

      Applies to:MedTech security programsHospital procurement responses
      Read details

    2023

    • Jun 14, 2023·3 years ago·FDA · Final GuidanceActiveMedium impact

      FDA Device Software Functions Guidance (2023)

      This guidance sets out the software documentation the FDA expects in a premarket submission, using two levels (Basic and Enhanced) based on risk. It sits alongside the cybersecurity guidance, which covers the security content.

      Applies to:SaMDSoftware in a medical device
      Read details
    • Mar 29, 2023·4 years ago·FDA · StatuteActiveHigh impact

      FD&C Act Section 524B - cyber device requirements in effect

      Section 524B (Omnibus 2023) made cybersecurity submission content mandatory for cyber devices. The FDA has issued Refuse to Accept decisions for non-compliant submissions since October 2023.

      Applies to:Cyber devices (FD&C Act §524B)
      Read details
    • Mar 29, 2023·4 years ago·FDA · Final GuidanceWithdrawnMedium impact

      FDA Refuse-to-Accept Policy for Cyber Devices (2023)

      When Section 524B took effect, the FDA said it would not refuse submissions for missing 524B content until October 1, 2023, and would work with sponsors during review instead. After that date, submissions missing the required cybersecurity content could be refused.

      Applies to:Cyber devices
      Read details

    2021

    • Dec 1, 2021·5 years ago·IEC · StandardActiveHigh impact

      IEC 81001-5-1 - secure software lifecycle for health software

      IEC 81001-5-1 defines the secure development lifecycle for health software and is the foundational standard for the security risk management activities the FDA and Notified Bodies expect.

      Applies to:Health softwareSaMD
      Read details

    2016

    • Dec 28, 2016·10 years ago·FDA · Final GuidanceActiveMedium impact

      FDA postmarket cybersecurity guidance (2016)

      The FDA's postmarket guidance describes how manufacturers should monitor, assess and fix cybersecurity vulnerabilities in devices already on the market, including when a fix needs to be reported to the FDA and when it does not.

      Applies to:Marketed devices
      Read details

    2014

    • Oct 2, 2014·12 years ago·FDA · Final GuidanceWithdrawnLow impact

      FDA's first premarket cybersecurity guidance (2014), now superseded

      The FDA's 2014 guidance was the agency's first statement of what cybersecurity content belongs in a premarket submission: a hazard analysis, a list of controls, and a plan for updates. Later premarket guidance replaced it.

      Applies to:All networked devices
      Read details

    Spotted something we missed? Email info@bluegoatcyber.com with a link and we'll add it.

    Ready when you are

    Secure your device before it reaches patients.

    30-minute strategy session. No cost, no commitment - just answers from people who've supported 275+ FDA submissions, with zero cybersecurity rejections.

    Book strategy sessionExplore services