← All use cases

Platform & Strategy · Cloud Security & Digital Twin

Close a finding only when the system confirms it

A finding stays open until the affected system has been re-checked and agrees, so your remediation record lists confirmed changes.

1. Pick a finding · 2. Approve it · 3. Re-check the system · 4. Close or keep open1Pick a finding2Approve it3Re-check thesystem4Close or keepopen

The problem

Our remediation tool reports success when it sends the change. If the change then fails, the ticket still closes and the risk is still there. When the auditor asks what changed and when, all we can produce is a list of attempts.

How Aribot handles it

  1. 1

    Pick a finding

    An open finding produces a proposed change.

  2. 2

    Approve it

    The reviewer's decision is recorded with the proposal.

  3. 3

    Re-check the system

    After the change is made, Aribot re-checks the affected system and records whether it agrees.

  4. 4

    Close or keep open

    Only a confirmed result closes the finding, and an unverified one stays open and says so.

What you get

  • A remediation record made of confirmed changes
  • Unverified outcomes kept open and labelled
  • Evidence an auditor can take as it stands
  • A backlog figure that moves only when the estate changes

Related use cases