Skip to content
ANCHOR OCCDocs
Talk With Anchor

Accounts and Passwords

Every privileged account in one place, its password checked and changed on schedule, and revealed only when someone truly needs it.

root on a Linux server, a Windows administrator, a domain service account, a PostgreSQL owner: each becomes an Account in Anchor, with the system it lives on, the Scope it belongs to and the Policy that governs it. The list shows at a glance what was last proven, and when.

Accounts metrics for the last 30 days
The last 30 days: operation success, connection success and connections per day.
The Accounts list with each account's target, latest proof, Scope and Platform
Each account's target, latest proof, Scope and Platform.

Prefer to see them by server? Switch the list to cards, grouped by target.

Accounts in card view, grouped by target
Card view: each card's V, R and C show its latest proof, rotation and Connect.

Anchor verifies that each stored password still works and rotates it on the schedule its Policy sets, inside your change windows. If someone changed it outside Anchor, Reconcile puts it back under control with a linked administrative account.

An account's summary showing its latest proof, its actions, its identity and the Scope and Policy that govern it
An account's summary: its latest proof, what you may do with it, who it is, and the Scope and Policy behind it.
An account's Work tab listing a successful Verify and an earlier one refused because the server's identity was not yet trusted
Every Verify, Rotate and Reconcile is a job with its own reference and result. The first Verify ran before the host's key was approved.

A change whose result is uncertain, such as a network drop at the wrong moment, is never treated as an ordinary failure. Anchor keeps the new password safely aside and marks the account for reconciliation, so a credential is never lost in transit.

Platform Password managed over Sessions
Linux SSH Terminal and file transfer in the browser
Windows (local accounts) WinRM over HTTPS Desktop in the browser (RDP)
Windows Domain LDAPS Desktop in the browser (RDP)
PostgreSQL TLS SQL workspace in the browser
Stored credential Kept encrypted only —

Most people never need to see a privileged password: Anchor changes it and opens sessions with it. When someone must, revealing is deliberate. Their role and the account’s Policy must allow it, they can be asked for a reason and to confirm it is really them, and the value hides again after 30 seconds. Every reveal, and every blocked attempt, is recorded.

My Locker holds the credentials and notes that belong to you alone: a vendor portal sign-in, a support PIN, a runbook note. Items are encrypted to you, there is no administrator view, a revealed value hides again after 45 seconds, and every view and change is recorded.

My Locker listing a credential and a secure note with their type and reference
My Locker: a credential and a secure note. Only titles are listed; nothing is shown until its owner reveals it.
Next stop · 03Privileged SessionsConnect from the browser or your own SSH client, and never see the password.