{"id":1590,"date":"2017-11-03T11:36:24","date_gmt":"2017-11-03T15:36:24","guid":{"rendered":"https:\/\/solutionsreview.com\/identity-management\/?p=1590"},"modified":"2017-11-06T15:06:51","modified_gmt":"2017-11-06T19:06:51","slug":"rsac-17-unsticking-your-privilged-access-management-program","status":"publish","type":"post","link":"https:\/\/solutionsreview.com\/identity-management\/rsac-17-unsticking-your-privilged-access-management-program\/","title":{"rendered":"RSAC ’17: Unsticking Your Privileged Access Management Program"},"content":{"rendered":"

Nearly every breach involves privilege elevation. To address this problem, most companies will buy a Privileged Access Management (PAM) solution, \u00a0which let them manage, monitor, and protect powerful privileged user<\/a>\u00a0accounts within the IT infrastructure of an enterprise.<\/p>\n

However, many of these PAM solutions stay on the shelf or are woefully under deployed against the vast number of privileged accounts present in an organization. In this 45-minute session, Lance Peterman, Identity and Access Management Architect at Merck, will provide a core understanding of what a PAM program should contain and tips on how to avoid common pitfalls that keep a PAM program from reaching its potential.<\/p>\n