[fusion_builder_container hundred_percent=”no” equal_height_columns=”no” menu_anchor=”” hide_on_mobile=”small-visibility,medium-visibility,large-visibility” class=”” id=”” background_color=”” background_image=”” background_position=”center center” background_repeat=”no-repeat” fade=”no” background_parallax=”none” enable_mobile=”no” parallax_speed=”0.3″ video_mp4=”” video_webm=”” video_ogv=”” video_url=”” video_aspect_ratio=”16:9″ video_loop=”yes” video_mute=”yes” overlay_color=”” overlay_opacity=”0.5″ video_preview_image=”” border_size=”” border_color=”” border_style=”solid” margin_top=”” margin_bottom=”” padding_top=”0px” padding_right=”” padding_bottom=”0px” padding_left=””][fusion_builder_row][fusion_builder_column type=”1_1″ layout=”1_1″ spacing=”” center_content=”no” hover_type=”none” link=”” min_height=”” hide_on_mobile=”small-visibility,medium-visibility,large-visibility” class=”” id=”” background_color=”” background_image=”” background_position=”left top” background_repeat=”no-repeat” border_size=”0″ border_color=”” border_style=”solid” border_position=”all” padding=”” dimension_margin=”” animation_type=”” animation_direction=”left” animation_speed=”0.3″ animation_offset=”” last=”no”][fusion_text]
If you are reading this blog post, you have survived 2016. By most accounts, it was a rough year in regards to the state of security in healthcare. Cyber attacks have been no exception to this calculation. We saw the announcements of some of the biggest breaches in history, the continued proliferation of ransomware, and even the recent reports that Russia was meddling in U.S. politics through attacks on IT security.
Let us, as a collective, decide to do better this year. Most of the atrocious breaches and other IT security related incidents could have been avoided if we could be smarter about our security hygiene. Security starts with basics, and that is where we need to return to this year.
Back to the Basics
Before we start to spend boatloads of money on new security solutions, like new software and hardware, we should look at what is currently in place and identify how it can be more effectively implemented and/or better protected. For example, I perform penetration testing and security assessments almost every working day. Oftentimes, I find simple mistakes that could easily lead to compromising sensitive data. Most of these issues are directly related to missing patches or, even worse, using end-of-life (EOL) and deprecated software.
Can you answer these questions confidently:
- When was the last time you did a vulnerability scan on your network?
- How many findings were there?
- How many of those would still be there if another scan was run today?
Obviously, the above are rhetorical questions, and I don’t expect a deluge of emails answering them. However, I am curious as to how you might answer these questions.
Furthermore, if you were to conduct a new scan, would that scan have similar results as the previous scan? If so, you are not alone … almost everyone is in that same boat. But, why is this? The immediate answer is that it is too easy to put things off, wait for a new system to replace the vulnerable one, or ignore fixes due to lack of time. Unfortunately, this is the pervasive attitude, and it is time for a change.
How to Adjust
One of the single greatest security improvements that we could make to this approach is to address the security concerns that already exist today and make better use of what we have, with what we already have in place. Before you start blowing the seemingly endless 2017 budget on bigger and better analytics or a rack-mounted box of silicon and aluminum that promises to save the day through security black magic, consider your own house first. How long ago did you intend to have all the EOL systems off the corporate network? Are you still accepting TLS version 1.0, or worse yet any version of SSL? These are just a few examples that I see most often.
I also propose that we should make initiatives and follow through to address old systems shored up. For example, what if the firewalls, database, or system is due to be replaced this year? Attackers are not looking for issues to exploit next month or even tomorrow, rather they are looking for these type of cracks in the perimeter. I am by no means suggesting that you should halt improvements and upgrades. Instead, I am suggesting that these types of issues should not be used as an excuse to ignore vulnerabilities that reside on the network right now.
What Can We Do?
What we once thought of as a wall around our network is now more of a porous mesh that lets almost anything through. We let users bring in their own mobile phones, connect them to corporate email, and trust they won’t allow their device to be compromised. We have all opened countless ingress and egress points in our once solid walls to allow cloud-based services to be accessed, allow our users to access the web, and allow external devices (BYOD and contractor provided) to access the internal network. This is the new face of security and should not be ignored. Our attack surfaces are growing exponentially every day, and new fixes will not make a difference if we ignore the issues we already know about.
I suggest to step back and evaluate all the security vulnerabilities that were pushed to the back burner last year and ask how many could be the root cause of an upcoming incident. Then address, reassess and prioritize your available resources that can help remediate threats. Approach the here and now, plan for the future, but don’t rely on it as a fix for all vulnerabilities that are present in this moment. It is also important to remember that business should continue as usual during this process and that CynergisTek has resources that can help you with that assessment.