A lot of the time we like to think that adding a new tool or creating a new policy will start to cover our bases and make us less vulnerable. While that can be true in a lot of cases, we often tend to overlook system interaction changes and a plethora of other holistic variables. A key thing to keep in mind is our security posture. Security posture is the way we structure and protect our self from a cyber perspective and usually has a more holistic/complete view of our systems.
A good amount of the security vulnerabilities we have don’t come from “New” threats or a breakthrough in some technology, but from the simple misunderstanding and configuration of the security tools we already employ. It’s something we don’t always think about when we think of Cybersecurity but it’s crucial to recognize. Sometimes the fault lies within our self, not a failure of some tool we employ, but our misuse/misunderstanding of that tool.
While this is by no means an exhaustive list, here are some things to think about when you look at your overall Security Posture, I call them the 5 C’s:
5 C’s of Security Posture
A lot can go wrong that can lead to security lapses and breaches. Having a plan to respond to that ups your security posture. An ounce of prevention is worth a pound of cure. Having contingency plans for when murphy’s law strikes could prove to not only be the safest way to go, but also the most cost effective.
Continued Additions to posture:
When adding new tools to an already implemented system it’s crucial to keep in mind exactly what resources that system needs to function properly, and how it will interact with your already in place policies. Additional tools are meant to improve your security posture, not bend it. If they conflict in any way, it could leave open bigger vectors for cyber-attacks.
Review your current policies and tool configurations to make sure that you’re blocking what you need to. Is your spam setting too lenient or maybe too restrictive? Have you been having issues getting emails from partners? Understanding an issue to why something is being blocked could help you spot holes in your security. It could also allow for you to onfigure your tools to operate to their full potential.
Make sure that whenever you make a change, you follow through with it. If you migrate your password bank, for example, keeping a log of the old one makes it so that you’re still vulnerable to exploits for that tool. It also means you won’t be receiving any of the updates for that tool due to your migration to a new tool. Once complete migration occurs, make sure to clean your slate, so that you don’t unintentionally leave behind security vulnerabilities.
Compatibility to current posture:
Another thing we tend to overlook is the compatibility of the systems we use to the tools we purchase. One thing to always look out for is to check that the features you pay for work with your systems. Sometimes an asset of a tool is only 90% functional in certain environments, and that’s ok. However, if we don’t understand that caveat, we’ll be complacent in not protecting our self from that 10% loss due to our system incompatibilities