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
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2010-5312
Published: 2014-11-24
Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

CVE-2012-6662
Published: 2014-11-24
Cross-site scripting (XSS) vulnerability in the default content option in jquery.ui.tooltip.js in the Tooltip widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title attribute, which is not properly handled in the autocomplete combo box demo.

CVE-2014-1424
Published: 2014-11-24
apparmor_parser in the apparmor package before 2.8.95~2430-0ubuntu5.1 in Ubuntu 14.04 allows attackers to bypass AppArmor policies via unspecified vectors, related to a "miscompilation flaw."

CVE-2014-7817
Published: 2014-11-24
The wordexp function in GNU C Library (aka glibc) 2.21 does not enforce the WRDE_NOCMD flag, which allows context-dependent attackers to execute arbitrary commands, as demonstrated by input containing "$((`...`))".

CVE-2014-7821
Published: 2014-11-24
OpenStack Neutron before 2014.1.4 and 2014.2.x before 2014.2.1 allows remote authenticated users to cause a denial of service (crash) via a crafted dns_nameservers value in the DNS configuration.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?