← All use cases

Cloud Security Platform · Cloud Security & Digital Twin

AI-drafted fixes that wait for your approval

Aribot drafts a fix for each finding with the model that wrote it on record, and nothing changes until a person approves the dry run.

1. A finding arrives · 2. Draft a plan · 3. Dry run it · 4. Approve, apply, re-check1A findingarrives2Draft a plan3Dry run it4Approve, apply,re-check

The problem

A model-written fix looks plausible, so it is easy to approve and hard to audit later. I'm asked to sign off a change whose effect I can't see until it runs. Our reports mark findings resolved when the instruction was sent.

How Aribot handles it

  1. 1

    A finding arrives

    A scan result comes in with no plan attached.

  2. 2

    Draft a plan

    A plan is generated at Draft status, carrying the provider and model that wrote it.

  3. 3

    Dry run it

    The reviewer sees exactly what would change, and nothing changes yet.

  4. 4

    Approve, apply, re-check

    After explicit approval the change is made, then the resource is re-read to confirm it.

What you get

  • Generated fix plans with their authorship recorded
  • A dry run before any change
  • Explicit approval on every applied fix
  • Findings closed on a re-read, with the re-check stored apart from the execution

Related use cases