1Commando  /  Product  /  Blast radius
Blast radius

Pick any account and see what a compromised version reaches.

Each ring is one more hop from the identity. Its groups, roles, and direct grants sit on the first ring, and whatever those lead to sits on the rings beyond. Restricted resources and flagged edges are drawn in red so the eye finds them first. It works the same for a person, a service account, or an agent.

1 HOP 2 HOPS 3 HOPS ap-approvers team-revenue-operations Salesforce · Data export NetSuite · Payment approval RESTRICTED Bill.com · Approver RESTRICTED Brex · Approver RESTRICTED zapier-svc SERVICE ACCOUNT
IDENTITYzapier-svc
REACHES11 resources
BY HOP1 at 1 hop · 10 at 3 hops
RESTRICTED3
FLAGGED8, all high
OWNERnone on record
KEY ROTATED2024-11-14
Blast radius of zapier-svc, a service account in the demo org with no owner on record. Each ring is one more hop from the account.
How it works
01

Rings

The chosen identity sits in the center. Each ring is one more hop away, so the shape of the risk is visible before you read a label.

02

Restricted first

Restricted resources are outlined in red, and every edge into a flagged resource is red, so the worst case is the first thing you see.

03

Any identity

Open it from any identity profile or from the machines list, for a person, a service account, or an AI agent. In the demo org, 24 of the 169 machine identities have no owner on record.

What you get

Blast radius, in practice.

  • Reach count and restricted count for every identity
  • Owner and time since the last key rotation on the same profile
  • A Trail link for every resource in reach, with the evidence for each hop
  • Comparison with peers and with the identities whose access is most similar
Get started

See your own access graph.

Start with Okta or Google Workspace, plus a Workday export. 1Commando only reads from them.