Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Royal Security Fail: 'May I Speak To Kate?'
Newest First  |  Oldest First  |  Threaded View
PJS880
PJS880,
User Rank: Ninja
12/17/2012 | 4:27:28 PM
re: Royal Security Fail: 'May I Speak To Kate?'
It was a very foolish prank but it did prove that the hospital; was not trained properly. That is not the nurse's fault she did not do anything wrong in my opinion. Social engineering attacks are just that they prey on human behaviors and that is all this was. It a an elaborate social engineering skit for entertainment purposes. Did the DJ know that what they were doing was 'hacking' probably not, and thought it was just that a prank call. Hopefully the hospital will use this information and properly train their staff so as this dopes not happen again.

Paul Sprague
InformationWeek Contributor
jaysimmons
jaysimmons,
User Rank: Apprentice
12/13/2012 | 7:19:54 PM
re: Royal Security Fail: 'May I Speak To Kate?'
I agree with Paul CerratoGs comment: You canGt blame others for having poorly trained staff or allowing such a low-level setup to work. At the end of the day, everyone that has access to patient information should be trained on how to handle such information.

Jay Simmons Information
Week Contributor
pcerrato10
pcerrato10,
User Rank: Apprentice
12/7/2012 | 6:36:34 PM
re: Royal Security Fail: 'May I Speak To Kate?'
"Our nurses are caring and professional, and not used to coping with this sort of journalistic trickery." What a poor excuse.

The author has a point. The hospital should be training staffers to spot tricksters like this.

Paul Cerrato
Editor
InformationWeek Healthcare


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-38235
PUBLISHED: 2022-08-16
XPDF commit ffaf11c was discovered to contain a segmentation violation via DCTStream::getChar() at /xpdf/Stream.cc.
CVE-2022-38236
PUBLISHED: 2022-08-16
XPDF commit ffaf11c was discovered to contain a global-buffer overflow via Lexer::getObj(Object*) at /xpdf/Lexer.cc.
CVE-2022-38237
PUBLISHED: 2022-08-16
XPDF commit ffaf11c was discovered to contain a heap-buffer overflow via DCTStream::readScan() at /xpdf/Stream.cc.
CVE-2022-38238
PUBLISHED: 2022-08-16
XPDF commit ffaf11c was discovered to contain a heap-buffer overflow via DCTStream::lookChar() at /xpdf/Stream.cc.
CVE-2022-36141
PUBLISHED: 2022-08-16
SWFMill commit 53d7690 was discovered to contain a segmentation violation via SWF::MethodBody::write(SWF::Writer*, SWF::Context*).