Core Concepts
Users, scopes, resources, accounts, policies, jobs, sessions, and logs in one operating model.
Anchor docs explain the operating model behind the platform: how privileged access is organized, governed, automated, and reviewed.
The documentation follows the same objects administrators work with in the product: users, scopes, resources, accounts, policies, Anchor Connect sessions, logs, My Locker, API workflows, and evidence for review.
Core Concepts
Users, scopes, resources, accounts, policies, jobs, sessions, and logs in one operating model.
Resources
Managed resource and account context for privileged access governance.
Accounts
Privileged account hygiene, ownership, and review concepts.
Policies
Security as Code control logic for access, verification, rotation, and governance.
Security Model
Zero Trust access, least privilege, policy-driven access, and ledger-backed integrity.
Audit and Compliance
Review evidence, posture signals, policy drift, stale account detection, and standards-aligned reporting.
Logs and Audit
Actor, target, operation, policy context, result, and timestamp evidence.
Anchor Connect
Secure session access and isolated access paths through Anchor Connect.
API Examples
Representative automation examples for policy, verification, rotation, audit, posture checks, drift, and session requests.
Architecture
Anchor Engine, Web UI, Anchor Vault, Anchor Connect, and Anchor Compass in one high-level component model.
Start with the object model, then move into security, automation, and Anchor Connect. The pages are intentionally concise: they focus on the concepts a buyer, security architect, or operator needs to understand before a technical walkthrough.