Risk
2/4/2013
04:10 PM
Gunnar Peterson
Gunnar Peterson
Commentary
50%
50%

Is SCIM The Shim You Have Been Looking For?

SCIM is designed to solve common, real-world scenarios while managing users across cloud and enterprise domains, but incentives will drive its success

The recent announcement that Ross Anderson's "Security Engineering" book is available for free is great. This book is top-tier and a must-read for any infosec pro. One of the things I learned from Anderson's work is that security isn't just policies, mechanisms, and assurance. Incentives matter a lot, too.

Security engineering is a lot about finding the right standards. Today this often means handicapping the probabilities as to which standards will gain widespread adoption, as SAML has, or lie dormant, as SPML has. It matters a lot because designing for industry standards is an extra step that pays off only if the standard gets taken up by a broad community.

Analyzing standards has a lot to do with understanding the use cases the standard is trying to solve, the strength and review of the security mechanisms, and how it can be integrated. But trying to surmise how well adopted it will be, especially now, means understanding the incentives as to who might use it.

To say there has been a flurry of work in identity standards during the past decade might be the understatement of, well, the decade. But of all these identity standards, there has been precious little in provisioning (a gap that the provisioning vendors are happy to feast on with high six- and seven-figure projects), but with the progress SCIM is making this may be changing.

On a technical level, SCIM is a REST API for user management across domains. The standard defines account provisioning events and triggers, user and group schemas, and mapping layers. The ability to push and pull accounts to/from enterprise and cloud apps is a problem that the industry has dealt with for a long time; standards (as opposed to ad-hoc projects) are very welcome here.

But whether SCIM gets broad adoption is less about how its API works and probably more about how it aligns incentives for ecosystem participants. This is where I think it looks pretty compelling. The enterprise couldn't care less about provisioning in and of itself. It cares about having an authoritative source, that it's consistent, and that it's auditable. The simplest way to achieve this is the main goal.

For the enterprise using cloud apps, it also cares that it can publish user and group data. SCIM helps here, and so it also helps the cloud vendors that want to onboard as many users as quickly as possible.

If SCIM progresses, then where this leaves traditional IAM suite vendors is anybody's guess. I expect it means that the provisioning systems will continue to evolve more into business process automation, such as offering more just-in-time provisioning where user data is pulled in and assembled as needed based on event types. But the incentives will play a role alongside the technology and policy pieces.

Gunnar Peterson is a Managing Principal at Arctec Group Gunnar Peterson (@oneraindrop) works on AppSec - Cloud, Mobile and Identity. He maintains a blog at http://1raindrop.typepad.com. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.