Six request types
Requests shaped like the work
General, Asset Permission, Application, Command Confirm, Login Confirm and Login Asset Confirm, each raised as its own request type, with configurable multi-level approvals behind it.
Privileged access that fits the systems you already run.
Privileged access management fails when it becomes a second place to manage users. OmniPriv connects natively to the ticketing, monitoring and directory systems that already hold your identities and your events.
Approvals run through tickets your teams already understand, access events reach the SIEM you already correlate in, and users, groups and entitlements stay sourced from LDAP or Active Directory rather than duplicated beside it.
One request · the systems you already run
Request log
oracle-fin / sysCredential withheld
Connected, not copiedillustrative
- built-in request types, each with multi-level approvals
- 6built-in request types, each with multi-level approvals
- LDAP and Active Directory sync for users, groups and entitlements
- 2-wayLDAP and Active Directory sync for users, groups and entitlements
- SIEM event forwarding, no batch exports
- LiveSIEM event forwarding, no batch exports
- protocol proxies: RDP, SSH, VNC and HTTP
- 4protocol proxies: RDP, SSH, VNC and HTTP
A ticket is a gate, not a paper trail
Every privileged action can be made to depend on an approved ticket, checked at the moment of release rather than reconciled afterwards.
On retrieval
Tickets raised automatically
Requesting a privileged password raises a ticket and the full approval workflow on its own. The credential stays withheld until that workflow completes, so nobody has to remember to open one first.
Before release
Pre-access verification
A ticket is a mandatory prerequisite before privileged credentials are released. Ticket status is checked in real time, so pending, rejected and closed tickets block the release automatically.
Connect to whatever already holds your identities
Directories are the source of truth, and they are treated that way. Users and groups are synchronised against LDAP or Active Directory in both directions, so a joiner, a mover or a leaver is reflected in privileged access without a second provisioning process to keep in step.
Identity Management platforms plug in at the same layer for user lifecycle management and automated provisioning, which keeps entitlement decisions in the system that already owns them.
- LDAP and Active Directory integration with bidirectional synchronisation
- Automatic user and group provisioning driven by the directory itself
- User entitlement management, so privileged access follows the directory rather than a copy of it
- Identity Management integration for lifecycle management and automated provisioning
Directory sync · bidirectional In sync
LDAP / AD
source of truth
OmniPriv
privileged access
s.patel · Added to DBA-Prod
Privileged access provisioned
One event stream into the systems you already monitor
Privileged activity is only useful when it lands where your analysts are already looking, and when the access path itself carries no permanent credentials.
Real-time SIEM forwarding
Privileged access events are forwarded to your SIEM platforms in real time for centralised security monitoring and event correlation, rather than exported on a nightly schedule.
RDP, SSH, VNC and HTTP proxies
Sessions to targets run through protocol proxies for RDP, SSH, VNC and HTTP, keeping the credential on the platform side of the connection.
Vault access by privilege level
On top of standard proxied connections, users can reach the Password Vault itself according to their privilege level in OmniPriv, so access is scoped to the role, not the network position.
No parallel monitoring stack
Nothing has to be stood up alongside your existing tooling. Events, tickets and entitlements all flow through the systems your teams already operate.
Event forwarding · SIEMReal time
- VNCsession closed · scada-hmi-04 sent
- HTTPconsole login · vcenter-01 sent
- RDPsession recorded · win-db-02 sent
- SSHsession opened · linux-prod-01 sent
Integrations you can point at
Every connection listed here is built in, not a professional-services project.
Ticketing6 request types
LDAP / Active Directorybidirectional sync
Identity Managementlifecycle and provisioning
OmniPrivbuilt in, not bolted on
SIEMreal-time forwarding
RDP · SSH · VNC · HTTPprotocol proxies
Password Vaultby privilege level
Ticketing6 request types
LDAP / Active Directorybidirectional sync
Identity Managementlifecycle and provisioning
SIEMreal-time forwarding
RDP · SSH · VNC · HTTPprotocol proxies
Password Vaultby privilege level
Fit privileged access into the stack you already have
- Ticketing
- Directories
- Telemetry
- Connected, not copied
Tickets gate the release, directories source the identities, and privileged events reach the monitoring you already trust.
We will walk through the integration points against your ticketing, SIEM and directory systems.
Frequently Asked Questions
Have a question that is not here?
Talk to the OmniPriv team about your identities, systems and AI agents.
Request a DemoSix: General, Asset Permission, Application, Command Confirm, Login Confirm and Login Asset Confirm. Each has configurable multi-level approvals, so a request can be routed differently depending on the asset, the application or the action being confirmed.
A ticket is a mandatory prerequisite before privileged credentials are released, and its status is checked in real time at the moment of release. Pending, rejected and closed tickets block that release automatically, there is no window where an unapproved ticket still yields a credential.
On every privileged password retrieval request. OmniPriv raises the ticket and the full approval workflow itself, and the credential is withheld until the workflow completes. The practical effect is that the approval step cannot be skipped by simply not asking for it.
OmniPriv synchronises with LDAP and Active Directory in both directions, with automatic user and group provisioning and support for user entitlement management. Identity Management platforms integrate at the same layer for user lifecycle management and automated provisioning.
RDP, SSH, VNC and HTTP sessions are proxied so the credential stays on the platform side. Beyond those standard connections, users can also reach the Password Vault directly according to their privilege level in OmniPriv.
