Imagine how much easier managing privileged access would be if numerous everyday manual tasks were done automatically for you.
Can you picture it?
There’s no need to conjure the image in your mind for too long because it’s now reality.
Device Discovery, new in the PAM 9.0 release, is your gateway to a whole world of time-saving, hassle-cutting automation.
When you see it in action, you’ll think about how easy it could make many of your many privileged access processes, such as JML.
We've been able to achieve this in PAM 9.0 by deepening the level of collaboration with Osirium PPA (Privileged Process Automation).
Osirium PAM is already ahead of the competition in terms of rapid deployment. We get PAM up and running in days, not weeks or months.
And Device Discovery is enhancing that even further. By deploying it during the initial setup of PAM, you unlock significant time savings.
On an ongoing basis, you don't want to have to go into PAM every time your organisation has a new user or a new device. What you really want is a PAM setup that knows the rules.
Device Discovery makes it faster for customers to be able to get their devices into PAM and get people using them.
You eliminate the need for tedious manual entry and preparing bulk imports, automating the process of onboarding new devices into PAM.
So, for example, when your Human Resources system provisions a new user, or when your Windows team deploys a new Windows server they've made and put into Active Directory, PAM becomes one piece in a cascade of actions that flow through automatically.
Device Discovery also lightens the load on the PAM admins too. Particularly in the case of scheduled Device Discovery, you won't need a PAM admin to be involved when a new device is added in the estate.
It will trickle through and be usable by PAM users without requiring the PAM admin to be involved – freeing their time to tackle more important matters.
It interrogates Active Directory and then pull out the Windows member servers and provision them into your PAM server.
You can run that as a one-time task, or you can schedule that to happen on an ongoing basis.
In the latter case, you potentially just need to provision a device in AD, then it can automatically flow into PAM and users will have access to it.
We’re always listening to customer feedback on how to enhance our solutions and the updates in 9.0 reflect that.
Customers asked for changes in the behaviour of change tickets. In response, we’ve implemented a package of enhancements that will make them a more streamlined and valuable feature.
Customers wanted to be able to assign a change ticket to a specific device connection rather than having change tickets apply to all device connections they make from the moment they acquire the first change ticket. And we’ve delivered that in PAM 9.0.
Want to learn more about PAM 9.0 and upgrade? Get in touch.
If you’re new to PAM and would like to book a demo or speak to our team to find out more, please contact us here.