← All use cases

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.

1. Connect the clusters · 2. Read the workloads · 3. Keep source severities · 4. Triage with a record1Connect theclusters2Read theworkloads3Keep sourceseverities4Triage with arecord

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. 1

    Connect the clusters

    Read-only cluster access brings workloads into scope.

  2. 2

    Read the workloads

    Live pod and policy state is checked, and findings are raised.

  3. 3

    Keep source severities

    Rated findings keep their severity, and unrated ones get their own band.

  4. 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