Micro-segmentation provides the ability to isolate communication flows within applications and workloads and allows for more granular workload security than traditional tools. Beyond using micro-segmentation to allow or block connections and alert on those activities, the ability to compare, within a single platform, policy violations to historical observations can dramatically accelerate breach detection, investigation, and response.
The movement of data and workloads to the cloud has been more like a headlong rush. In the quest for a competitive edge, businesses are clearly eager to take advantage of the agility and elasticity the cloud affords them – so much so that security is often an afterthought. But hey, isn’t the cloud provider taking care of that?
Some companies are surprised to hear the answer is no, at least not entirely.
In traditional data center environments, security teams usually leverage their standard security tools and agents to capture network-level logs. Capturing these logs gives teams visibility into network architecture and traffic flow. However, when we migrate applications to AWS, these standard practices change. The same toolsets might not be as efficient as they were in the traditional environment. While security fundamentals are the same, the approach changes. Security teams need to explore new options and adopt new tools to ensure adequate security coverage.
Containers and orchestration systems use numerous technical abstractions to support auto-scaling and distributed applications that obfuscate visibility into application communication flows. Security teams lose visibility into application communication flows, rendering traditional tools useless and exposing the application to risk.
Micro-segmentation is very achievable. While it can feel daunting, you can succeed by proactively being aware of and avoiding these roadblocks. Read more
The Virtual Desktop Infrastructure (VDI) continues to gain popularity among our customers due to its many advantages and benefits when deployed within the modern data center infrastructure. However, those deployments lack some of the capabilities that are needed to address the threats that are introduced when moving away from hardware desktops to a virtual environment. Thus, many organizations are still hesitating about VDI in view of security concerns, especially due to the increased attack surface and the fact that endpoint devices, which are vulnerable by nature, share compute resources with the organization’s most critical and important servers inside the data center.
This is part 2 of a 2-part series examining how security requirements have changed for an evolving IT infrastructure.
In part I of this blog series, we discussed the changes in the way businesses and IT teams are executing and how security practitioners are being presented with a unique opportunity to align their tools and strategies with the direction the business is going. In this post, we’ll review some of the strategies and tools that can be used to help secure your hybrid cloud environment and keep pace with the DevOps model.
Guest blog by Edward Amoroso, Founder and CEO of TAG Cyber – he summarizes a recent discussion with GuardiCore on their approach to securing the modern data center.
I recently discovered Matt Butcher’s awesome Illustrated Children’s Guide to Kubernetes. Available in book, video, and blog form (https://deis.com/blog/2016/kubernetes-illustrated-guide/), the cartoon narrative starring a PHP app named Phippy is exactly what good cyber technology writing should be: Fun, simple, and informative. Even if you have no interest in Docker container orchestration, check out Matt’s work. You’ll like it.
When the Equifax breach was announced on September 7th, I was not surprised. When I heard the magnitude of the damage: 143 million US consumers and 44 million British consumers – which equate to roughly 57% and 97% respectively of both country’s populations, age 18 years of age and older – I, again, was not surprised. Why?