Separating people (system administrators and third parties) from device passwords (known as privileged access management) allows users to keep their personal passwords and profiles, and be able to map identities to specific roles on specific devices across an infrastructure. This means users can access systems that they need to.
This leads to real accountability: before you could have a situation where a team of people would all use a shared password to systems, now you have identities having sessions on systems. This leads to knowing Who did What Where and When – and this means there's nowhere to hide inappropriate access.
In this webinar we will explore the importance of separating the unpredictability of people from passwords, direct system logons and legacy applications.
Key takeaways:
- A project is not finished when it works – it is only finished when it is SECURE
- Legacy applications are technical debt – this debt needs to be paid, or incumbent interest will swamp the organization
- Taskification – modest upfront time costs that give the triple win of speed, security and compliance
