Latest / Decrypted: The UK Cyber Briefing / The Craneware breach, and the 2,000 hospitals waiting on Edinburgh
Transcript
- 0:03This is Decrypted. Sunday, the twenty-sixth of July.
- 0:07The Craneware breach, and the 2,000 hospitals waiting on Edinburgh.
- 0:12Craneware is an Edinburgh company, listed on A I M.
- 0:17It makes billing and pricing software used by more than 2,000 US hospitals, and around 10,000 clinics and pha
- 0:26rmacies. On Monday it told the London Stock Exchange that hackers had accessed "a subset of its data environme
- 0:34nt."
- 0:38They also took some employee data, and a slice of customer and partner records.
- 0:43The company has told the Information Commissioner's Office and the F B I.
- 0:48It's brought in external forensics.
- 0:52And it says operations were never disrupted.
- 0:54Its shares fell nearly 10% anyway.
- 0:58This is a useful story precisely because it isn't dramatic.
- 1:03Craneware appears to have done most of what good incident response looks like, and still ended up here.
- 1:09Next. What was actually taken.
- 1:13Craneware is careful to say a lot of what was copied is "non-sensitive or already public" data.
- 1:21Plus file names, rather than confirmed file contents.
- 1:26Don't read that as nothing happened.
- 1:28Picture an attacker who walks away with an index of file names across a shared billing platform.
- 1:34They've effectively photographed the labels on every folder in the cabinet, without opening one.
- 1:41And Craneware sits between thousands of hospitals and their revenue.
- 1:45So knowing which folders exist, and for which named customers, is useful reconnaissance in itself.
- 1:52It could feed a follow-on phishing or business email compromise run against any of those 2,000 hospitals.
- 1:59Dressed up as routine Craneware correspondence.
- 2:03And finally. The design lesson, not the disclosure lesson.
- 2:08The attack stayed a "subset" of the environment.
- 2:12That's evidence some segmentation was already in place, and it's worth crediting rather than assuming failure
- 2:19.
- 2:26So a "subset" is still a large blast radius, measured against any single hospital's own risk appetite.
- 2:33The Secure by Design principle at stake here is tenant isolation, not just functional isolation.
- 2:40A vendor holding data for many customers should be architected so that a compromise of its own corporate envi
- 2:47ronment can't cross into any individual customer's data.
- 2:51By default, not by policy.
- 2:53Quick disclosure to the I C O and F B I, and bringing in outside forensics fast, is genuinely good practice.
- 3:01But that's the response bar.
- 3:03The design bar is making sure the tenant boundary held before any of that becomes necessary.
- 3:09If you're a UK software firm selling into regulated sectors overseas, healthcare especially, treat this as t
- 3:17he standard to build to. Not just the standard you'll be judged against afterwards.
- 3:21That was Decrypted. The written version and every source are linked in the show notes.
- 3:27Thanks for listening.