Identity security built on a knowledge graph

Find access that doesn't make sense.

1Commando maps every employee, service account, and AI agent to what it can reach, scores that access against similar roles, and flags anything irregular for review.

Read-only connectors · Okta · Workday · Google Workspace · GitHub · AWS · Snowflake · Salesforce · Slack
1CommandoTrail
Demo data · Marlow Industrial · 1,960 employees · 104 service accounts · 65 AI agents
Ask Commando In development
Why does Sarah Mitchell have GitHub prod-deploy?
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
GitHub team · synced from Okta
0 of 4 accounting peers hold it
grants
deploy
env: prod
RESOURCE
GitHub · prod-deploy environment
last used: 2022-11-02
RESTRICTED
Flagged for review
Commando

Sarah reaches GitHub prod-deploy through eng-oncall, a group she joined while she was in Engineering. None of her 4 accounting peers hold it and it has not been used since November 2022. Recommend removal.

Try
Figure 0. One trail through the knowledge graph for each question, with who granted each hop and when, where the source records it. In the app today you pick the identity and the resource on the trail page. Typed questions will come with Ask Commando, which is in development.
The product

What a review looks like in 1Commando.

A working recreation of app.1commando.ai running on Marlow Industrial, a demo company with 2,324 identities on its graph: 2,253 current employees, contractors, service accounts, and AI agents, plus 71 offboarded accounts. Create an account and you land in the same demo.

The overview: posture, flagged grants, how open flags built up by grant month, and review progress by department. Numbers are a snapshot of the demo org on September 26, 2026.
The problem

Access piles up.

People change jobs and keep what they had. Nobody goes back to take it away.

Reviews are rubber stamps.

A quarterly spreadsheet with a row for every grant gets approved in an afternoon.

Many machines have no owner.

Service accounts, API keys, and AI agents carry standing access. When no owner is on record, nobody is asked to review it.

The graph

Everything sits on one knowledge graph.

We read your Okta directory over its API and import admin exports from your HR system, cloud, code, and data platforms. Every identity, group, role, permission, and resource becomes a node. Every grant becomes an edge that records who granted it and when, wherever the source system keeps that.

Because every identity sits on the same graph, access that looks unlike its neighbors stands out.

OktaIDP
WorkdayHRIS
GitHubCODE
AWSCLOUD
SnowflakeDATA
SlackSAAS
FLAG
Entities
Employees1,960
Contractors124
Service accounts104
AI agents65
Groups and roles389
Resources223
Relationships
member of · assigned · grants10,826
granted by · last usedwhere recorded
flagged957
Figure 1. Okta, Workday, GitHub, AWS, Snowflake, and Slack are six of the nine source systems whose exports build the demo graph. The other three are Salesforce, Google Workspace, and a CSV admin export that covers about 40 more apps. Counts from the demo org.
Read about the Access Map
The score
Identity profile · Employee
Source: Workday · Okta
SM
Sarah Mitchell
Senior Accountant · Accounting
Manager Travis Park · Since 2019-04 · Employee
Clearance score
ACCOUNTING
100
FINANCE
94
ENGINEERING
5
IT
5
HR
18
Grants · 6 of 51
Domain
NetSuite · Controller
ACCOUNTING
Cleared
Brex · Bookkeeper
ACCOUNTING
Cleared
Snowflake · FINANCE schema
FINANCE
Cleared
GitHub · prod-deploy environment
ENGINEERING
Flagged
Expensify · Policy admin
FINANCE
Cleared
Slack · Workspace Admin
IT
Flagged

Every identity gets a score per domain.

A high score means access in that domain is expected for this identity. A grant is flagged when its score is low for how sensitive the resource is, or when few peers hold that same resource. The score rates the fit between a permission and a role, and says nothing about how the person performs.

ROLE
Department from the HR system sets the starting expectation for each domain.
PEERS
The share of peers, meaning people with the same manager, title, or department, who hold access in that domain.
SENSITIVITY
Restricted grants weigh the most, then confidential and internal. Public resources are never flagged.
USE
Last use of each grant. Access unused for 90 days or more counts more heavily toward a flag.
HISTORY
The job the person held when each grant was made. Access granted in a previous department counts more heavily, and many flags are leftovers from an old job.

When a reviewer approves a flagged grant, the decision and any reason given are recorded, and the flag stays closed for one year. After that it comes back for review.

Read about the Clearance Score
The trail

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

The trail page starts from one identity, lists only what it can reach, and draws the path to the resource you pick.

Everything, drawn at once
eng-oncall Deployer ap-approvers zapier-svc Finance approver dept-engineering Sarah Mitchell AP approver platform-admins ramp-sync Engineer finance-approvers DATA_LOADER CUSTOMER_DATA_READER
The same data, as a trail
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
GitHub team · synced from Okta
0 of 4 accounting peers hold it
grants
deploy · environment: prod
RESOURCE
GitHub · prod-deploy environment
last used: 2022-11-02
RESTRICTEDFlagged for review
Every hop carries its evidence. Source system, grant date, who granted it, the job the person had at the time, and last use, with a button that copies it as text.
Paths stack. Up to four routes to the same resource show one under another, shortest first.
Path between. The knowledge graph finds the shortest routes between any two entities, through groups, roles, reporting lines, and the owners of service accounts and agents.
Figure 2. Left, a few hundred entities drawn at once. Right, the three hops that explain why Sarah Mitchell can deploy to production.
Read about the trail
Blast radius
1 HOP 2 HOPS 3 HOPS ap-approvers team-revenue-operations Bill.com · Approver RESTRICTED Brex · Approver RESTRICTED NetSuite · Payment approval RESTRICTED zapier-svc SERVICE ACCOUNT

Pick any account and see what a compromised version reaches.

Each ring is a hop count from the account: one hop for its direct grants and groups, two for what those groups carry, and so on. Restricted resources are outlined in red. It works the same for a person, a service account, or an agent.

IDENTITYzapier-svc · service account
REACHES11 resources · 3 restricted
OWNERnone on record
KEY ROTATED2024-11 · 22 months ago
Figure 3. Blast radius of zapier-svc in the demo org. It reaches 11 resources, 3 of them restricted, and has no owner on record.
Read about blast radius
Access creep · In development

Every grant on one timeline.

Each grant will appear on the date it was made, with job changes marked. Access that stayed after a job change will be drawn in red. The grant dates and job history it needs are already on the graph.

Scroll sideways to see the whole timeline.
2019 2020 2021 2022 2023 2024 2025 2026 ENG ACCT FIN JOINED · ENGINEERING · 2019-04 MOVED · ACCOUNTING · 2022-09 TODAY 2 ENGINEERING GROUPS STILL HELD · ENG-ONCALL UNUSED SINCE 2022-11 HELD IN THE JOB IT WAS GRANTED IN HELD AFTER ROLE CHANGE
Figure 4. A preview drawn from Sarah Mitchell's grant dates in the demo org. She joined Engineering in 2019 and moved to Accounting in 2022. Two engineering groups stayed with her, and eng-oncall has not been used since November 2022.
Read about access creep
Machines and agents

Agents and service accounts are scored and flagged like people.

Service accounts, AWS IAM users, Slack bots and apps, GitHub App installations, Google OAuth apps, and AI agents live on the graph with their owner, their reach, and their last use. A machine with no owner on record and a restricted resource in reach is flagged the same way a person would be.

Flagged
zapier-svc
Service account
Reaches 11 · 3 restricted
Owner: none on record
Last used: 2026-09-21
Cleared
build-runner-01
Service account
Reaches 3 · 1 restricted
Owner: Nicholas Bradley
Last used: 2026-09-21
Cleared
salesbot
AI agent
Reaches 2 · 0 restricted
Owner: Maya McCarthy
Last used: 2026-09-22
Flagged
DATA_LOADER
AI agent
Reaches 3 · 3 restricted
Owner: Travis Matthews
Last used: 2026-09-22
Flagged
ramp-sync
Service account
Reaches 3 · 2 restricted
Owner: none on record
Last used: 2026-03-02
Figure 5. Five machine identities from the demo org. Two have no owner on record.
Read about machines and agents
Ask Commando · In development

Commando will answer questions about the graph in plain English.

Each answer will name the identities and groups involved, with a link to each one's trail in the graph.

Time
From
Message
14:02
You
Who outside Finance can approve payments in Brex?
14:02
Commando
Besides Finance, Accounting, Finance Operations, and the CFO, three identities. Dan Porter, Sales Operations, through the ap-approvers group, added 2025-11-02 by M. Reynolds. zapier-svc through the same group, and ramp-sync through finance-approvers, unused since March 2026. Neither service account has an owner on record. All three are flagged. Show trails
14:05
You
Which AI agents can read customer records?
14:05
Commando
Three. DATA_LOADER, owned by Travis Matthews, reaches the Snowflake CUSTOMERS schema, the Databricks Unity Catalog customers table, and the S3 bucket cust-pii-exports through reader roles J. Harper assigned on 2026-06-12. It has never used the S3 bucket, and that grant is flagged. churn-predictor, owned by Eugene Gray, reads the CUSTOMERS schema through a direct grant. sdr-outreach-agent can view all Salesforce contacts and has no owner on record. Both are flagged high. Show trails
Log. Demo data. In the finished assistant, every name links into the graph.
Read about Ask Commando
Reviews

Quarterly access reviews built from the graph.

Each review lists flagged grants first. Reviewers see each outlier with its trail and peer comparison, then approve it for one year or request its removal, with an optional reason. A removal request stays open until the access is gone from the source system. The review and the decision log export as CSV for auditors.

Q3 2026 access review · Marlow Industrial
957 flagged · 3 shown
Sarah Mitchell
GitHub · prod-deploy environment
0 of 4 peers hold it · unused 3.9 years
Dan Porter
Brex · Approver
Sales Operations · via ap-approvers
Removal requested · 14:09
Travis Park
NetSuite · Payment approval
Assistant Controller · 6 of 41 peers hold it
Approved for one year
Review. Three of the 957 flagged grants in the demo org's Q3 2026 review. Try Approve or Request removal on the first row. The decisions on the other two rows are examples.
Read about access reviews
Connectors
Available now
OktaLive API sync
WorkdayHRIS export
Google WorkspaceAdmin export
GitHubOrg export
AWSIAM and Identity Center
SnowflakeGrants export
SalesforcePermission export
SlackAdmin export
Any other appSimple CSV layout
Coming next
Microsoft Entra ID
BambooHR
Rippling
GitLab
Azure
Live GitHub, AWS, and Google Workspace sync
Figure 6. Connectors today. Okta syncs over its API with a read-only token. The others import from admin exports uploaded in the app, and apps without their own connector use a simple CSV layout of resources, roles, and assignments. Nothing is written back to any system.
Read about connectors
Security

1Commando only reads from your systems.

1Commando needs to read a lot of your company to build the graph. This is how that access works.

Read scopes only

Every connector only reads. When a reviewer requests a removal, your team makes the change in the source system, and the next import shows it.

Okta token stored encrypted

The Okta connector uses a read-only API token, encrypted at rest, that you can revoke in Okta at any time. Other sources come from admin exports you upload.

Where the data lives

Everything is served over HTTPS, and connector tokens are encrypted at rest. Hosting, retention, and deletion details are available on request.

Compliance

Security documentation and our current audit status are available on request.

Get started

See your own access graph.

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

We read every request.