“No man is an island,” said John Donne, and that would also be true of every modern business. Somewhere, for some reason, every organisation must work with suppliers or partners – the “third parties” in the title.
There’s a lot of good that can be achieved when working closely with third parties, but there are also a lot of risks. Perhaps the most infamous example of third-party access going bad is Target stores in the US which lost private data on 70 million customers related to data shared with their HVAC supplier.
That’s not a reason to prevent all close working with partners. With the right controls and monitoring in place, access not only becomes secure but easier to manage. In the latest episode of the Osirium PAM Express Tutorials series, we take on the weighty issues of allowing third-party access whilst maintaining high security.
Essentially this breaks down into six steps:
Third-Party Access Architecture
In this new video in the PAM Express Tutorials series, you see the user experience through the Remote Web Gateway, this is useful when your third parties cannot install software on their own workstations. It gives RDP, SSH, Web and MAP Server access along with all the defined tasks in Osirium PAM.
As always, if you’d like to know more, please get in touch.