According to IT research firm Gartner, Inc.’s estimate, almost half to two-thirds of businesses approach identity and access management in the wrong way, since initial considerations include only production requirements. In his recent paper “A Process View of Identity and Access Management Is Essential”, Earl Perkins, the research vice president at Gartner observes that the traditional “build” of formal identity and access management (IAM) systems suffer due to wrong direction and participation of the wrong people.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Although Gartner points to improvement in certain experiences along with evolution of technologies, it observes that major efforts to formally build an identity and access management system for an organization overlook a key lesson—planning does not include everyone who should be involved. Due to the introduction of risk, compliance, accountability and transparency, identity and access management has seen changes. Gartner observes that the basis for good identity and access management involves active roles from the entire organization—not just IT. This approach ensures the required extent, accountability and transparency of access.
A merit of this approach as Perkins observes, is that identity and access management products occupy a relatively minor focus of the decision process in the entire program. Viewing identity and access management as a process also helps identify key queries during product selection (for example, how do products fulfill certain process steps). Viewing identity and access management as a process helps an enterprise articulate its requirements and target them through prioritization of need. It helps map the identity and access management process on top of known business processes to determine the convergence or touchpoints for control and intelligence purposes. Process steps that are best performed manually or are people-intensive can be identified, as can different identity and access management process flows for different organizations, applications or system environments.
The operational process view can also enable businesses to define organizational roles for managing IAM, as well as develop identity and access governance model that incorporates such operations. By linking operational identity and access management process to the policy model of the organization, this part of IAM governance can be established as a lifecycle, rather than as an ad hoc set of activities applied in a reactionary way to access and identity problems. Identity and access management as a process can be effective in converging business and enterprise processes with IT processes and accelerating IAM program maturity for the long term.