AVOID CONTAMINATION IN
YOUR LINUX ENVIRONMENT.
IN YOUR LINUX
Containers. Whether they be Kubernetes, Docker, or something else, there’s no question as to the level of flexibility they’ve provided for the Linux DevOps space, in part because they are thought to be a safer form of deployment since they are a way to contain and monitor the operations happening within.
But from a security perspective, the best way to picture containers is as your home. Let’s say you invite a few friends (or your third-party vendors) over to have a great game night. (Yeah, we’re nerds.) Except, your third-party vendor friend Joe has a big mouth (or log4j vulnerability) and winds up telling a bunch of strangers about the party you’re throwing. Next thing you know, there are a ton of people you don’t know in your house, there’s a keg in the living room, someone broke Great Aunt Mabel’s teapot, and two guys just crashed through the bay window having a fight. And your game night has been ruined by container contamination.
WHAT IS CONTAINER CONTAMINATION?
For containerized environments running on cloud servers like AWS, Azure, or Google, a container does a decent job keeping the application within it from accessing the host. But if a malicious actor can get inside the container, the application will be disrupted. And, on a public-facing server, the potential for this type of intrusion is extremely high. While you may be doing everything correctly in terms of vulnerability patching, and coding best practices (or in our analogy’s terms, not opening the door to strangers), can you feel confident that every other developer for third party applications you leverage are behaving the same way? It’s highly doubtful and can easily result in a bunch of strangers in your house. On top of that, we’ve also seen attackers able to pivot from container to container and attacking the host for maximal damage.
HOW DOES ZEROLOCK SPC HELP PROTECT?
WHERE CAN I FIND ZEROLOCK SPC?
Extend your use to a full year via the Red Hat Marketplace: ZeroLock Self-Protecting Container on Red Hat Marketplace – United States.
Linux, kernel v3.5 or higher. Distribution agnostic.
x86-64, ARM-64 (coming soon)
No kernel modification or modules required.