Why ZenXPAM

Four things legacy PAM cannot do

A side-by-side look at how ZenXPAM approaches privileged access compared with how PAM is usually built.

Enforcement, not just observation

Every PAM product records privileged sessions and lets you find the violation afterwards. ZenXPAM compiles the justification on a request into an approved command scope, lets the approver review and edit it, and enforces it at the target - in the kernel on Linux shell sessions and at the query proxy for databases. Out-of-scope actions are blocked before they run. On other transports the session is recorded, reconstructed and risk-scored.

AI that runs inside your perimeter

Risk explanation, intent compilation, natural-language policy authoring and audit search run on a local model inside your own deployment, and a local provider is enforced in production. The AI keeps working with no outbound connectivity at all - which is what makes it usable in environments where a cloud-delivered assistant simply cannot be switched on.

Built multi-tenant, in any hosting model

One deployment serves many customer tenants, each with a signed entitlement defining its ceilings, feature modules and validity window, under a single cross-tenant console. It works whoever hosts it - you, your customer, or a sovereign datacentre - so onboarding a customer is a provisioning call against infrastructure you already run.

Evidence an auditor can verify without trusting us

Audit records are hash-chained, and evidence packs are signed with a per-file manifest and an offline verifier. Internal controls map to named clauses in several frameworks at once, so one control answers SOC 2, ISO 27001, PCI DSS, HIPAA and NIST in the same review. "Tamper-evident" is a checkbox; independently verifiable is a different conversation.

Side by side

ZenXPAM versus conventional PAM

Compared against how privileged access management is typically architected.

CapabilityZenXPAMConventional PAM
Approved scope enforced at the targetLegacy PAM records the session and reviews it later
AI usable with no outbound connectivityCloud-delivered AI cannot be switched on in sovereign estates
Many tenants on one deployment, partner-hostedTypically one tenant or instance per customer
Standard, just-in-time and emergency access in one workflowUsually separate modules with separate licences
Signed evidence with an offline verifierExport and screenshots are the norm
No appliance, no Windows Server or SQL Server estateA recurring licensing and maintenance cost elsewhere

Recently delivered

Machine identity, now in the product

New capabilities added to ZenXPAM, ready to evaluate in a proof of concept.

  • Non-human identity inventory: a read-only scan of AWS access keys, Azure app secrets and certificates, GitHub App installations and Google Cloud service-account keys, with owner triage and dormant-identity flags
  • Scheduled safe rotation for AWS IAM keys and Azure client secrets, with a grace window, verification before cutover and one-click rollback - proven against live AWS and Azure accounts
  • Short-lived GitHub App installation tokens issued on demand, instead of long-lived personal access tokens
  • Secret delivery to workloads through TypeScript and .NET SDKs and a zenx-secret CLI, with the previous value kept during the grace window
  • SSH key rotation on target authorized_keys files with pinned host keys
  • On-premises OCR text search across recorded graphical sessions, and a post-session review of what a session did against what it was approved to do
  • ACME certificate renewal (dns-01) for server and client certificates
  • Google Cloud service-account key rotation

Coming next

What's coming next

Planned expansions of the ZenXPAM platform.

  • Cloud infrastructure entitlement management (CIEM) across AWS, Azure and GCP
  • HSM and external key-manager integration, and a formal cryptographic validation path
  • Packaged DevOps secret providers for GitHub Actions, GitLab CI and Jenkins (GitHub App tokens and the secret-delivery SDKs and CLI are available now)
  • Service-account lifecycle governance beyond rotation and storage (inventory, scheduled rotation and dormant-identity flags are available now)
  • Full-text search across recorded session video (OCR text search over graphical sessions is available now)
  • Workload identity federation and AI-agent identity governance
  • M-of-n recovery-key escrow for the vault, so a quorum of custodians can recover credentials without the master password
  • Native OT and ICS protocols - reached today through RDP and SSH jump hosts

Procurement and security review - common questions

See the enforcement in a live session