Get started
What DataDike PAM does and the problem it solves: it holds the credentials of privileged accounts, hands them out without showing them, brokers the sessions that use them, and records each one.
The components a running instance is made of, what each one does, how a session travels between them, and how the network path from the solution to an asset is formed.
The vocabulary DataDike PAM uses, and how the objects relate to each other.
How the console is divided into areas, how to switch between them and between organizations, and which screen holds each kind of object.
The end-to-end path from an empty instance to a recorded session: register an asset, choose its platform, register the account, write the authorization, connect, and find the recording in the audit trail.
Last updated
Was this helpful?