Enhanced Visibility and Compliance to Containerized Environments

DZone 's Guide to

Enhanced Visibility and Compliance to Containerized Environments

The latest Twistlock release includes improved Runtime Radar and new Compliance Explorer for large enterprises and government agencies.

· DevOps Zone ·
Free Resource

Twistlock has announced the availability of Twistlock 2.0 during DockerCon in Austin, Texas. This latest release of Twistlock’s includes an updated user interface, performance improvements and new features that enable organizations to stop an attack before it starts.

While Twistlock 2.0 was built to handle the most stringent of security requirements found in many enterprises, it also benefits smaller development teams that need more simplicity and agility to take their innovations to market more quickly and safely. To help companies stay in front of a potential compromise, Twistlock 2.0 builds on the capability to identify vulnerabilities as part of the continuous integration (CI) process and relies on frequent monitoring to prevent the deployment of unsafe and non-compliant images in the first place.

“Container security needs to be truly application aware and based upon developer intent,” said John Morello, chief technology officer at Twistlock. “Twistlock 2.0 relies on application intent analysis to produce a more predictable and secure container environment. Twistlock 2.0’s breadth and depth of compliance features and applicability to various industries make it an obvious choice for organizations looking to improve their container security.”

Runtime Radar 2.0

Initially introduced in Twistlock 1.6 as a way to visualize how containers interact with each other, Runtime Radar 2.0 provides a single view into the status, connectivity, and risk state of an organization’s environment. Runtime Radar allows organizations to see their entire environment from relationships between pods to processes to network calls, file access, and system calls for individual containers. New features include color-coded overlays of vulnerabilities and compliance state and the ability to export an organization’s connectivity topology into a Kubernetes networking policy. Each of these new features increases the understanding of a company’s inherent security risk in addition to providing an additional layer of defense.

Compliance Explorer

Large enterprises and government agencies have demanding compliance needs. In addition to needing the ability to check their state of compliance at any point in time, these organizations must also have the ability to actively enforce compliance across their entire environment. Twistlock’s new Compliance Explorer relies on predictive analytics to monitor an organization’s current compliance state and creates a dashboard displaying how compliant a company is at any given point in time, listing out those entities that are non-compliant. This data can also be exported for integration with other tools.

Additional new capabilities and features available in Twistlock 2.0 include:

Embedded secret detection and blocking: Checks for compliance of .509 keys, SSH keys, AWS tokens, and other credentials stored in the clear within image file systems or provided to containers via unencrypted environment variables.

Certificate authentication: For organizations using public key infrastructure, Twistlock has added support for authentication, ensuring users stay secure everywhere they log on.

Jenkins Pipeline Support: Twistlock 2.0 expands on Twistlock’s native integrations with Jenkins, adding support for Jenkins Pipeline, a powerful way to create build automation as code, and increases efficiency and reusability.

Improved file integrity assurance: A set of additions to Twistlock’s file integrity capabilities, including certificate monitoring within images, user-defined file monitoring, and advanced heuristics combined with process behavior to detect anomalous behavior.

cloud ,container security ,continuous integration ,devops

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}