Before the breach: Cloud breach response best practices

One of the most difficult and damaging events that can occur for any business’ infrastructure is a breach. However, breaches occur when proper planning hasn’t gone into an infrastructure contingency plan.

There are several areas of consideration that need to be fully planned for before any IT strategy and data objectives can be balanced in the face of a potential breach: whether technical, HR, or compliance, have a response plan for each area is necessary before any problem ever arises.

In this post we will explore the technical considerations that go into breach planning. So where do you start in planning your cloud breach response?

Know where the data lives

Understanding what your data is, where it resides in your systems, and how the data flows is of the utmost importance when beginning your technical planning for breach protection. It’s surprising to considering that given the importance of data, many organizations don’t have a complete handle on their data flows through various different levels of the application, especially in situations where it might be exposed.

These are things that you have to know if you’re trying to respond to a breach and are trying to drill down into where could things have been exposed that shouldn’t have been. You don’t want to be sorting that out after.

Logging for success

It’s important to make sure in advance you have all the right types of reporting and management and logging protocols in place, not just your regular server logs. Your application logs need to be centralized and put some place that will be easily accessible and a source where it’s easy to correlate what happened against the server logs, firewall logs and everything else at the same time.

Depending on where things are stored and at what level information becomes accessible to be breached, businesses have to think very carefully of what they have to log in the application. They should log specific user access. But you don’t want to log anything that gets displayed to users because you don’t want ePHI to be in the logs (which does happen). One of the things you have to check for in PCI compliant hosting, for instance, is anything that actually could be a credit card number.

Separation of church and state

You definitely want to know what the separate roles are for people who have access to the systems and based on that whether there’s the likelihood that someone has the wrong type of permission and got to things that they shouldn’t have. Then there’s always the question of, once you have drilled down and figured out where the vector a breach may have happened and what might have gotten compromised, how you actually get to the source of the root cause analysis.

This will help frame the steps that need to be taken depending on whether it was a person or something in the software.

Where do MSPs fit?

MSPs can’t handle all breach planning and response protocols because they are primarily on the OS and infrastructure side. So they have to be able to collaborate with clients, by providing insight into the layers of the stack that they have access to or requesting more information from within the application to compare to the logs they have with those they don’t.

The reasons to share? You might realize there’s an ongoing problem, but you might not be able to tell when it started without these sharing protocols in place.

Bottom line: Setting up protocols and communication channels between your organization and your MSP ahead of time is super important. However, the technical response is only part of the planning. Check back for our next segment which explores the legal/compliance and HR planning necessary to avoid or deal with a breach.

What are your thoughts on breach planning? Let us know on Twitter @CloudGathering.

The post Before the Breach: Cloud Breach Response Best Practices appeared first on Logicworks Gathering Clouds.

Related Stories

Leave a comment


This will only be used to quickly provide signup information and will not allow us to post to your account or appear on your timeline.