1Commando  /  Product  /  Trail
Trail

Pick an identity and a resource, and Commando draws the path.

A trail starts from one person, service account, or AI agent and draws only the hops that lead to one resource: identity to group to role to resource, with the evidence on every hop.

Trail: Sarah Mitchell to GitHub · prod-deploy environment
EMPLOYEE
Sarah Mitchell
Senior Accountant
Accounting
ACCT 100FIN 94ENG 5
member of
added 2021-06-14
by T. Brooks
GROUP
eng-oncall
99 members · Okta
Sarah was in Engineering when added
member of
GitHub team sync
from Okta
GROUP
github/eng-oncall
99 members · GitHub
all through the Okta eng-oncall group
grants
deploy
source: GitHub
RESOURCE
GitHub · prod-deploy environment
last used: 2022-11-02
RESTRICTED
Flagged for review
Commando

Sarah Mitchell reaches GitHub · prod-deploy environment through eng-oncall and github/eng-oncall. Engineering score 5 for a restricted resource. 0 of 4 peers hold it. Last used 2022-11-02. Granted while in Engineering. Recommend review.

Sarah Mitchell's trail in the demo org: three hops to a restricted resource, flagged for review. In the app, an evidence table under the trail lists each hop's permission, date added, granter, source, and last use.
How it works
01

Start from an identity

Pick a person, service account, or AI agent. The page lists only what it can reach, flagged and restricted first. Pick a resource and the trail is laid out left to right, so it reads like a sentence.

02

Evidence on every hop

A table under each trail lists every hop's relationship, permission, date added, who granted it, source system, the job the person had at the time, and last use. Hover a hop to see the same evidence, or use Copy evidence to paste it into a ticket.

03

More than one route

When an identity reaches a resource in more than one way, up to four paths stack as rows, shortest first. Group member counts include members who come through nested and synced groups.

What you get

Trail, in practice.

  • A trail from any person, service account, or AI agent to any resource it can reach
  • Routes through nested Okta groups, GitHub teams synced from Okta, and app roles
  • An evidence table with a Copy evidence button for tickets and audit notes
  • A Path between view in the knowledge graph that connects any two entities
Get started

See your own access graph.

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