Without secure hosts, you cannot run secure containers. In Twistlock 2.4, Twistlock extends our host protection to protect hosts from unexpected behavior in both known and new services.
Container Host Protection Capabilities
Twistlock will define each service by the capabilities that the service requires. For new services, these container host protection capabilities are determined by machine learning the first time the service is run on a host protected by Twistlock. For example, here are the capabilities for dockerd, the underlying daemon for Docker:
Capabilities define the expected system and administrative actions that the service will take.
When a service requests a capability that isn’t in its model, Twistlock will generate an audit:
In this case, an HTTP server executed the useradd command, which is included in the USERS_ADMIN capability. This is out of the model for the http-server service (obviously, I hope).
We can also create rules that prevent this behavior:
With this rule in place, further attempts to exploit http-server are blocked:
Improvements to host protection allow Twistlock to more precisely model the actual activity of background services, resulting in more comprehensive preventive runtime defense while also demonstrating lower false positive rates.
Related Twistlock 2.4 Posts:
- Twistlock Platform
Follow us on Twitter
Follow us on Twitter for real time updates on the cloud native ecosystem, Twistlock product, and cloud native security threats.
How to Securely Configure a Linux Host for ContainersRead the Blog
Don’t Forget the Audit Trail! The Role of Reporting in SecurityRead the Blog
Securing Cloud Native Applications on Pivotal Container Service (PKS)Read the Blog
What to Know: Gartner’s Security Considerations and Best Practices for Securing Serverless PaaSRead the Blog
Crypto Mining and the Cloud: The Perfect IT Security StormRead the Blog