1Commando  /  Product  /  Access creep
Access creep

Find access that stayed after a job change.

In development The timeline view is being built. Today, access granted while someone worked in another department counts more toward a flag, and the flag names that department, for example "granted while in Engineering". Flagged grants go to the access review.

The timeline will show each grant from the date it was added, mark each job change from your HR system, and draw in red the access that stayed after the job changed.

Scroll sideways to see the whole timeline.
2019 2020 2021 2022 2023 2024 2025 2026 ENG ACCT FIN JOINED · SOFTWARE ENGINEER · 2019-04-08 MOVED · SENIOR ACCOUNTANT · 2022-09-05 TODAY team-core-api · 5 flagged · last used 2026-09-21 eng-oncall · 5 flagged last used 2022-11-02 team-general-ledger team-general-ledger finance-approvers · 2023-01-10 10 FLAGGED ENGINEERING GRANTS STILL HELD · 5 UNUSED SINCE 2022-11-02 GRANTED FOR THE JOB AT THE TIME HELD AFTER THE JOB CHANGED
Sarah Mitchell's access in the demo org. She moved from Engineering to Accounting on 2022-09-05, and ten flagged engineering grants are still held. Five of them have not been used since 2022-11-02.
How it works
01

Grant dates

Each grant carries the date it was added, who added it, and when it was last used, wherever the source system records them.

02

Job changes marked

Title and department changes come from the job history in your HR system. Each of the person's own memberships and direct grants is matched to the job they held when it was added, and the trail's evidence table shows that job on the first step.

03

Creep in red

A grant added while the person worked in another department counts more toward a flag, and the flag names that department. Flagged grants go to the access review. The timeline will draw them in red.

What you get

Access creep, in practice.

  • Flags that name the department a grant came from
  • Job history from your HR system matched to the date of each membership and direct grant
  • Evidence of when access was added and by whom on every trail
  • A timeline per identity, once the view ships
Included · Dormant access

Access nobody has used in 90 days.

Standing access that nobody uses is the easiest risk to remove. A sensitive grant unused for 90 days counts more toward a flag, and the flag says how long it has gone unused. When a flagged grant has gone unused for 90 days, the access review recommends removing it.

Sarah Mitchell
GitHub · prod-deploy environment
last used 2022-11-02
Unused 90+ days
ramp-sync
Brex · Approver
last used 2026-03-02
Unused 90+ days
legacy-backup-svc
AWS · S3 bucket db-backups
last used 2025-12-18
Unused 90+ days
Maya McCarthy
Salesforce · System Administrator
last used 2026-09-19
active
Travis Park
NetSuite · Payment approval
last used 2026-09-19
active
Request removalApprove for one yearThe review recommends removal for the three unused grants and approval for the two in use. Access stays live until it is removed in the source system.
Five grants from the demo org, three of them unused for more than 90 days.
01

Detect

Last use comes from the Okta sign-in log, the AWS credential report, last-login dates in Snowflake, Salesforce, and Google Workspace, GitHub's last-active date, the time each Slack user record was last updated, and usage columns in admin exports. The threshold is 90 days.

02

Decide

A flagged grant unused for 90 days comes to the access review with a Revoke recommendation. The reviewer requests removal or approves it for one year, with an optional reason.

03

Verify

1Commando only reads from your systems. Once the access is removed at the source, the next import shows it gone and the grant leaves the review.

  • An unused-for-90-days count on the overview
  • Last use on every flag and every review row
  • A removal recommendation for every flagged grant unused for 90 days
  • Last-use dates in the auditor export
Get started

See your own access graph.

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