Risk
2/4/2013
04:10 PM
Gunnar Peterson
Gunnar Peterson
Commentary
Connect Directly
RSS
E-Mail
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, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5316
Published: 2014-09-21
Cross-site scripting (XSS) vulnerability in Dotclear before 2.6.4 allows remote attackers to inject arbitrary web script or HTML via a crafted page.

CVE-2014-5320
Published: 2014-09-21
The Bump application for Android does not properly handle implicit intents, which allows attackers to obtain sensitive owner-name information via a crafted application.

CVE-2014-5321
Published: 2014-09-21
FileMaker Pro before 13 and Pro Advanced before 13 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-2319...

CVE-2014-5322
Published: 2014-09-21
Cross-site scripting (XSS) vulnerability in the Instant Web Publish function in FileMaker Pro before 13 and Pro Advanced before 13 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-3640.

CVE-2014-6602
Published: 2014-09-21
Microsoft Asha OS on the Microsoft Mobile Nokia Asha 501 phone 14.0.4 allows physically proximate attackers to bypass the lock-screen protection mechanism, and read or modify contact information or dial arbitrary telephone numbers, by tapping the SOS Option and then tapping the Green Call Option.

Best of the Web
Dark Reading Radio