← All use cases

Threat Modeling · AI Threat Modeling & Unified Workbench

Threat model as a team, with disagreements on record

Several people edit one architecture at once, Aribot derives threats on each change, and disputed threats stay on the model with the reason attached.

1. Open the diagram · 2. Invite reviewers · 3. Edit together · 4. Derive threats · 5. Accept or dispute1Open the diagram2Invite reviewers3Edit together4Derive threats5Accept ordispute

The problem

Our threat models are written by one person and reviewed by nobody who disagrees with them. When someone objects, the finding gets deleted and there is no trace of the argument. The team is spread across time zones, so the review meeting never has everyone in it.

How Aribot handles it

  1. 1

    Open the diagram

    Share an architecture, and it opens as an editable canvas.

  2. 2

    Invite reviewers

    Others join from an invite link, and their presence shows live.

  3. 3

    Edit together

    A new data flow added by one person appears for everyone.

  4. 4

    Derive threats

    Aribot raises threats on the changed model.

  5. 5

    Accept or dispute

    Each threat is accepted or disputed, and both outcomes are kept with the reviewer's reason.

What you get

  • Live co-editing of one architecture
  • A change feed showing who did what
  • Disputed threats kept on the model with their reason
  • A history of what changed between sessions

Related use cases