Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

6/23/2020
10:00 AM
Eric Olden
Eric Olden
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

5 Steps for Implementing Multicloud Identity

Why embracing, not fighting, decentralization will pave the way to smoother cloud migrations.

According to the "RightScale State of the Cloud" report, virtually every company (84%) that uses infrastructure-as-a-service (IaaS) or platform-as-a-service (PaaS) clouds uses more than one provider. Most employ three or more public clouds from leading providers such as Amazon Web Services (AWS), Azure, and Google Cloud Platform (GCP).

There are a number of trends driving this multicloud proliferation, including the need for greater agility, flexibility and scalability, better network performance, improved risk management, avoiding vendor lock-in, and getting more-competitive pricing.

Each of these cloud platforms uses a different, built-in identity system that creates separate silos. Meanwhile, identity-as-a-service (IdaaS) solutions that manage access to SaaS apps introduce yet another separate identity store. Despite this accelerating cloud adoption, many organizations still run the majority of their critical business applications on-premises using a hybrid model, creating even more identity silos.

As a result, the coexistence of multicloud and hybrid clouds introduce an inherently distributed architecture that spans multiple platforms and identity systems. This "new normal" is transformational, not incrementally different from what came before.

Adopting a Distributed Security Model
The challenges associated with implementing security that can span multicloud and hybrid-cloud architectures is being complicated by the fact that identity has become the new security perimeter because many users are accessing apps and data from outside of the firewall. 

Initially, many organizations try to set up multicloud infrastructures manually but quickly discover that identity management efforts don't scale due to a lack of staff and expertise, which results in misconfiguration errors, slow process times, and increased costs. In addition, most organizations have significant investments in legacy systems they must maintain while migrating to new cloud infrastructures. This will require IT departments to support a mix of cloud and on-premises apps for the foreseeable future, further complicating the multicloud challenge.

Here are five steps that will lead organizations to the creation and implementation of a successful multicloud identity strategy.

Step 1: Embrace Decentralization
The best way to solve multicloud identity problems is with a distributed architecture. Orchestration software can be used to serve as a connectivity "fabric" between cloud and on-premises identity systems and unify policy management and enforcement.

Step 2: Modernize! Don't Migrate Legacy Infrastructure
Don't move messy identity silos as part of migration projects. Instead, upgrade and modernize identity capabilities with new identity-as-a-service options. This makes it possible to consolidate policies and simplify roles and groups, check for compromised credentials, lock out dormant accounts, and force users to securely reactivate their accounts.

Step 3: Unify Visibility into App and Identity Ecosystems
To effectively implement a new identity strategy, it's important to understand where existing apps and identity systems are located. What are the dependencies between each app and identity systems? What identity workflows exist today and who has access to what? Having the right tools can speed up and streamline this discovery and mapping process.

Step 4: Use Standards, Not APIs, for Integration
Avoid lock-in to proprietary systems or writing to outdated APIs when updating identity systems. Instead, use standards like SAML, OIDC, and SCIM. Rather than performing multiple 1:1 integrations, an abstraction layer can provide 1-to-any flexibility. This approach also eliminates the need to rewrite apps in order for them to interoperate with a new identity system.

Step 5: Develop a Phased Migration Plan
A complex migration is made easier by breaking it into smaller, more manageable phases. For example, grouping migrations and planning an incremental shift will minimize disruption and risk. Grouping apps in terms of their migration complexity also helps anticipate and plan for potential speed bumps during a migration, for example:

  • Complex = Cookie-based sessions and IAM SDKs
  • Medium = HTTP headers and custom attributes
  • Simple = SAML and OIDC standards-based sessions.

Review the capabilities you currently use that can be carried forward and determine what new capabilities will be needed to support the multicloud environment. There will be some level of coexistence support required until all legacy infrastructure can be decommissioned. Finally, calculate the costs that will be saved by retiring legacy infrastructure, which can be earmarked to fund other innovations.

Related Content:

 
 
 
 
Learn from industry experts in a setting that is conducive to interaction and conversation about how to prepare for that "really bad day" in cybersecurity. Click for more information and to register for this On-Demand event. 
 

Eric has made a career out of simplifying and securing enterprise identity management. He founded, scaled, and successfully exited both Securant/ClearTrust (Web Access Management) and Symplified, (the first IDaaS company). Recently Eric served as SVP and GM at Oracle, where ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5148
PUBLISHED: 2021-03-05
SonicWall SSO-agent default configuration uses NetAPI to probe the associated IP's in the network, this client probing method allows a potential attacker to capture the password hash of the privileged user and potentially forces the SSO Agent to authenticate allowing an attacker to bypass firewall a...
CVE-2020-36255
PUBLISHED: 2021-03-05
An issue was discovered in IdentityModel (aka ScottBrady.IdentityModel) before 1.3.0. The Branca implementation allows an attacker to modify and forge authentication tokens.
CVE-2019-18351
PUBLISHED: 2021-03-05
An issue was discovered in channels/chan_sip.c in Sangoma Asterisk through 13.29.1, through 16.6.1, and through 17.0.0; and Certified Asterisk through 13.21-cert4. A SIP request can be sent to Asterisk that can change a SIP peer's IP address. A REGISTER does not need to occur, and calls can be hijac...
CVE-2021-27963
PUBLISHED: 2021-03-05
SonLogger before 6.4.1 is affected by user creation with any user permissions profile (e.g., SuperAdmin). An anonymous user can send a POST request to /User/saveUser without any authentication or session header.
CVE-2021-27964
PUBLISHED: 2021-03-05
SonLogger before 6.4.1 is affected by Unauthenticated Arbitrary File Upload. An attacker can send a POST request to /Config/SaveUploadedHotspotLogoFile without any authentication or session header. There is no check for the file extension or content of the uploaded file.