IAM Meets The Extended Enterprise
Company boundaries are blurring as businesses interact closely and utilize online services in growing numbers. Business ecosystems include different stakeholders including customers, partners, and subcontractors to owners and investors. Each stakeholder has their own business processes, infrastructure, and identities. As the number of external stakeholders grows, so, too, does the need to better manage these identities.
It is not enough today to know who is accessing your online services, but also in which role / capacity they enter, or who they represent.
Traditional identity management solutions, which concentrate on provisioning employee identities from the HR-system to the Active Directory, and providing Single Sign-On to internal applications, are ill-suited for this situation. New ways of thinking are required to improve convenience and loyalty towards customers, to deploy secure online services, to minimize the cost in customer acquisition and external identity management.
Internal vs External identities
The business drivers behind an Identity Management or Identity Relationship Management deployment — regulatory demands, desire to cut cost, improve security – differ when what’s at issue is internal vs external identities. This translates to different demands to the solutions companies need to select in order to satisfy the business objectives.
Productivity vs Convenience
A Single Sign-On deployment is likely required for both internal vs external facing use cases, but the driver might be different and skew the importance of the feature set that is required. Internally the wish is to increase productivity by enabling employees to login into company applications without repeated password entry. For external identities SSO brings convenience for the business customer as they can login from their corporate network to the online services with their own business IDs.
Where the focus of internal identities is compliance with security policy, with external identities, compliance likely means adhering to local regulations where access to sensitive information may require the use of a credential which has a security level described by the local legislation / regulation (e.g. NIST or STORK).
Efficiency vs Customer Acquisition
Workflows such as inviting people to use a service or requesting access privileges with the tools the IAM provides can improve internal efficiency. But for external identities the driver is to facilitate customer acquisition process by enabling e.g. sales people to invite leads and customers to use the services directly from the CRM.
Audit vs Lead and Customer Tracking
Internal identities certainly need good audit trails, but for external identities the same audit trail has monetization potential – when it can help better target existing customers with upsell opportunities and converting leads into paying customers faster.
Standardization vs Openness
An internal corporate network gravitates towards standardization, whereas the external networks that a B2B service provider wants to connect will remain heterogeneous and diverse.
Centralized vs Distributed and Heterogeneous
Again the underlying technology would be the identity provider and much the same way as in standardization companies wish to centralize the access policies and decision points. Externally the identity provider also should support decision-making points within the customer organization which can permit access and let the customers manage their own privileges. This means that even though internally the company might select a single standard or process to follow, for external connected identities and networks, they need to embrace diverse options.
Internal Control vs Outsourced & Tiered Management
Employees and their access credentials as well as authorization should be controlled internally. Externally it makes much more sense to let the customer organization attach (authorize) access privileges to their employees. This would save a lot of effort for the company offering the online service to external companies i.e. customers.
Ownership vs Trust
Companies want to own their employee identities at least to some extent. The concept of Bring Your Own ID (BYOID) might change this slightly, yet the company would want to retain control over access privileges (roles, authorizations). For external identities, at issue is defining trust – since the online service provider should be able to trust the identities coming from the customer domain, and trust that their access privileges are properly maintained within the customer organization.
Organizations have a tremendous opportunity to enable new business models with significant impact on the bottom line – and that includes all kinds of organizations, from service provider, manufacturer, utility company, retailer, financial or healthcare institute, or even the government. As more interactions and assets move online, providing the right identity and lifecycle management services will become fundamental to creating new business paradigms and ensuring trust.
By Petteri Ihalainen