№ 30ProcessCanonRelevant to: Manufacturer · HDO · Regulator Corpus reviewed April 27, 2025

    “Our incident response plan is the IT team's runbook.”

    A widely held belief in MedTech, and a dangerous one. Here's what the regulators, the standards bodies, and the field evidence actually say.

    The Myth

    Our incident response plan is the IT team's runbook.

    This belief shows up in boardrooms, design reviews, and FDA pre-submissions every week. It feels safe. It is not.

    The Reality

    Medical device incidents trigger overlapping obligations: FDA MDR reporting, HHS breach notification (if PHI), CISA coordinated disclosure, customer comms, and clinical risk assessment. A generic IT runbook misses every regulator-specific clock.[1]

    Why it matters

    Manufacturers without a device-specific IR plan miss the 60-day HHS notification window and the 30-day FDA MDR clock, compounding penalties on top of the breach.[2]

    60 / 30 daysHHS breach notification / FDA MDR clocks
    What to do instead

    Concrete next steps.

    Specific, defensible actions to replace the misconception with practice. Each item maps back to the citations above.

    1. 1

      Build a device-specific incident response plan

      Cover FDA MDR, HHS breach notification, CISA disclosure, customer comms, and clinical risk assessment. Each has its own clock and audience; an IT runbook covers none of them.

    2. 2

      Map the 30-day FDA MDR and 60-day HHS clocks

      Document who detects, who decides, who files, and the maximum elapsed time at each step. Late notifications compound penalties on top of the underlying breach.

    3. 3

      Run a tabletop incident exercise twice a year

      Exercise medical-device-specific scenarios with cross-functional participation. Capture the after-action lessons in a tracked plan.

    4. 4

      Pre-establish disclosure channels with CISA and your ISAC

      Have the relationships, PGP keys, and reporting templates in place before you need them. Cold-calling CISA at 3am is not a strategy.

    References

    The receipts.

    Review the sources behind this entry. Each reference shows which claim it supports and who published it.

    2 sources
    1. 1
      HHS Breach Notification Rule
      Supports: The RealityRegulator / government hhs.gov
    2. 2
      FDA Medical Device Reporting (MDR)
      Supports: Why it mattersRegulator / government fda.gov

    Found a broken or outdated source? See our evidence methodology and send a correction.

    Need help getting this right?

    Blue Goat Cyber works with MedTech manufacturers on premarket and postmarket cybersecurity programs.

    Talk to an expert
    Related misconceptions

    If this one bit you, these will too.

    Inferred from shared tags and category — not editorial picks.