Abstracting Cloud Complexity With Cado's New Import UI

One of the biggest inhibitors to incident response in the cloud is understanding the many and varied tool sets required to truly understand root cause, scope and impact.

Each provider has its own console, none of which was created for the faint hearted. Each provider has multiple offerings for compute, storage, Kubernetes and container orchestration, and serverless functions. Each has its own way of managing accesses, and logging and monitoring what's going on.

In a multi-cloud environment, this makes investigation and response extremely difficult for a security team, demanding that they be experts in each of the cloud platforms, as well as incident response.

At Cado, our mission is to abstract as many of the complexities of the cloud as possible, and recently we've revamped our import UI to make data import as consistent as possible no matter what service, no matter which cloud.

Cado's Newly Refreshed Import UI

To get started, first select your credentials, whether that be for an Azure Tenancy, a GCP project, or AWS account, Cado supports all three major cloud providers.

Next, select your service, locate your resource, and off you go!

While you'll need some knowledge of cloud terminology, and a basic understanding of how the Kubernetes control plane works, with Cado, it's a much more simple process to navigate investigation and response across more than one cloud console.

After the data is imported into the Cado platform, it's automatically processed and analyzed, so that you can do what you do best - interperet what you see and truly understand a potential attackers' footprint.

Seamlessly dive into important incident data with Cado's timeline and advanced search and filter capabilities.

If you're interested to see how Cado can help you simplify cloud investigations? Contact us to schedule a demo or check out our 14-day free trial.