Cloud Security Platform · Cloud Security & Digital Twin
Kubernetes findings in the same view as your cloud
Cluster findings such as privileged containers or automounted credentials land in the same violations view as the rest of your estate, scoped to cluster resources.
The problem
Our workloads change on every deploy, and the cluster security view is a separate tool nobody opens. A developer gets a 'privileged container' alert with no workload named and no sign of how it was rated. At audit, container posture gets answered from memory.
How Aribot handles it
- 1
Connect the clusters
Read-only cluster access brings workloads into scope.
- 2
Read the workloads
Live pod and policy state is checked, and findings are raised.
- 3
Keep source severities
Rated findings keep their severity, and unrated ones get their own band.
- 4
Triage with a record
Each finding names its namespace and workload, and the assignment records who rated it and why.
What you get
- One place to look for cluster and cloud findings
- Findings named by namespace and workload
- Unrated findings kept in view
- The same evidence trail as cloud findings
Related use cases
Triage multi-cloud findings without losing the unrated ones
Findings from every connected cloud in one list, with severities from the source and a separate band for findings that arrived with none.
Connect cloud accounts read-only and see which failed
Connect AWS, Azure and GCP accounts with read-only access and see which ones Aribot could actually read, so an unread account never passes as clean.