Enhanced Systems Access Management (eSAM) FAQs

  1. What is a privileged account?
    Privileged accounts are root and system administrator accounts
  2. Will sessions be recorded when a privileged account is access by someone other than the system owner?
    Service owners can check out privileged accounts without workflow or recording of the session. Anyone who is granted access to a privileged account through workflow, will be connected to the system without the password being given to them (e.g. SSH or RDP) and the session will be recorded.
  3. Is there redundancy for the eSAM application?
    Yes. There are currently two geographically dispersed and replicated PAM servers
  4. Can a system owner delegate authorization when they are away?
    Yes, Instruction will be in user documentation.
  5. Is eSAM logging and auditing user access?
    Yes, all access will be logged, audited, and can be reported on.
  6. Do system owners have to go through workflow to get access to privileged accounts?
    No, system owners can automatically checkout a privileged account without going through workflow. 
    If not a vault owner you must wait for a safe owner to provide access to a specific vault.  
  7. What accounts are managed by eSAM?
    eSAM manages Administrator on a Windows system and sysadmin and root on a Linux System. eSAM has a broad variety of connectors to manage almost any privileged account including managing a variety of other accounts such as EAD service accounts, Cisco devices, passwords in scripts, etc.