The question about the level of detail, an IAM solution must cover, has been around since some time. But more than ever before, it is one of the most challenging questions in many IAM projects.
On the one hand, audits are requesting end-to-end coverage (from the user to the individual file, document, folder). On the other hand, the amount of data is growing disproportionately with each implemented level. Some implementations stop the IAM administration at group-level in general in order to keep data in a range, that still can be managed. Others go further. What level of detail does make sense? Is it realistic, to run e.g. 10.000+ Windows folders by one central IAM solution? Are there alternatives to a full implementation of ´User to Ressource´ relations? Is the growing number of data access management systems an appropriate complement to IAM for this challenge?
However, this is not only – and maybe not even primarily – a technical issue. It is about organization. It is about accountabilities and responsibilities. How to define the levels and how to ensure that cooperation works for instance between persons responsible for systems and others being responsible for the overarching IAM system?
Join this thought leadership panel session to get answers to your questions.
Entitlement & Access Governance defines an approach that combines the cross-system view of Access Governance with system-level management of entitlements. However, there are various ways to keep your data under control. While some vendors address the challenge by expanding their Access Governance solutions, others tackle it from the system and data level. Which approach works better? And for whom? In this discussion, Borja Rosales of Druva and Pervez Goiporia of Oracle will discuss with KuppingerCole Analyst Amar Singh about the pros and cons of various approaches on Entitlement & Access Governance – or just Data Governance.