Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Tech Talks With Kinsoft

Tech Talks With Kinsoft artwork

Boston Scientific - One Network Box, Two Weeks Without Shipping, and Nothing Encrypted

Sep 24, 202622 minAudio

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! A catch-up episode, recorded after the fact. The investigation had concluded and been published by 23 September (AEST). US medical device maker Boston Scientific lost roughly two weeks of manufacturing and shipping to a cyber intrusion in which, according to CrowdStrike, nothing was encrypted and no data was taken. Timeline (US time). 25 August: system availability issues traced to an unauthorised third party; containment begins and CrowdStrike is engaged. 26 August: voluntary SEC disclosure. 30 August: no further unauthorised activity since 25 August; cloud systems unaffected. 3-5 September: shipping and most manufacturing resume. 7-8 September: material-incident SEC filing; the company says it is unlikely to meet Q3 and full-year guidance, with a new outlook due 28 October. 9 September: manufacturing, fulfilment and shipping fully restored. 18 September: investigation concludes. By 23 September (AEST): CrowdStrike summary published. What CrowdStrike found. Entry via "an external-facing network management device" - vendor, model and method not disclosed; the device has been decommissioned. No evidence of encryption; no activity in Microsoft 365 or email; no interactive access to HR, manufacturing, SCADA or product development systems; no logins to SAP, Salesforce or cloud apps; no evidence that data, including patient or customer data, was accessed or taken. Implanted devices unaffected. No group has credibly claimed it and no CVE has been linked; attributions to ShinyHunters and a pro-Russian group are unsupported. Not yet explained: how an intrusion without encryption caused a two-week outage. Lessons. Inventory and harden internet-facing management devices, with management interfaces off the internet and MFA on. Map which systems the business cannot run without. Logging is what lets you state that no data was taken - and in Australia, it decides whether you have a notifiable breach. A staged, frequent, evidence-based disclosure is a good model for ASX continuous disclosure too. Visit www.kinsoft.com.au to talk through your security and IT needs. Sources: Boston Scientific SEC filings (26 August and 8 September 2026); Boston Scientific incident updates; CrowdStrike investigation summary; TechCrunch; SecurityWeek; HIPAA Journal; Quartz; MedTech Dive; 24x7 Magazine.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

You know, usually when we talk about a massive corporate disaster like a bank heist or something, there is this expectation of, well, obvious destruction. Right. Like it's highly visible. Yeah, exactly. You picture the blown open vault, the alarms blaring, the empty safe deposit boxes. The authorities walk in, point at the giant hole in the wall and say, well, there it is. That is what they took. There's a clear crime scene, an obvious point of entry and a quantifiable loss that, you know, everyone can immediately understand. But imagine you arrived at that exact same bank

and the vault was perfectly intact. I mean, not a single dollar missing. No alarms tripped. Right. No alarms. The safety deposit boxes haven't even been breathed on. But the bank manager was so spooked by like a shadow near the back door that they intentionally welded the front door shut. They turned off all the ATMs. Yeah. just stopped letting anyone make a withdrawal or deposit for two entire weeks. Which would effectively crash the bank's operations, right? I mean, it would cause a massive financial panic. Completely.

Even though the robbers themselves didn't actually steal a single cent or break a single lock. It completely flips our traditional understanding of what a security breach actually looks like in practice. And that is exactly what we are getting into today. Welcome to the Deep Dive. We are thrilled to have you with us as we explore a cybersecurity incident that defies absolutely everything we have come to expect about how cyber attacks work. It really does challenge all the assumptions. It does. So our source material for this deep dive comes from a September 25th,

2026 catch -up edition of Tech Talks with Kinsoft. And our mission today is to understand how a massive global medical device maker lost two weeks of manufacturing and shipping. They completely tanked their quarter. Yes. And yet no data was stolen and no files were encrypted. Okay, let's unpack this. Well, it requires a fundamental shift in perspective. You know, we have been conditioned by the media and by past high profile incidents to associate cyber attacks with digital hostage situations. Oh, totally. We expect ransomware

extortion. Exactly. We expect leaked databases and ruined hard drives. But this case reveals a completely different kind of vulnerability. Which is what makes it so fascinating. Right. It's one where the sheer fear of the unknown. And the actual protocols designed to protect a company become the destructive mechanism itself. So the company at the center of this is Boston Scientific. And to really grasp the gravity of a two -week shutdown, you kind of have to understand the sheer footprint of this giant. Right. This isn't some niche regional supplier with a warehouse

in the suburbs. Not at all. I mean, they are based in Massachusetts, but they have roughly 59 ,000 employees. Spread across more than 120 countries. Yeah, and according to the HIPAA Journal, their medical devices are used by around 48 million patients every single year. We are talking about critical, life -altering hardware here. Specialized cardiac stents, advanced surgical products, neurological modulators. Stuff you kind of need. Right. These are devices that hospitals literally cannot function without. And crucially, most of what they sell

is single -use. Like, the surgeon opens the sterile packaging, uses the device during a procedure, and then it is disposed of. It has to be replaced by a brand new one for the next patient. Exactly. So it is this high -volume, constant -flow supply chain. Because hospitals do not have the physical space or the budgets to stock infinite supplies of these specialized, single -use devices. They operate on a just -in -time inventory model. Right. They rely on a steady, mathematically predictable rhythm of shipping and fulfillment from the manufacturer. If a product is delayed,

surgeries get canceled. It is really that simple. So keep that incredibly fragile, high stakes rhythm in mind as we look at the reality of this disruption. The pressure doesn't just build overnight. It compounds. It really snowballs. Based on U .S. time, on August 25th, an alert pops up. Boston Scientific detects what it broadly calls, quote, system availability issues, unquote, across parts of its network. And they trace it to an unauthorized third party. Right. They immediately begin containment

protocols and bring in the cybersecurity heavy hitters CrowdStrike to investigate. And within hours, this digital anomaly translates into physical paralysis. Yeah. Over in Ireland, local media reports that staff at Boston Scientific's massive court campus are suddenly sent home. What's fascinating here is how the physical manifestation of a digital threat is just so immediate. Yes. An analyst in a security operations center sees an anomalous connection. And thousands of miles away, real people are walking out of physical manufacturing

plants. The assembly lines building pacemakers just halt. The sterilization chambers power down. The lights are essentially turned off. It highlights how utterly tethered the physical manufacturing world is to its digital nervous system. Because without the network to tell the machines what to build or the shipping software to print the labels, the factory is just an expensive empty shell. Exactly. And over the next week, the momentum of the crisis just snowballs. It is not a matter of simply turning the servers back on the next

morning. No, it takes until September 3rd through the 5th for shipping to even slowly start resuming from their major distribution centers. Right. The sterilization sites finally come back online. And manufacturing slowly spins back up. Because restarting a global manufacturing operation is agonizingly complex. It isn't a light switch. Not at all. When you sever a network unceremoniously, Databases get corrupted. Inventory systems lose sync with the physical warehouse shelves. Robotic assembly lines have to be recalibrated. Yeah,

and software has to be carefully, methodically brought back online, segment by segment. You have to ensure the intruder isn't hiding in a reboot script. It's like a massive global train network slamming on the emergency brakes, all at exactly the same time, you know? Oh, that's a good way to put it. Like the sheer violent inertia of stopping is one thing. But getting it going again, you have to manually inspect every single mile of track. Coordinate every single automated signal. Yeah, and slowly build

up the steam before those incredibly heavy trains can start moving safely. And while they are slowly getting those trains moving, the financial reality sets in. Right. On September 7th and 8th, the pressure culminates in a formal material cyber incident report filed with the SEC. They have to officially warn Wall Street that this disruption is so severe, they are going to miss their financial guidance for the quarter. And for the entire year. And with a new outlook scheduled for October 28th, Quartz reports that shares fell over 4 % on the news. Though, to be fair, the stock

was already navigating a rough year for unrelated macroeconomic reasons. Sure. But finally, on September 9th, two full weeks after the initial alert, order fulfillment, manufacturing, and shipping are declared fully restored. Two weeks of severe operational degradation. Yeah. Normally, when a massive enterprise goes dark for half a month, we assume the attackers utterly destroyed the internal infrastructure. We assume the servers are melted slag and the databases are scrambled with military -grade encryption. But the forensic investigation tells a completely different story.

CrowdStrike finishes their analysis by September 18th, and the summary goes public on the 23rd Australian time. And the findings are defined entirely by what did not happen. Yeah, this part is wild. the investigators proved a massive almost confusing absence of malicious activity they found Absolutely zero evidence of data encryption. No activity in Microsoft 365 or their corporate email. Right. No interactive access to HR systems, manufacturing systems, industrial control systems, or research and development. There were no application

-level logins to massive enterprise tools like SAP, Salesforce, or any of their cloud apps. And the absolute biggest sigh of relief, no patient or customer data was accessed, staged for exfiltration, or taken. Even the existing implanted heart devices out there in the world and their monitoring systems were completely untouched. Though I think new activations for cardiac remote monitoring were temporarily disrupted. Yes, temporarily. But overall, the environment was pristine. Aside from the initial unauthorized entry at the perimeter,

the attackers did nothing. In technical terms, there was no lateral movement. Okay, so lateral movement being the attacker's ability to hop from the initial break -in point over to the really valuable stuff. Exactly. When an attacker breaches a network edge, they usually land in an unprivileged zone. To do real damage, they have to move laterally. Meaning they search for internal vulnerabilities, steal administrative credentials, stuff like that? Yeah. And hopping from server to server until they reach the quote -unquote crown jewels, like the customer database

or the core financial systems. So in this case, the attackers essentially broke into the foyer, couldn't figure out how to open any of the interior doors, and just stood there? Pretty much. Furthermore, no credible threat group even claimed responsibility. Really? Nobody tried to take credit. Well, the HIPAA Journal actually had to issue a correction after initially linking it to a ransomware group called Shiny Hunters. Oh, right. And a separate claim by a pro -Russian hacktivist group was completely unsubstantiated. There wasn't even a known CVE, a common vulnerability and exposure,

linked to the breach. Wait, hold on. I'm looking at this list of untouched systems. If no patient data was stolen, no files were encrypted, no ransomware deployed, and the cloud apps were perfectly fine, why on earth did the company panic and stay down for two weeks? It's a great question. I mean, why suffer all that financial damage and shut down the Cork campus if the attackers were just standing in the foyer and didn't actually break anything? That feels like a massive overreaction. It seems like an overreaction until you understand the reality of incident response. In today's

threat landscape. The most devastating operational damage isn't always caused by the attacker's weapons. Okay, what do you mean? Sometimes it is entirely caused by the victim's shield. Meaning Boston Scientific essentially did this to themselves? Like they caused their own outage? Yes. The two -week outage was the direct result of the company's own defensive containment strategy. Wow. When a security team detects an active, unauthorized intruder inside the network, But they don't yet have perfect visibility into how deep the intruder

is or what their intentions are. The standard responsible playbook is to immediately sever connections. You pull up the drawbridge to prevent the lateral movement we just talked about. Exactly. You lock it down. Which explains why the CEO, Mike Mahoney, stated publicly that all plants and distribution centers globally were shut down. Not just the specific server that was breached, but the entire global physical operation. Right. And that happens because of how enterprise networks are architected. Modern companies operate in a hybrid environment. They have cloud systems

like Salesforce for customer relationship management or Microsoft 365 for email. Which are hosted off -site on external servers. Those were perfectly safe. But the foundational on -premises systems, the localized servers that actually run the factory floor manufacturing robots, manage the physical warehouse inventory, and process real -time shipping orders, those are tightly interconnected. Yes. So when the security team realized the intruder had touched the on -premises network, they intentionally shut those internal systems down to ensure the

attacker couldn't use them to pivot or deploy ransomware. It's like finding a tiny leak in the plumbing of your guest bathroom, so you run down to the basement and shut off the main water valve to the entire house. That is exactly what it is like. The house is completely safe from flooding, which is great. But now nobody can take a shower, you can't run the dishwasher, and you can't wash your hands for two weeks while you wait for the plumber to meticulously check every single pipe to confirm the leak was just a loose washer. The cure, in the immediate term, genuinely feels as debilitating as the disease.

If we connect this to the bigger picture, it exposes a critical vulnerability in business continuity. Yeah, because Boston Scientific successfully survived the cyber threat. They protected their data, but their revenue stream took a massive hit. It demonstrates that knowing exactly which on -premises systems your physical business genuinely cannot function without is a critical map every company needs to draw before an emergency strikes. Because the business impact of throwing that main water valve is brutal. Oh, absolutely. Analysts

at J .P. Morgan pointed out a really harsh reality for the medical device industry. Remember, these are single -use devices. Right. If a hospital has a specialized surgery scheduled for Tuesday morning and your shipping is halted so the required stent doesn't arrive, the hospital doesn't just put the patient on hold for two weeks. No, they pivot to a competitor's product or they utilize an alternative method. So that sale isn't just delayed until Boston Scientific gets its servers back online. That sale is lost completely. Right. The company hopes to recover some of that revenue,

but a massive chunk of it simply evaporated because the factory was forced to hold its breath. Business leaders, not just IT departments, have to be deeply involved in network architecture decisions for this exact reason. Yes. If your critical order fulfillment server sits in the same blast radius as a vulnerable edge device, your entire global revenue stream is at the mercy of your own containment protocols. Which brings us to how this all started. How did these ghosts even get into the foyer in the first place? It wasn't

an employee clicking on a bad link in a phishing email. And it wasn't a stolen laptop left in an airport lounge. The initial vector was an external facing network management device. We don't know the specific vendor and we don't know the exact software flaw, but it was essentially a piece of hardware sitting on the edge of their network. Right. They ended up decommissioning the device entirely, blocking the attacker's infrastructure, resetting all global passwords, and hardening the environment. Because these edge devices, routers, firewalls, load balancers,

VPN gateways, they are the new front line of cyber warfare. A VPN gateway, for example, is literally designed to act as a door between the wild open internet and the secure internal network. It has to face outward to allow remote employees to log in. Kinsoft's main advice in the source material is incredibly adamant about this vulnerability. These edge devices must be patched obsessively. They require mandatory multi -factor authentication, or MFA. Yes, and critically, the management interfaces, the secret portals used by IT admins to actually

configure the device settings, should never be exposed to the open internet. They should be hidden behind another layer of security. Here is where it gets really interesting. This wasn't a sophisticated, highly coordinated, Ocean's Eleven style heist. No. It was a boring, likely forgotten network management box just sitting out there on the internet that brought a 59 ,000 person global giant to its knees. It's the digital equivalent of investing millions in vault doors and laser grids, but leaving the basement window

unlocked. Exactly. Because attackers use automated tools to constantly scan the entire Internet 24 -7, looking specifically for those unlocked basement windows. But the real triumph of Boston Scientific's response, the only reason this story doesn't end in a catastrophic regulatory nightmare regarding data privacy, comes down to something equally boring but incredibly vital. Which is logs. Network logs. Yes. CrowdStrike was only able to confidently announce that no data was taken because Boston Scientific had the meticulous,

comprehensive network logs to mathematically prove it. OK, but how does a log actually prove a negative, though? How do you prove someone didn't take something? Think of a log like a highly advanced digital turnstile combined with a security camera. OK. It doesn't just record who enters a room. It records exactly how many bytes of data they interact with and, crucially, how many bytes of data flow back. out of the network. Right. A central logging system, often called a SIM, aggregates all this traffic. If

the logs show an unauthorized IP address connected to a server, but the outgoing traffic log registers zero bytes of data transferred back to that external address, you have mathematical, forensic proof that no files were exfiltrated. Wow. And without that undeniable mathematical proof, it is a totally different reality. It is the legal difference between telling your customers nothing was taken versus we have no idea what they took. Right. Under strict regulatory frameworks like Australia's Privacy Act, mentioned in our source material,

if a company cannot definitively prove that data wasn't taken during a breach, they are legally forced to assume the worst. They have to declare a notifiable data breach. That means alerting government regulators. Directly contacting 4 .8 million patients. facing potentially massive financial fines. And suffering catastrophic long -term reputational damage. All because they lacked the data to prove a negative. Keeping those logs actively saved them from a regulatory apocalypse. It really did. It allowed leadership to stand

up and say, with receipts, our patients are safe. Which perfectly sets up how they handled the public communication of this entire mess. Yeah, this case is actively being praised as a masterclass in crisis communication. It serves as a textbook model for how corporate transparency should function during an active crisis. It closely mirrors the continuous disclosure obligations that ASX -listed public companies are held to in Australia. Right, because usually companies try to sweep these incidents under the rug, or they wait until late

on a Friday night to release a vague, jargon -filled statement hoping the news cycle just swallows it. But Boston Scientific played it entirely straight. First, They filed a voluntary disclosure with the SEC on day one. They didn't even know the full scale of the problem yet, but they immediately raised their hand and said, something is wrong, we are actively looking into it. From a leadership perspective, that is a difficult decision. The stock market fundamentally hates uncertainty, and admitting a breach before you have all the answers guarantees a short -term

hit to your valuation. But they kept going. Step two, they provided regular, ongoing public updates. They didn't go dark for two weeks while the factory was down. Right. Step three, once the financial reality actually became clear, they filed the formal material incident SEC filing, admitting openly they were going to miss their financial guidance. And finally, step four, they published the actual forensic summary from CrowdStrike at the end, detailing exactly what the attackers touched and, more importantly, what they didn't.

What stands out to you about how this was handled? Think about how you usually hear about corporate data breaches as a consumer. Yeah, it usually involves a leaked memo or an investigative journalist forcing the company to admit a failure months after the fact. Exactly. What stands out here is the realization that early honesty builds resilience and trust. Yes, the market punished their stock price in the short term. But by controlling the narrative with verified facts, rather than letting rumors and panic fill the void, they protected the long -term integrity of their brand.

Patients and doctors still trust their medical devices because the company proved in real time that they prioritize transparency over saving face. It's the exact same dynamic as hearing bad news from a friend directly versus finding out they lied to you from a third party. Oh, absolutely. You can usually forgive the mistake, but the cover -up destroys the relationship permanently. And by publicly releasing the CrowdStrike forensic summary, they actively contributed to the collective defense of the entire medical device industry. Oh, that's a great point. Other massive enterprises

can look at that specific report, identify that they use those exact same network management devices, and go secure their own perimeters before the attackers scan them next. Exactly. Well, we have covered a massive amount of ground today. We've gone from a global manufacturing shutdown to the intricate architecture of network logging and the psychology of corporate PR. So what does this all mean? Let's distill the core takeaways. Right. First, the edge of your network, those incredibly boring external routers and VPN gateways,

they are your biggest liabilities. They are the unlocked basement windows. Second, you do not need a terrifying ransomware infection to suffer a catastrophic business outage. Your own defensive containment protocols can be just as paralyzing to your bottom line. And third, having exhaustive, unalterable network logs is your absolute only defense against regulatory nightmares. Logs are the only mechanism you have to mathematically prove a negative and save your company's reputation. It demands that we completely redefine what readiness

actually means for a modern enterprise. It really does. And that brings us to our call to action for you listening right now. Think about your own workplace, your own company, or even your personal home network setup. Do you know what single point of failure would grind your entire day to a halt if you had to physically pull the plug to stop an intruder? What is the one core system you genuinely cannot run without? And is it sitting dangerously close to an exposed edge device? It is a map worth drawing today before the alarms actually go off. And as you

map that out, consider this final thought. We started today talking about the bank manager who locks the doors to protect an untouched vault. effectively bankrupting the business in the process. As cyber threats become increasingly ambiguous and our automated defensive containment protocols become more aggressive to match, we have to wonder, will the most destructive, expensive cyber incidents of the future actually be caused by attackers at all? Or will they be caused by companies being

forced to completely paralyze their own operations just to prove to the regulators that they are safe? Now that is a thought to keep you up at night. The shield becoming heavier and more dangerous than the sword. Thank you for joining us on this deep dive into the modern mechanics of cyber warfare and corporate resilience. Keep questioning, keep learning, and we will catch you next time.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Iris Ohyama - A Suspicious File in the Cloud, 7.7 Million Customers at Risk, and an Online Store That Went Dark

    Nov 19, 202620 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Japanese home goods company Iris Ohyama (online store operator Iris Plaza) found a suspicious file in an external...

    Credit the people on this episode

  2. Who Gives A Crap - A Marketing Supplier Breached, Six Days to Tell the Client, and Customer Data That Didn't Need to Be There

    Nov 17, 202619 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Australian online retailer Who Gives A Crap told customers on 7 November 2026 that their information was accessed...

    Credit the people on this episode

  3. Last Week in Tech - An Outlook Zero-Day That Leaks Your Password Hash, Chrome's Eighth Exploited Bug, and Nvidia Without Jensen Huang

    Nov 15, 202621 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Last week in tech, 7 to 14 November 2026. Microsoft's November Patch Tuesday (10 November) fixes well over a...

    Credit the people on this episode

  4. Chainalysis - From "Non-Sensitive" to "All Users": How a Breach Notice Changed in Five Days

    Nov 12, 202619 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Chainalysis disclosed on 30 October 2026 that an external actor using "offensive agentic techniques" accessed...

    Credit the people on this episode

  5. NSW Health - A Dental Voucher Website, Four Gigabytes Taken, and the Providers Whose Details Were Exposed

    Nov 10, 202623 minAudio

    Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! NSW Health reported unauthorised access to its Oral Health Fee For Service Scheme website on 29 October 2026;...

    Credit the people on this episode