Security is Security, regardless of location

Security is Security, regardless of location

Let’s face it, the cloud is here to stay. If you are resisting it because of security, then you are probably not security focused with your on-premises assets either. Psychologically, it is always reassuring to know that all your data is sitting within your firewall, secured by the lack of access and accessible by a pipeline that you control at all times. That alone is a false positive that can get most companies in trouble, because it can create ease of mind and leave you in a dangerously relaxed state. Vulnerabilities are not a simple bi-product of the geographic location of data. They exist because of a lack of focus on governance and rigorous processes that continuously revisit your security policies. Some of the more high profile breaches we hear about in the news have come from within. It is not always a hacker finding a path from the outside in, but an outsider exploiting you by utilizing methods that require one of your own to inadvertently, or advertently, expose your data.

The number of security products in the marketplace that advertise securing all things IT are numerous and most of them are good products. None of them can replace well designed processes and frameworks that ensure your chances of a breach remain minimal. Humans use software, so humans need to be governed to ensure they are not the cause of a breach.

Are security reviews injected at various layers of your IT ecosystem? They should be. The difference between a good secure infrastructure and a great one is the cadence at which you revisit your security framework to keep up with the changing IT landscape. I am not suggesting endless meetings, but a realistic dose of recurring security reviews and security processes/framework updates.

 How to proceed:

  1. You should hire an external firm to review your security
    1. You need somebody to tell you that your baby is ugly.
  2. Make auditing a quarterly exercise at a minimum
    1. Update your auditing checklist often.
  3. Inject security reviews in everything IT
    1. Do you have a BYOD policy? If your employees can bring their own devices into the workplace, make sure you are managing these devices.
    2. How are you ensuring company owned assets that leave your building are secure in case they are lost or stolen?
    3. How are you ensuring company owned assets that never leave your building are secure?
  4. Even the most technical of employees are not security focused
    1. If you have in-house developers, make sure their code is reviewed by their peers or an external development firm. Developers never think there's anything wrong with their code.
  5. Eliminate shadow applications
    1. A line of business that needs a specific application to do their jobs effectively must go through IT to get the application on-boarded.
  6. Standardize
    1. Different operating systems and different browsers and different versions make it messy and will always result in you missing something during a review. Choose one or two versions of everything and enforce it. You don’t necessarily need to be running the latest and greatest, but it’s time to sunset your Windows XP clients (Vista too) and your Windows Servers 2003.
    2. Find the budget to update legacy products. It’s a lot more cost effective to buy a Windows Server 2012 License than to get your Windows Server 2003 hacked.
  7. Create layers for access
    1. It is cumbersome to go through two or three layers of authentication to access data, but it is more cumbersome and expensive to clean up.  
    2. A password, even a complex password that expires regularly, is not enough. What other form of authentication are you using?
  8. Isolate
    1. Understand the various businesses and roles in your company, from end to end. If a breach happens because of employee negligence, is it in silo and not far reaching?
  9. Diagrams are fun to build and useful too
    1. Take the time to build a detailed (very detailed) diagram of your network topology and all the assets within. Update it often. It’s the next man up model. Even a junior IT employee should be able to look at it and understand how to shut off the leaking pipe and act quickly when necessary. I bet you don’t have one today and if asked you’ll need ten people in a conference room talking over each other to explain the complexity of your infrastructure.
  10. IT is not just servers and laptops and mobile devices
    1. HVAC?

To view or add a comment, sign in

More articles by Joseph Khalaf

  • Simplicity fronting Complexity

    There’s nearly a 100 percent chance that if you are reading this, you own a smart phone or a tablet…unless you’re…

    2 Comments
  • To Excel or Not to Excel

    In 1995, I had the honor of being hired by Microsoft to work on the Excel team. Ever since I worked so intimately with…

    8 Comments
  • Automation or Bust: How Upgrading Your Software SAVES Your Business Money

    Every few thousand miles or so, we get the oil changed in our cars. We do this because it’s a piece of required routine…

    2 Comments
  • Out of the box: The Myth

    For the third time in as many months, I have had clients ask me about finding a product that meets their exact…

  • Has Microsoft Licensing upset the faithful?

    After a 17 year career at Microsoft it would be fair to admit that I have great loyalty for the company and all of its…

    7 Comments
  • Missing out on a movie night and a good laugh

    While not a big sucker for sensational news and excessive coverage of any one topic, especially when it comes to…

    5 Comments

Others also viewed

Explore content categories