Hybrid Deployment Model.
Shared Brain, Private Body.
PAM-Pro utilizes an innovative "Shared Brain, Private Body" architecture, providing a unified SaaS control plane for governance and ticketing, while maintaining discrete customer Key Vaults and Storage to ensure absolute cryptographic isolation.
SaaS: The Shared Brain
The central SaaS platform serves as an unprivileged orchestrator tracking metrics, SLA expirations, and ticketing workflows, while your "Private Body" consists of discrete, isolated Key Vaults and Storage Accounts deployed specifically for your environment to broker physical credentials.
- Independent Customer Policy Control
- Ephemeral Session Management
- Multi-Tenant Microsoft Entra ID Connections
On-Premise: Total Sovereignty
The On-Premise model utilizes the exact same single-account architecture as SaaS, but delivers it as a full standalone deployment entirely within your physical infrastructure or private Azure subscription, ensuring absolute air-gapped isolation.
- Sovereign Infrastructure Ownership
- Ephemeral Session Management
- FIPS 140-2 Level 1-3 Support
SaaS Separation of Duties
Defining the clear boundary between Platform Hosting and Data Ownership.
- Platform Patching & Infrastructure
- Core SaaS Infrastructure Hosting
- 99.9% Uptime SLA Compliance
- Continuous Security Vulnerability Scanning
- Application Governance Workflows
- Microsoft Entra ID Sync Pipelines
- Entra ID Risk Signal Telemetry (P2)
- Tenant Root Encryption Key (TREK) Custody
- Per-Account Authorization Policy Definition
- Account Discovery Scope & Promotion
- Regular Audit Log Review & Attestation
Tri-Layer Protection
Regardless of deployment model, PAM-Pro enforces a rigorous zero-knowledge custody chain. Vaults are mandatorily dual-keyed using Microsoft defaults alongside a dedicated Tenant Root Encryption Key, enveloping all payloads mathematically.
SLA & Shared Responsibility
Understanding the operational constraints of mathematically enforced Zero-Knowledge.
Root Key Rotation & Reset
Rotating the Tenant Root Encryption Key will mathematically sever access to all currently enveloped payloads. This will force a mandatory password reset event across all managed accounts.
Huntoso Mitigation: Configuration stores are backed by Azure Blob Versioning and native immutability locks to prevent accidental payload locks.
Break-Glass IdP Reliance
Huntoso deliberately refuses to store local "back-door" Break-Glass credentials to ensure complete identity continuity. If Microsoft Entra ID experiences a global outage, PAM-Pro authentication is suspended until Microsoft SLA resolves.
The Benefit: The identity of your secrets remains entirely with you, preventing lateral Huntoso breach risks.
Default Audit Horizon (1-Day to 365 Days)
By default across all SaaS tiers, Huntoso maintains WORM-compliant Immutable Audit telemetry for a strict 1-day default retention window to maximize client data privacy and minimize exposure footprints.
Customers requiring prolonged compliance retention can configure their environment for up to 365 days. Huntoso.ai cannot delete or truncate customer audit records while an immutability retention policy is active.