Behind the song · cybersecurity · networked devices · standards
Whose Part Is This? The Standard Behind the Chant
A hypnotic techno chant built on the real rule that splits a networked device's security three ways.
In short
- A real international standard splits medical device network security three ways: maker, hospital, and IT provider.
- That standard requires a documented, shared risk-management process among all three.
- The song's chant mirrors the standard's structure: write the split down before, not during, an outage.
"Whose Part Is This?" turns a very specific, very familiar argument into a club chant: a networked device goes down at two in the morning, and three different badges show up, each one sure the fix belongs to somebody else.
Where the song came from
That three-way standoff, maker, hospital, network, isn't invented for the song. It maps onto a real international standard that splits responsibility for a medical device on a hospital network three ways: the device manufacturer, the healthcare delivery organization running it, and the IT or infrastructure provider carrying its traffic. The standard requires all three to document a shared risk-management process rather than leaving it to be sorted out in the moment.
Line goes quiet at two in the morning,three different badges, one broken screen,maker says patched, hospital says configured,network says check what's in between.
Writing it down before the dark
The song's answer is the standard's answer too: write it down before the outage, not during it. "Three names on one line of a shared agreement" is a fair one-line summary of what that risk-management paperwork is actually for, turning a three-way argument into a single, agreed division of labor.
That's why the chant works as a chant. "Maker's part, hospital's part, network's part" isn't just a catchy call-and-response, it's close to the literal structure of the agreement the standard asks these three parties to put in writing, said out loud instead of buried in a document nobody reads until something breaks.
The song ends on "all three," which is the point: none of the three parties gets to opt out of the agreement, because a device on a shared network is never only one party's problem.
That's a useful reframe for a scenario that usually plays out as a scramble. A broken screen at two in the morning doesn't wait politely for three organizations to sort out ownership. The value of having the split written down beforehand is exactly that it removes the argument from the moment when the argument costs the most, and turns it into a decision that was already made, calmly, in daylight.
It's also a reminder that a networked device was never really one party's machine to secure alone. The manufacturer builds it, the hospital runs it, and whoever carries its data in between has a hand on it too. The song just says that out loud, over and over, until it's impossible to miss.
None of that turns a real standard into light entertainment by accident. It works precisely because the underlying frustration, three different badges, one broken screen, is something most people in the field have lived through at least once, even if they've never seen the paperwork that's supposed to prevent it.
Sources
- IEC 80001-1: Enhancing Medical Device Cybersecurity, Blue Goat Cyber




