1Commando  /  Product  /  Clearance Score
Scoring

Every identity gets a score per domain.

A high score means access in that domain is expected for this identity. Confidential or restricted access in a low-scoring domain that few peers hold is flagged for review. The score measures how well an identity's access fits its role.

SM
Sarah Mitchell
Senior Accountant · Accounting · 4 peers
Clearance score
ACCOUNTING
100
FINANCE
94
ENGINEERING
5
IT
5
HR
18
Grants checked against the score
Domain
NetSuite · Controller
ACCOUNTING
Cleared
Brex · Bookkeeper
ACCOUNTING
Cleared
GitHub · prod-deploy environment
ENGINEERING
Flagged
Slack · Workspace Admin
IT
Flagged
Sarah Mitchell's scores by domain in the Marlow Industrial demo, then four of her grants checked against them.
How it works
01

Role and peers

Each department sets a starting expectation per domain. The score is 60% that expectation and 40% the share of peers who hold confidential or restricted access in the domain. Peers share a manager and title. When that group has fewer than three people, it widens toward the whole department.

02

Fit per grant

Each sensitive grant gets a fit: half the domain score, half the share of peers who reach that exact resource. Anomaly is sensitivity weight × (1 − fit), raised for access unused in 90 days, machines without an owner, and contractors on restricted systems. A grant is flagged at 0.45 and marked high at 0.70.

03

History

Job history shows where the person worked when each grant was made. Access granted while they were in another department counts for more, because many flags are leftovers from a job the person no longer has.

What you get

Clearance Score, in practice.

  • A score from 0 to 100 per domain for every person, service account, and AI agent
  • Flags weighted by sensitivity: restricted counts fully, confidential 0.6, internal 0.2, and public access is never flagged
  • No flag when half or more of a person's peers hold the same access
  • Approvals that hold for one year, with an optional reason
Included · Pre-grant check In development

Check access before you grant it.

The pre-grant check will hook into access requests in Slack or your identity provider. Before an approver clicks, they will see the score, the peers, and whether the grant would be flagged.

Access request · Slack
Dan Porter requests Brex · Approver
Sales Operations Analyst · manager Maya McCarthy · reason: "covering for Finance during close"
Commando checking the graph: role, peers, current access
FINANCE SCORE64
PEERS HOLDING0 of 13 peers
RESOURCERESTRICTED · held
VERDICTWould be flagged
DenyOpen the trailDan already reaches Brex · Approver through ap-approvers, added 2025-11-02. That grant is flagged for review.
A mockup of the planned check, using Dan Porter's scores and peers from the Marlow Industrial demo. The graph shows he already holds this access.
01

Request arrives

Requests will come from Slack, from your identity provider's access request flow, or from a ticket. Each one will be matched to an identity and a resource on the graph.

02

Commando scores it

The scoring that runs on existing grants will run on the request as if it were already granted. The approver will see the verdict, the reasons, and any path that already reaches the resource.

03

Approver decides with evidence

The approver will grant or deny in the system they already use. 1Commando only reads from connected systems, so a new grant shows up on the graph after the next import.

  • A verdict before access is granted
  • A warning when the person already reaches the resource through a group
  • The same scores, peers, and reasons reviewers see in a review
  • A record of each request and its verdict
Included · Posture score

One number for the whole company.

The posture score rolls the fit of every sensitive grant into one figure for the company and one for each domain. The overview shows the company figure and the six domains with the most open flags, and each of those domains links to the flags behind it.

Posture score · Marlow Industrial
0
957 flagged grants · 2,253 current identities
FINANCE
81
ENGINEERING
93
OPERATIONS
79
Company score and the three domains with the most flags, computed from the Marlow Industrial demo.
01

Roll up

Posture is 100 × (1 − Σ weight × anomaly ÷ Σ weight) over every sensitive grant held by a current identity. The same sum per domain gives each domain its score.

02

Weighting

Restricted access has weight 1, confidential 0.6, and internal 0.2, so restricted access counts five times as much as internal access.

03

Decisions

Approved grants and exceptions count as fitting until they expire. A removal request keeps counting until the next import shows the access is gone at the source.

  • A company score from 0 to 100
  • A score for each domain, such as Finance or Engineering
  • The flags behind each listed domain, one click from the overview
  • Credit for a removal only once the access is gone at the source
Get started

See your own access graph.

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