Before making any policy changes, one usually would want to be able to analyze how it would impact traffic. Tetration has the ability to simulate and validate policy before applying changes using its Policy Analysis feature.
One of the awesome things that Tetration can do is create dynamic policies based on changing conditions and detect vulnerable software in workloads. In this blog post, I will briefly go over both of these features.
We previously went into application mapping in this blog post and we will delve into it further in this post to explain how that application mapping is used to create whitelists that can be used for micro-segmentation.
In this post, I’ll be going over the Host Profile dashboard inside of Tetration. It won’t be a long post but it’ll show you some of the details one can gleam from this dashboard.
In this post, we’re going to dig into how applications are mapped in Tetration, what it looks like in the UI and how this information can be used.
Before I begin, I’d just like to thank my friend JP Cedeno for giving me a crash course into Tetration and allowing me to use what he taught me to make the next few blog posts. I’d also like to dedicate this blog post to Matt White who asked for it some months ago. In this blog post, we’re going to go over the fundamentals of Tetration.
Since Tetration has visibility both inside the endpoint and the traffic flowing through the network, it gives us some amazing forensic analysis capabilities. In this post, we will review some of these powerful capabilities but this is far from all of the forensic features in Tetration.