A key to understanding what a good security framework is, is to first understand what this question actually means.
So, let us breakdown the question a bit. What do I mean by security framework for business?
Why do we even give a 2 cents about security for business? The truth here is that security as a word is meant to make you feel protected from something dangerous or protect you from something/someone who wants to take away what you deem to be important to you.
So with that diluted definition of security in mind, how do we start hacking away at developing this security framework?
Oops, one more definition if i may…what is a framework?
A framework is a real or conceptual structure intended to serve as a support or guide for the building of something that expands the structure into something useful. In the case of this post, I hope to give you a framework that would guide you in your path to setting up a good defence strategy in protecting your information assets.
When someone talks about security, it’s usually in the context of wanting to be safe from someone or something. We can say this in another way in that people feel safe when they are able to identify the person or object they are interacting with. By this understanding you can conclude that identification plays an important role in a good security framework as this aids in our objective to stay safe or rather in the context of business, keep our assets and information safe.
Identification doesn’t need to be limited to the scope of seeking out potential threats thou. In the context of the information age, data classification, or rather…, wait for it…, identifying what data is important to us and what is not, also helps us paint a clearer picture of where we should invest our attention and resources on. Therefore this process, called Data Classification, makes it onto our journey towards creating a good security framework.
Armed with the words Identification and Data Classification, and this is just me guessing here, probably doesn’t do much for you right?
What are the different ways that Identification can help in the protection of your information assets?
Well, if we draw an imaginary box around our business and say to the world this box is made of fiery hot lava and if you pass it to try to get at my information, you will be melted into gooey pulp of hot liquid ooze and no wizard in Hogwarts will be able to mould you back into a human being, would you say that our information is relatively safe?
Most all businesses, before 2013 would have probably said yes that they are safe to the above question. And no, they most certainly did not build pits of lava around their buildings…although that would be a cool (no…hot) thing to see, haha…
The earlier concepts of security spoke widely about protecting your perimeter which meant for many businesses, placing a firewall (It’s a network device, cool your jets now), between the business network and the Internet. This network device sat as gate-keeper and monitored all traffic in and out of the business. The general rule of thumb here was to block all inbound connections from the internet except for the services that you truly wanted to expose to inbound connections and then basically pretty much allow all outbound connections, well because back then “phishing” ({soft under tone voice} will explain later), wasn’t really a thing and outbound monitoring wasn’t really needed.
Ok so we covered firewalls at the perimeter, so what other fancy pants tools did businesses use to protect the perimeter?
As email got introduced to the world, this then became another entry point into a business, so the fancy pants tool in this instance was something appropriately described as an email filtering system. This system acted as the gate-keeper for all email into and out of a business. It used technology like Anti-Virus Scanners to scan the emails for any viruses that may have been present in any of the emails coming into the business or leaving the business for that matter as well.
While many a folk were certainly focused on the perimeter protection, there were others also looking after the inside of the network. Yes, I let you sneak a peek above… Anti-Virus providers grew stronger, as the years sped on, to better protect our user workstations from getting infected, nope not from the flu, but by a virus. The kind of virus that prevented either your applications or even an entire workstation from working. As a new virus was introduced to the world, the Anti-Virus providers tried keeping up by updating their software to be able to detect the new viruses and thereby block the virus from infecting other workstations. This to and fro battle continues even today in this information age we now find ourselves in.
These three tools, firewalls, email filtering systems and Anti-Virus programs all used the ability to identify a safe state or a threat state of the data traffic entering or leaving your business to be able to protect your business from your information being lost to the bad guys.
Later on, we see how Identification evolves into further helping your business in the battles with Dr.Evil.
Data Classification is a much harder topic, but let us take a crack at it. Data Classification is a process of categorising data assets based on its sensitivity. It may be classified as: public, internal, confidential (or highly confidential), restricted, regulatory, or top-secret.
Now in a new Start-Up, Data Classification is super simple as you have the opportunity to classify the data as you give birth to the data. Thou the opposite can be said for an existing business or enterprise where the data points are vastly spread out and often not commonly known to all in the business. Therefore classification in this respect becomes a rather long drawn out process which usually gets a low priority because of the sheer effort of the task.
But without classification of your data how does a business know if they are leaving a valuable piece of their business just out there for the grizzly to pounce on it (#Fancy Bear reference). Are we creating new points of entry into business by not appropriately classifying our data? The IT folk/security folk, all probably answer yes to this question, not because it’s true, but because an unanswered question is open to speculation and speculation always at least once in any scenario offers a negative outcome.
With the introduction of cloud providers and therefore cloud services such as storage on the public internet, I will leave you with this thought, if you are not actively telling your staff what data is important to you and what is not, how do you expect them to know whether storing this data in the publicly available storage platforms by multiple cloud providers is safe or not? The flip side to this is that if your staff is already doing this and the IT and Security folk don’t know where this is happening how can the put security measures in place to protect that data?
Let us recap shall we…
A Good Security Framework: (So far…)
- Classify your data into categories of sensitivity.
- Determine where your data is stored.
- How your data moves from point A to point B?
- How your data is processed?
- What/Who processes your data?
- Do you have the appropriate security measures in place to protect your data in each of the above states?
- Identify where your perimeter to business starts and stops.
- Introduce tools to inspect the paths in your perimeter that remain exposed to the internet.
- Configure the tools to identify safe states and threat states when they inspect these exposed paths.
- Block all inbound threat states.
So we are slowly getting there, I see…
What is an Insider Threat?
In the past all businesses merely focused on perimeter security which, as you can imagine focused the Death-Star beam solely on the exterior of the business. This basically left the inside of the network in the dark and in clear view of Dr.Evil to come in and poke around. With firewalls predominantly blocking most if not all inbound connections, the focus was not nearly enough to inspect and block outbound connections as well. This loophole in the security posture of businesses back then was quickly found out by the bad guys out there. These bad guys then designed innovative ways to bypass the firewalls and tricking the users of businesses in creating outbound connections to their compromised websites on the internet which thereby started to give the bad guys direct access to the internal workstations.
All this accomplished without having to make a single inbound connection to the firewall that was all blocking inbound connections. This simple scenario thereafter introduced the concept of the Insider Threat, well in the context of the scenario below that is, and this concept has never left us since that horrid day.
So this new threat then forced the innovative spirit of the good guys and therefore brought the world what many proudly or frustratingly call the Internet Proxy. The internet proxy then sat on the inside of the network usually in between the users and the internet to filter outbound traffic towards the internet and attempted to identify safe states or threat states of the inspected traffic. It then blocked all threat states of that traffic and thereby started winning back the war from the bad guys.
Before we add this new tool to the recap, let us first explore what threat condition gave the bad guys benefit prior to the introduction of the Internet Proxy. This threat condition is called the “Phishing Attack”. It got this name because of the similarities to the conventional water sport/survival practice known as fishing in which the fisherman baits the fish into biting the hook before reeling it in for the kill. In a similar fashion the attacker usually either sends the fish…oops sorry, user an email with the bait being a link and the hook being a compromised website, so when the user clicks on the link and browses to the website, creating the outbound connection which is allowed by the firewall, either the user’s machine then gets infected with a virus or information gets stolen. On the other hand an attacker could just merely leave a compromised website out there in the wild with a similar name to a high traffic website so if users stumble their way onto the compromised website while simply browsing the internet as part of their daily routine, they will then also be infected or have their information stolen.
In practical sense, once the hook catches its bait, going in for the kill would mean that the bad guy would need to exploit some kind of vulnerability on the users’ workstation to be able to compromise the machine. What this means is that an additional line of defence is required to stop this from happening even if the hook was effective in luring the victim in, an excellent vulnerability management programme needs to be in place to be able to appropriately identify potential vulnerable workstations so that they can be patched to the latest software version that would stop the vulnerability from being exploitable. In turn this also means you would need to have an equally effective patch management programme to be able to remediate vulnerable workstations in a timely manner.
In addition to vulnerabilities found on workstations, vulnerable services on your server equipment that are exposed to the internet could also be a threat. A constant review of public facing services needs to be in place so that you have a remediation plan for these services if they are absolutely meant to remain public facing.
So to recap on our framework, we now also added the capability to inspect outbound traffic to the internet as well as identify safe states and threat states and therefore block outbound threat states towards the internet. A good vulnerability management and patch management programme will be needed. A continuous review of all internet facing services must be held and vulnerabilities remediated where identified. I will re-summarize the entire framework with all additional points towards the end of the post again.
So the question beckons, what happens when the next guy is smarter than you, like way smarter?
When all the security measures your genius team puts together are not enough and the bad guys get into your network un-detected, what then?
Well, the answer is right under your nose isn’t it? They got in un-detected…so the next notch in your armour should be aimed at empowering detection capability within your business isn’t it?
With detection capability we start to introduce concepts like Indicators of Compromise. What tells you that a workstation on your network has been compromised? How do you even know where to look? More importantly how do you know when the workstation was compromised and how far spread the infection was?
Let us unpack this concept of Indicators of Compromise a bit more, shall we?
Yes, we shall, most definitely…
The best way to spot the needle in the haystack is to know that the haystack is not made of metal and that the needle is made of metal. What I mean by this, is if you understand what the norm in your network is then it would be relatively easy to spot the variances from the norm. Let us explore a scenario that might better explain this.
If you suddenly have your sales staff making attempts to access areas of your network that is usually restricted to sales staff. That may be an indicator of compromise because the behaviour is not the norm. You want to investigate further in this regard.
Another example, would be if you suddenly start to witness excessive traffic generated from one workstation on your network to every other device on your network. This is not normal traffic for any business and usually points to what the bad guy’s call a port scan. This port scan allows the bad guy to find other workstations on the network that are easy targets for compromise. You want to investigate further in this regard.
So how do you monitor for indicators of compromise?
- Identify the type of data flowing through each of your current devices of protection.
- Can this data alert you to interesting traffic that may point to indicators of compromise?
- Are you able to send this data to a central point for consolidation and analysis?
- Collect all your logs / data from your various security devices.
- Analyse these logs for immediate unusual traffic from each specific security device.
- Correlate the findings above, from all your security devices.
- Inspect the correlated data for identifying information of threat actors.
- Update your security devices to block the identified threat actors.
So that ends the blog post correct? We are safe…there is nothing else we need to do because we won…
Ok so you didn’t believe that for a second did you…and you shouldn’t believe that we are done…not even for a second…
Our adversaries are determined and in some instances maybe even more so than the good guys. This therefore always inspires innovation in the threat space which keeps us good guys always switched on and on our toes looking eagerly towards the future to see what is next…
So there in, I bring to you the bonus round….
Authentication, Authorization and Accounting, as well as network segmentation and application whitelisting, not forgetting be-gone the admin level access to the user.
So to add to our arsenal of weaponry against the unforeseen ungodly nightmare of the dark in this fight to the never-ending finish line, we have to create the ability to only allow in our environment, what and who we can verify to be required on our network. This scenario is introduced by the concepts of authenticating only valid users on the network, authorizing only valid services on the network for authenticated users and accounting for all their network traffic so it can be monitored and added to future correlated data for threat analysis. This scenario is further secured by keeping your different business areas segmented from each other which will make it easier for unusual traffic to be identified. Removing admin level access from your users will make it easier to avoid unwanted applications being installed on your workstations which will help the drive to only run known applications / whitelisted applications on your network. This then prevents the attacker to introduce their infected applications into the environment and gain a foothold on your network.
Ok so, as promised here is the summary below…
A Good Security Framework: (…in my humble opinion…)
- Classify your data into categories of sensitivity.
- Determine where your data is stored.
- How your data moves from point A to point B?
- How your data is processed?
- What/Who processes your data?
- Do you have the appropriate security measures in place to protect your data in each of the above states?
- Identify where your perimeter to business starts and stops.
- Introduce tools to inspect the paths in your perimeter that remain exposed to the internet.
- Configure the tools to identify safe states and threat states when they inspect these exposed paths.
- Block all inbound threat states.
- Implement Internet Proxies to inspect outbound traffic to the internet as well as identify safe states and threat states and therefore block outbound threat states towards the internet.
- Implement good Anti-Virus scanners on your all your workstations to catch the low hanging fruit such as junior bad guys using older threat tools to try their luck on your network.
- Implement a Vulnerability Management Programme to be able to identify workstations in your business that make it easy for a bad guy to exploit.
- Implement a Patch Management Programme to be able to remediate vulnerabilities found in your network.
- Establish a continuous review of your Internet facing services for any vulnerabilities and remediate accordingly.
- Look for Indicators of Compromise.
- Identify the type of data flowing through each of your current devices of protection.
- Can this data alert you to interesting traffic that may point to indicators of compromise?
- Are you able to send this data to a central point for consolidation and analysis?
- Collect all your logs / data from your various security devices.
- Analyse these logs for immediate unusual traffic from each specific security device.
- Correlate the findings above across all your security devices.
- Inspect the correlated data for identifying information of threat actors.
- Update your security devices to block the identified threat actors.
- Always Authenticate users trying to access your network.
- Authorise access to specific services for only authenticated users on your network.
- Account for all traffic generated by authenticated and authorized users on your network.
- Limit admin level access to users that are not required to have admin level access.
- And lastly, Whitelist applications on your workstations so that the bad guys are denied from having their malicious applications run on your workstations.
I certainly hope this post invokes and inspires great discussion in your businesses to better help you protect what is gold to you and yours. Stay Aware…