Check out the webinar replay done by Nick Wooler and me on the latest product offerings (Sun Role Manager 5.0 and Directory Server 7.0):
The presentation can be downloaded below:
Check out the podcast by Matt Modica from ESI and Nick Crown, PLM for Sun Role Manager & Identity Manager on here.
The discussion is centered around the Identity & Access Mgmt. project undertaken by ESI, their architecture, challenges faced and lessons learned.
Last week, I discussed a very interesting requirement posed by a customer where they were looking for complete glossary management for entitlements being managed in their warehouse of user identities. A major problem for them today is most entitlements, especially for mainframes, is not clearly understood by the business when they perform their quarterly attestation reviews. To add to that, there are no tools available in the market today that provide a centralized view for managing glossary definitions and security features that allow multiple owners to complete glossary definitions, that can later be leveraged by not just an attestation solution, but also by provisioning solutions and other downstream applications that require lines of business to thoroughly understand the meaning of cryptic entitlements (such as a RACF group membership or the true meaning of an SAP role).
According to them, this solution would truly provide an enterprise wide capability to effectively manage glossary definitions across applications and target systems, at the same time providing a means to attest to the validity of the entitlements themselves. According to another large banking customer, there is an entitlement creep that happens to an organization across time, and these entitlements are never cleaned up in the target systems. A mechanism to truly understand the meaning and whether the entitlement is indeed needed or not, is called for.
This begs for another question, in addition to regular glossary management capabilities (CRUD) do glossaries need to be approved before being defined or modified, for all entitlements? This would require workflow capabilities in order for designated for "glossary owners" to approve any changes being made to glossaries. Moreover, glossary owners would then be required to attest glossaries, and most importantly, the need for all entitlements pertaining to a target system or application on a regular basis, to provide comprehensive evidence to auditors that unwanted entitlements are actually being revoked from the target systems on a regular basis, furthermore, moving towards least privilege.
Its that time of the quarter again! Lets do some User Access Reviews! Its pretty much the case with most organizations, its one task managers do not look forward to. And I wouldn't blame them. Certifying a users access on a mainframe or Active Directory is not a manager's dream job. As a vendor and product manager, some questions related to this problem arise:
I'm a Product Manager, based in Austin, TX.


Recent Comments