Mortimer had the experience of privileged access management (PAM) at a previous employer. He set out to find a PAM solution that would be easy to adopt and manage for the University’s complex infrastructure.
As we were introducing PAM for the first time, we wanted to ensure it would be straightforward to implement and use as possible. There are bigger brands in the market, but they are considerably more complex and expensive. From a capability and cost point of view, Osirium came top of the contenders.
After reviewing several vendors offerings, he quickly focused on Osirium PAM. “As we were introducing PAM for the first time, we wanted to ensure it would be straightforward to implement and use as possible. There are bigger brands in the market, but they are considerably more complex and expensive. From a capability and cost point of view, Osirium came top of the contenders.” says Mortimer.
Implementation started with a small set of vendors onboarded with PAM and then expanded usage. That’s a typical deployment pattern with Osirium PAM and an excellent way to show early benefits without large, all-encompassing projects. Now, almost all vendors can only access systems via PAM.
Administrator accounts on the target systems and devices are protected because the vendor never has direct access and can never discover the administrator credentials. Access can also be granted for specific periods, for example, only during working or non-working hours. Occasionally, access may be set up for a vendor for a short period around a specific project, for instance, during a recent upgrade to the campus CCTV system.
Since adopting Osirium PAM, whenever any issues were found, the University worked closely with the Osirium support team have been able to do everything they wanted to do, and now PAM “just ticks over and we have one less treat actor to focus on.”