Extending an organization’s access management services into the cloud is ad hoc, dependent on your cloud service...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
provider, and rudimentary at best. However, with that said, there are some steps you can take to utilize cloud services as they become more mainstream:
- Ask your cloud service provider to support open standards for access management.
- Standardize and automate your user provisioning as much as possible.
- Create a centralized entitlement management mechanism within your organization.
- Extend policies and procedures regarding access management to include cloud services.
Let’s take a closer look at these steps, particularly the two key architectural and process components of access management services that need to be considered in the cloud:
- Entitlement (privilege)management: assignment and enforcement
- User provisioning and de-provisioning
Organizations who want to utilize access management in the cloud will need to spend a significant amount of time ensuring their systems and applications have the ability to consume an externalized entitlement management service. In a nutshell, this means designing your application and systems to provide and consume eXtensible Access Control Markup Language (XACML) type information. XACML is the leading general purpose standard for describing policy management and access decisions. It describes a language as well as a processing environment model. The main purpose of XACML is to allow organizations to implement a common authorization standard across all systems and applications by providing a standardized language, a method of access control, and policy enforcement. In contrast, Security Assertion Markup Language (SAML) is an open standard used for federated identity.
The key is that you will have to ensure your systems and applications can consume the XACML information, and that your IAM system can provide it.
The reason I stress XACML is that it is an open standard; you should be wary of spending significant amounts of resources to integrate into a cloud service provider’s proprietary entitlement management system. When it comes to the cloud, open is better.
However, I don’t know of an existing cloud service provider that supports the ability to have externalized entitlement management on a large scale. Meaning that while this is an admirable goal, the reality of cloud providers being able to consume or provide entitlement management is currently not practically feasible. For now, focus on providing the entitlement service and consume it with your own applications or systems. Think of this as a early frontier; as time passes, adoption of standards such as XACML will pave the way for a more universal entitlement management across cloud services.
Along with identity and entitlement management, user provisioning and de-provisioning are key elements of identity and access management services. User provisioning is the process of allocating users to systems and applications and effectively granting identities access to information and systems. In order to effectively utilize IAM in the cloud, you will need to have an efficient process for user creation and removal. This process of provisioning and de-provisioning will set the initial entitlements and link them to an identity.
You should look to see how your current provisioning process integrates Service Provisioning Markup Language (SPML) to make providing and consuming the service as seamless as possible with your cloud service provider. Like XACML, SPML is a standard, and utilizing it as the basis for your service provisioning will provide future benefits of interoperability you would not get if youintegrate with proprietary cloud solution. Using SPML can allow you to standardize and automate much of the provisioning process, which is critical for a successful IAM operation in the cloud.
The need for standards
Standards for access management services are critical to ensure future cloud adoption. By using open standards -- as well as requiring cloud service providers to support them -- we set the foundation for a consistent and secure method of service offering and use. If the Internet has taught us anything, it is that the use of standards is the way to promote wide adoption and use of technology.
About the author:
Philip Cox is a principal consultant of SystemExperts Corporation, a consulting firm that specializes in system security and management. He is a well-known authority in the areas of system integration and security. He serves on the Trusted Cloud Initiative Architecture workgroup, as well as the PCI Virtualization and Scoping SIGs. Phil frequently writes and lectures on issues dealing with heterogeneous system integration and compliance (PCI-DSS and ISO). He is the lead author of Windows 2000 Security Handbook Second Edition (Osborne McGraw-Hill) and contributing author for Windows NT/2000 Network Security (Macmillan Technical Publishing) and CIW Security Professional Certification Bible(Wiley).