Skip to content
ANCHOR

Accounts

Accounts represent privileged identities associated with managed resources. They support access, rotation, reconciliation, or verification depending on the resource type.

Signal Stale account

Activity or verification signals suggest review is needed.

Owner Missing owner

Ownership is unclear, slowing remediation and access review.

Lifecycle Rotation due

Credential lifecycle no longer matches policy expectation.

Evidence Failed verification

Observed state may not match inventory reality.

Common categories include managed accounts, reconcile accounts, discovered accounts, break-glass accounts, service accounts, and temporary or brokered session identities. Keep naming explicit so operators understand the account purpose and expected lifecycle.

Account records connect resource ownership, policy expectations, rotation posture, verification state, reconcile relationships, and audit history. Stewardship should make it obvious who is responsible for the account and what Anchor expects to be true about it.

Review stale accounts, missing owners, failed verification, overdue rotation, policy mismatches, and standing access that could be replaced by just-in-time workflows.

Account hygiene is one of the places Anchor should feel different from legacy PAM. Instead of treating account cleanup as a periodic spreadsheet exercise, Anchor keeps stale access, missing coverage, failed checks, drift, and unclear ownership visible inside the operating model.

Verification asks whether the account or credential state still works as expected. Rotation changes managed credential material according to policy. Reconcile brings mismatched target state back into alignment through a controlled recovery path.

Each workflow should produce job steps, logs, audit context, and posture signals that reviewers can follow later.

Do not use production administrator accounts for early testing. Create lab accounts with limited blast radius and documented cleanup steps.