- What is the Goat Feed?
- The Goat Feed is a daily, MedTech-only cybersecurity feed maintained by Blue Goat Cyber. It curates every CISA KEV addition, FDA letter or recall, ICS-MA advisory, MAUDE adverse event with a cyber signal, EU regulator alert, and FDA Section 524B move that is relevant to medical-device manufacturers - and ignores everything else.
- How often is the feed updated?
- The feed pulls from upstream sources several times an hour. New items appear on /goatfeed as soon as they are ingested, classified, and reviewed. A short Monday email summarizes the previous week's notable and critical items.
- How are sources chosen?
-
Sources are chosen against four explicit rules. Items that do not clear all four are not ingested into the feed.
- Primary-source only. We ingest directly from CISA (KEV, ICS-MA), the FDA (Medical Devices RSS, Safety Communications), openFDA (recalls, 510(k), MAUDE), NVD, MHRA, ENISA, BSI, AAMI, IMDRF, and named vendor PSIRTs. No aggregator blogs, news rewrites, LinkedIn posts, or social media.
- MedTech relevance. Rule of thumb: would a medical-device manufacturer's regulatory, quality, or product-security team need to act on this before their next FDA submission, MDR technical-file update, or postmarket review? If yes, it's in. The item must affect a regulated medical device, a device manufacturer, a 510(k)/PMA/De Novo holder, an MDR/IVDR economic operator, or the cybersecurity processes that govern them - FDA Section 524B, the Feb 3, 2026 premarket cybersecurity guidance, MDCG cybersecurity guidance, or IMDRF principles.
- Concrete cyber signal. The item must name a specific technical or regulatory cyber artifact - for example, a CVE in an infusion-pump Wi-Fi stack, an FDA recall whose root cause is "unauthenticated firmware update", or a 524B refuse-to-accept letter citing a missing SBOM. Vague phrases like "cybersecurity concerns" without a named component, CVE, or regulator action do not qualify.
- Exclusion rules. We drop enterprise-IT CVEs with no MedTech vendor, consumer-tech advisories, generic ransomware roundups, drug-only recalls and sub-recalls, sterility / labeling / packaging recalls with no cyber cause, hospital-IT breaches that do not involve a device manufacturer, and duplicate cross-postings of the same primary item.
Borderline items are held for human review before publication; rejected items are logged with a reason. The full rubric lives on the Methodology page.
- What does the 'Blue Goat take' on each item mean?
- The Blue Goat take is a one-paragraph note from Blue Goat Cyber Research explaining what the item means for a medical-device manufacturer - typically the affected device class, the regulatory or technical implication, and what teams should look at next. It is editorial commentary, not regulatory guidance.
- How are severity labels (critical, notable, info) assigned?
- Critical = KEV-listed exploitation, Class I recalls, confirmed breaches, or active 524B enforcement signals. Notable = Class II recalls, ICS-MA advisories with patches available, and new guidance with material compliance impact. Info = background context, Class III recalls, and software-quality items without a confirmed cyber signal.
- Is the Goat Feed free?
- Yes. Reading the feed on bluegoatcyber.com/goatfeed is free and requires no account.
- How do I get notified of new items?
- Subscribe to the Monday email - a short summary of the previous week's notable and critical items, delivered once a week with no fluff. Personal watchlists, public RSS, JSON Feed, and an embed widget are on the roadmap and will be added later.
- How are corrections handled?
- When an item is updated after publication - for example, a vendor confirmation, a CVSS revision, or a clarification from the FDA - a Corrected badge appears on the item and the change is logged on the detail page. The article's dateModified reflects the latest correction.