Interpreting the Overview dashboard
The Privileged Access Service dashboard overview provides a summary of information about all of the objects added to Privileged Access Service. For example, the dashboard includes the total number of systems and accounts you are managing, the systems that have had the most password checkout activity, and a list of the account passwords that are currently checked out with the date and time when passwords where checked out and when the passwords are due to be checked back in.
You can access the following information by selecting the various dashboard options in the dashboard drop-down menu.
- Total Systems is the total number of servers and network devices you have added to the Privileged Access Service.
- Total Accounts is the total number of accounts you have added to the Privileged Access Service.
- Top System Checkouts lists the systems that have had the most password checkout activity for the last seven days.
- Systems By Type provides a pie chart overview of how many systems you have added to the Privileged Access Service by operating system type. For example, you can see how many systems are Windows, UNIX, or Cisco network devices.
- System Health indicates the number of systems that are reachable using the accounts stored in the Privileged Access Service and the number of systems that are not reachable.
- System Logins is a map that illustrates where the systems that have had login activity are located.
- Recent Activity lists the date and time for recent password check out, password check-in, and login activity.
- Password Checkouts lists all of the accounts that have a password checked out, when the password is due to be checked back in, and the user who checked out the password.
- Active Sessions lists the systems where there are sessions initiated from service using stored account information or manually-entered credentials.
For privacy reasons, user location data in the Admin Portal is based on the IP address used to access the Privileged Access Services. This IP address is often virtually assigned, so it may not reflect the actual log in location.