Tomorrow.

Our thoughts and ideas on what's next.

visit levick.com

Levick Blog

Tomorrow.

close

Connect.

We're on.
And we're available.

DC

1900 M Street NW
Washington, DC 20036
P 202.973.1300

NY

122 East 42nd Street
New York, NY 10168
P 917.612.8419

CHICAGO

70 West Madison Street
Chicago, IL 60602
P 312.214.2300

SF

535 Mission Street
San Francisco, CA 94105
P 415. 433.0100

Guest Author

May 15, 2017

Ransomware Spreading Like Crazy Worms

It All Just Makes You Wanna Cry

Curiosity, turned blind luck, saved us from something far worse from what we saw on Friday.  Had it not been for a British malware researcher registering some gobbledygook of a domain name (www [dot] iuqerfsodp9ifjaposdfjhgosurijfaewrwergwea [dot] com to be exact), who knows what we would be writing about today. At the rate we are going, if we were cats, we would be burning through our nine lives faster than Tony Stark builds Ironman suits.

In our last post, we said to stop sensationalizing.  We mean that. So by no means should you think that we are a tad bit overly hysterical, because WannaCry did spook us all out. Friday’s episode is proof positive of three things:

  • Things can get wildly out of control real fast.
  • Cyber weapons have made it out into the wild and will be used against us.
  • We were horribly unprepared for this attack; we are still horribly unprepared for the next attack. 

Luck – while a critical aspect of life – is not an effective resilience strategy.  WannaCry has already been modified and there are variants with no “kill switch” in the code. More hurt is in order for the unprepared.

What should concern us all was the brazenness of this attack.  Everything was fair game, from telecom to banks to healthcare to universities, and latest count is that people “wanna cry” in 150 countries.  That’s some aggressive foreign policy when you negatively impact 75% of the world’s nations in 72 hours.

The attack on healthcare is particularly disturbing – losing money is never fun, but losing lives is worse – but not unexpected and perhaps even a bit overdue.  Healthcare is a peculiar industry because of competing interests.  Specifically:

  • Patients and users require speed, but information security often takes time to process, putting the needs of front-line staff in opposition to the wants of security staff.
  • Management must be committed to quality care and their fiduciary duties, no easy task in an environment of competing needs.
  • Effective sharing of confidential patient information among primary care physicians, hospitals, and medical specialists has myriad benefits, but sharing introduces numerous potential points of failure.
  • Budgetary constraints which are felt more than in most industries as healthcare funding is becoming more difficult to secure and cybersecurity costs keep rising.

There is this issue of course that applies to all leading-edge firms, not just those in healthcare: if you want to be recognized as the “leader of your field” you also have the biggest juiciest target tattooed to your back.

And of course, there is this thing called emotion.  It is quite possible you will dial your “freak out factor” to 11 if you are already in a life-and-death situation and suddenly find out your computer is useless to you.  Should you find yourself in this situation, scrambling to find $300 worth of these funny things called Bitcoins may be a cheap way out.

We need to underscore how lucky we were and it is quite possible that by the time you read this, we are feeling second and third waves of WannaCry.  So here are some quick solutions and things to think about:

  • Back up your crown jewels like it’s going out of style. If you did not back up your data this past weekend, whether offline or on the cloud (or both) you deserve a failing grade.  Malicious actors have proof that ransomware pays off.  So long as there are people that are willing pay, malicious actors will keep on putting out ransomware.  The only way to stop this tactic is to eliminate the incentive.  Losing one day’s worth of data is a whole lot less painful than your entire digital library.  Over the long-term, the costs of doing nothing are exceedingly higher than doing something, so find an option that keeps your data out of harm’s way.  Backing up your data should become as regular and mundane as brushing your teeth (and you know what happens when you do not brush your teeth).
  • Have a recovery plan that can be activated in minimal time. Have clean images of operating systems and critical applications ready to be installed in a moment’s notice.  Of course, this is under the assumption you have your data backed up and ready to follow.  And by the way, if you have not tested your plan, you do not have a plan.  If you decide not to test your plan, make it out of wood and knock on it for good luck.  You may increase your chances of success.
  • Prepare for the Stone Age. We are actually very serious here.  For anybody born before 1989, there is a pretty good chance you used a pencil and paper somewhat regularly while growing up.  This may come as a shock to some, but for a good 5,000 years or so we got through life without electricity and digital technologies.  It was not pretty at times, but in a pinch, it works.  Remember, your success depends on your ability to bend while others are breaking.  If you are able to operate with “Stone Age technology” for 72 hours, you are ahead of the game.  If we are all down for more than 72 hours, chances are we have a much bigger problem on our hands (like, war).
  • Look before you cross the road (think before you click!). Would you cross a busy freeway of speeding cars going in both directions without looking?  Alright, so why would you just click something out of curiosity or because you are too lazy to look where it could take you?  Hover over a link and make sure the link goes to where it says it will go.  Read the email closely (one of us received an email from “concast.com” this week).  And if it feels wrong, just press delete.  Do not become the next “phish” that gets hooked!
  • Do not wait for the dam to come apart before you start patching. Enterprises are notoriously slow at patching their systems.  This is particularly true of small-to-medium businesses.  If you cannot do this, team up with a managed service provider (MSP) or managed security service provider (MSSP).  If you are not “patching and praying” on a regular basis, you are committing “sin” and will likely be punished for your misdeeds.
  • If you can afford it, seriously consider Artificial Intelligence, Machine Learning, and Cognitive Computing. We are still early into the wide-spread commercialization of these offerings, but they are the way of the future.  If you identify and stop (or even slow down) an attack before it ruins your day by using any one of these technologies, it is a win for your organization.
  • Putting all your eggs in one basket means they can all break at once. Sometimes keeping things apart is a good idea.  In our mad rush to connect EVERYTHING perhaps we overlooked some basics.  We really need to ask questions such as: do I really want the sales department to have the ability to connect to our super advanced R&D department?  Logical and physical segmentation of network and data assets needs to be looked at in more depth as a viable strategy (and remember you can use the cloud in this strategy).
  • Sharing is caring. The need for enhanced public/private cooperation will be critical in maintaining a knowledge base to track and counter future ransomware cyber threats. The new NIST Framework in conjunction with the Department of Homeland Security’s (DHS) cyber-threat information-sharing program implemented as part of the 2016 Cybersecurity Information Sharing Act (CISA) is a good basis to encourage more sharing of information threats.  And the cybersecurity Executive Order from May 11th is a good step in the right direction.
  • Time to have a serious policy discussion on Zero Day vulnerabilities and other exploits. Zero Day vulnerabilities and other exploits should be treated like neutron bombs able to run amok.    Note: we are all patriots first and understand that our nation’s military and intelligence agencies require – need – the ability to take advantage of these exploits, but if we are to keep a cache of these weapons in a stockpile, they need to be protected like the launch codes.  And if we do catch wind that of vulnerabilities that get out into the wild, patch them up at warp speed.

We offer these practical solutions to you in order to protect and secure what matters most to all of us.  We dodged a serious bullet on Friday and by no means are we in the clear.  Let this be a lesson to us, because by the time you read this, we may be feeling the #MondayBlues thanks to WannaCry Vol. 2.

In Defense of the United States of America,

The #Cyber Avengers

The #CyberAvengers are a group of salty and experienced professionals who have decided to work together to help our country by defeating cybercrime and slowing down nefarious actors operating in cyberspace seeking to exploit whatever their tapping fingers can get a hold of.  How?  We do this by raising our collective voices on issues critical importance so that we can keep this great country in the lead – both economically and technologically – and to keep it safe and secure.  All the issues are intertwined and more complex than ever, which is why we have differing backgrounds but have a common cause.  We complement each other, we challenge each other, and we educate each other.  What do we get out of writing articles like this?  Nada.  Goose egg.  We are friends.  We are patriots.  And we are not satisfied to sit around and do nothing.  We want to keep this nation and its data safe and secure.

The #CyberAvengers are: Paul Ferrillo, Chuck Brooks, Kenneth Holley, George Platsis, George Thomas, Shawn Tuma, Christophe Veltsos

Comments:
Categories: Public Affairs
Tags:
Posted by: Guest Author

2 Comments

  • http://tmv.com/special June Klein

    What services or setup do you recommend for windows 10 vmware w2008 server backup?

    • https://isicg.com Kenneth Holley

      June – I would be happy to assist with your question. Am I understanding correctly that you are looking to backup Windows 10 running via a VMware hypervisor installed on Server 2008? Assuming so, specific approaches below:

      If you’re looking to only backup on the data contained on the Windows 10 machine, the 3-2-1 rule is a best practice for backup and recovery. It means that when you build out your backup and recovery strategy you should:

      1. Keep at least three copies of your data
      That includes the original copy and at least two backups.

      2. Keep the backed-up data on two different storage types
      The chances of having two failures of the same storage type are much better than for two completely different types of storage. Therefore, if you have data stored on an internal hard drive, make sure you have a secondary storage type, such as external or removable storage, or the cloud.

      3. Keep at least one copy of the data offsite
      Even if you have two copies on two separate storage types but both are stored onsite, a local disaster could wipe out both of them. Keep a third copy in an offsite location, like the cloud.

      The 3-2-1 backup rule is a best practice because it ensures that you’ll have a copy of your data no matter what happens. Multiple copies prevent you from losing the only copy of your data. Multiple locations ensure that there is no single point of failure and that your data is safe from disasters such as fires and floods.

      It’s also prudent to ensure that the Windows 10 virtual machine itself is properly protected. There are several very good solutions which leverage AWS, for example, to provide protection for virtual machines. Also, if you’re running vCenter in conjunction with the hypervisor then you can take advantage of built-in virtual machine backup (and recovery) features.

      I will stop short of recommending any solutions by name, however there are many, many very good online / offline backup solutions out there.

      Warm Regards,

      Kenneth