September 13, 2016
The recent jump in cyber attacks against the healthcare industry—especially ransomware attacks—aren’t a coincidence. The reality is that the healthcare industry presents the perfect opportunity for attackers.
A balance of valuable personal data and hospitals that simply aren’t prepared for advanced attacks.
In May 2016, the Diabetes Technology Society (DTS) took a step forward in defending the new world of connected healthcare devices by releasing the DTSec standard. Now the question remains—can this new standard change the cyber security narrative for an ailing healthcare industry?
The DTS Cybersecurity Standard for Connected Diabetes Devices (DTSec) was released with the goal of making the healthcare industry more confident in the security of network-connected medical devices. While the standard will first focus on life-critical diabetes devices (such as insulin-pump controllers), it can be applied to any medical product.
DTSec hinges on thorough, independent expert evaluations of connected healthcare devices. The DTSec standard contains specific performance requirements that provide a concrete measurement platform for device security.
Certain approved labs will conduct the DTSec tests and the fundamental idea is that having multiple stakeholders involved in the process—not just a biased vendor—will improve the state of healthcare security.
With the ISO/IEC 15408 international standard for computer security certification at its heart, DTSec can potentially offer the healthcare industry a framework necessary for protecting Internet of Things (IoT)-enabled devices. However, the truth is that deploying medical devices that are built with security in mind is only one step toward securing electronic health records.
Urgent patient care is the chief concern for healthcare providers, which is why budget is generally used for increasing staff as opposed to consistent security equipment upgrades. However, IoT-enabled devices are becoming essential to providing quality patient care and improving outcomes in life-or-death moments.
Improving the security features of connected healthcare devices is important, which is why DTSec is such an important new standard. As IoT-enabled products become more inherently secure, the entire stack of security solutions must improve as well.
Keeping hackers from controlling devices such as insulin-pump controllers is an obvious concern for patient safety. However, The DTSec standard does not include testing or certification for in-line security appliances such as next-gen firewalls and intrusion prevention systems.
As IoT devices collect increasing amounts of patient data, defending hospital networks themselves—not just the smart devices—will become more critical than ever. Without a solution in place to identify and mitigate attacks, having DTSec-approved devices in place won’t mean much.
DTSec can certainly change the narrative for IoT-enabled medical device security. However, the narrative remains the same for the rest of the healthcare network. In any cyber security strategy, visibility must be the first step—especially as more inline security appliances become necessary at the edge of the network.
2015 may have brought the 5 biggest data breaches in the healthcare industry, but 2016 is proved to be equally troublesome for healthcare providers. Budgets are tight, but you have to build visibility into your cyber security plan as you continue complicating the security stack.
Looking to add inline or out-of-band security monitoring solutions, but not sure where to start? Join us for a brief network Design-IT consultation or demo. No obligation - it’s what we love to do.
If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.
If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.
While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.
Some of you may have noticed a flaw in the logic behind this solution! You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.
Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.
Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.
Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.