The IT Lead
Sign inGet started

Service account ownership reviews

Know who owns every service account, why it exists, and when it was last reviewed.

For small IT teams and MSPs with dozens to hundreds of service accounts and no appetite for a full identity governance suite. Import a CSV, nominate owners, collect attestations, keep a review trail an auditor can follow.

No credit card required to create a workspace. CSV import works on day one.

acme-it / service_accounts
214 rows · review Q4
IdentifierStatus
svc-backup-veeamAD · j.kellerReviewer accepted
sql-reporting-roEntra ID · m.ortizOwner attested
gh-actions-deployGitHub · no ownerUnknown owner
sp-intune-syncEntra ID · a.brandtOwner nominated
svc-print-legacyAD · r.hahnReview overdue
aws-billing-exportAWS IAM · s.ngPending
svc-sftp-payrollAD · l.vogtNeeds investigation
sample dataAPI connectors: not connected

CSV row ≠ attestation ≠ API check

  • CSV

    CSV row. Imported data. Says an account exists in a file, nothing more.

  • ATT

    Attestation. A named owner confirmed ownership, purpose and need.

  • API

    API check. Technical verification against the source system. Shown only when it happened.

Scope

One job, done carefully

The IT Lead records ownership and review decisions. It does not touch your directory.

Does

  • Import service accounts from CSV with validation and dedup
  • Assign nominated owners and schedule 30/90/180-day reviews
  • Send secure, time-limited attestation requests by email
  • Collect owner confirmations: own, purpose, still needed, access review
  • Reviewer accepts, requests clarification, or opens investigation
  • Full audit trail: who attested, when, and how
  • Exportable review report showing what was confirmed vs not checked

Does not

  • Act as an IAM, PAM, or directory administration platform
  • Scan for vulnerabilities or issue compliance certifications
  • Disable accounts or rotate passwords
  • Perform SCIM writes or session invalidation
  • Store passwords, API keys, or access tokens
  • Claim technical verification from a CSV import

Workflow

From CSV to evidence in four steps

A real CSV-to-owner-review-to-evidence flow. No "all secure" badges.

  1. 01import

    Import

    Upload a CSV of service accounts. Preview duplicates and errors before committing.

  2. 02assign_owner

    Assign owners

    Nominate an owner for each account and set a review interval of 30, 90 or 180 days.

  3. 03request_attestation

    Request attestation

    Owners get a secure, time-limited link and confirm ownership, purpose and whether access is still needed.

  4. 04review

    Review evidence

    Accept, request clarification, or investigate. Export what was confirmed and what was not independently checked.

Evidence model

Different evidence types, labeled as such

A CSV row is imported data. An attestation is a person's confirmation. An API check is a technical verification. Nothing turns green just because someone clicked confirm. Unverified stays neutral or amber.

svc-backup-veeamevidence
source
CSV import, 14 days ago
CSV
owner
Attested by j.keller@acme.example
ATT
reviewer
Accepted by IT lead
REV
privileges
Not checked against directory
API

Start tracking who owns what

Create a workspace, import a CSV, and send your first review request.