KeySkope
KeySkope / Use case / Orphan accounts
Use case / Orphan accounts

An account exists.
Who owns it?

Surface application accounts that do not match an identity in your connected source.

The review question

No matching identity

Establish the account’s owner and business purpose. Check for old email addresses, external collaborators and service accounts.

Explore the finding
REVIEW WITH CONFIDENCE

Make the next step clear.

Unmatched does not mean unauthorised. A finding is a question to investigate, not an automatic removal decision.

From finding
to follow-through.

Use the source evidence to make an informed decision with the application owner.

01 / CHECK

Confirm the source.

Check that the connector has completed a recent successful sync and that you are reviewing the right environment.

02 / REVIEW

Understand the account.

Inspect roles, ownership and available activity. Resolve any missing context with the app owner.

03 / FOLLOW UP

Close the loop.

Make approved changes in the source application, then sync again to check the updated account information.

A clearer place to start

Know your access.
Focus your next review.