As a small or mid-size company you may feel limited in what you can do to detect a data breach but this week’s discussion in the Back to Basics Series: How to Detect a Data Breach covers concrete steps to implement.
Panel is hosted by SideChannel’s Managing Partner, Brian Haugli and this session’s guests are Adriana Petrillo, J.D., CISSP, Cyber Security Specialist, CISA and SideChannel’s Principal Consultant & vCISO Terry Chapman.
It wouldn’t a proper “Back to Basics” if we didn’t start with, well, the basics. A good plan of attack in determining the best way to detect a data breach begins with laying the proper groundwork and NIST provides a solid foundation for this - Identify, Protect, Detect, Respond, Recover.
For organizations that have limited resources in time and money in considering the best approach for detection starting with the people aspect is a must for any size. What security awareness training have they had and the success of that program? What are the people touching (meaning what applications are they using - email, socials, desktop apps)? And what are they using, what devices are they engaging with regularly?
Additionally, assess what type of data the company has and where they are dealing with the biggest threats - is it the finance department; physical systems, etc.?
And of course include your basic asset inventory to be sure you know what all you need to protect to start with.
Once you’ve done your initial assessment of who you’re protecting and what you’re protecting, you need to determine how to detect threats. Of course, there needs to be some level of basic tech solutions that can monitor and track whether it’s email or URL filtering along with admin controls. Ensuring there is basic Access Management monitoring as well is essential. Adrianna recommended also monitoring for anomalies of data and what that data is being used for that is out of place.
Some practical implementations that are easy on the budget as well as good guidelines for getting the most out of detection and protection include:
But what about a cloud or SaaS only environment?
Much of the same principles apply including the ability to create Canary files that can be done in OneDrive or AWS buckets as well as other open source products using basic tech. Once you receive an alert, determine what the process from there is to identify what is going on.
Software recommendations for data discovery and inventory unfortunately is mainly geared to enterprise due to the hefty price tag of tech solutions. Verona and Alpide are potential solutions if you’re budget allows for them. Challenges with open source solutions are the many false positives they tend to yield which hinders the goal of optimizing detection with minimal noise so as to maximize human resources and attention.
The main consensus in this area is to focus on understanding where the key data is within your company and concentrate on protecting those vital areas.
Detection can inform response and what to do BUT it should also take a look at and inform what should be done better around specific protections.
A good detection plan must include an incident response plan because simply detecting is not enough - it should be clear what the next steps are once a detection occurs. This will save time and money and lead to quicker resolution.
One of the common failings in detection for many organizations includes companies not patching vulnerabilities in a reasonable timeframe which leads to more vulnerabilities and incidents occurring
One recommended solution is investing in understanding how to patch vulns quicker. This takes not only resources but investing in that policy and procedure changes as well. After an incident happens, evaluate how you can prevent having to detect and resolve the same issue from occurring repeatedly. Consider the process behind the patching - identifying, detecting, and closing high vulnerability gaps as efficiently as possible.
As usual, it depends. For many in leadership what may be foremost in the news is not necessarily relevant for your company’s space and may take the focus off of what is critical for your industry.
Look at the new pieces in the past year and identify those that occur within your organization’s market vertical as a guideline and use that to help educate your leadership for them to better understand themselves. Ecommerce sites, for example, have the specific challenge of fake websites imitating the legitimate business site is more an issue or credential stuffing attacks are more highly relevant than an API attack that targeted the healthcare industry.
Creating a threat profile for your org is an excellent exercise to provide a concrete framework in helping identify which threats to focus on and which to de-prioritize.
Key aspects to consider in creating a threat profile includes:
A resource to aid in determining attacks for your particular industry vertical is the Verizon Data Breach Investigations Report (DBIR) - this report breaks down the various threats according to sector and is a good starting point to understanding your industry vertical and what threats are most prominent. It’s also a great resource to use in educating leadership as well.
Creating a solid plan for detecting threats and the subsequent incident response is not a quick process but rather something that is slowly built over time. As each brick is put in place and added to your wall of defence it will strengthen and improve over time. It’s a long-term endeavour with constant maintenance and revisions as situations arise but establishing the basics and building from those will strengthen your business as it grows.
Brian Haugli - Host, Managing Partner at Side Channel and Founder of RealCISO.io, Host of #CISOlife;
Web: SideChannel;
Adriana Petrillo, J.D., CISSP Panelist, Cyber Security Specialist, CISA
Terry Chapman Panelist, Principal Consultant & vCISO, Side Channel