Risk
2/21/2013
07:17 PM
50%
50%

Is Single Sign-On A Security Tool?

SSO has largely been delegated in the eyes of infosec pros as a tool of convenience, but a survey shows IT increasingly viewing it as a security lever

Single sign-on (SSO) technology may have been primarily perceived as a tool of expediency in the past, but if results from a survey out today hold true, things have changed.

IT professionals are reporting that security trumps ease-of-use and operational convenience as the top motive behind SSO deployments today. But security experts warn that in order to achieve that security objective, organizations need to shore up the authentication and access control processes that power SSO front-end technology, while establishing a secure means to bridging identities between on-premises and cloud applications.

[Are your misconceptions coloring how you view SSO? See Single Sign-On Mythbusting.]

"Over the last few years, SSO has really been more about convenience -- organizations were really looking to basically ease the burden of having all these different applications that their employees need to access," says Brian Czarny, vice president of marketing for Symplified. "That's really flipped around, whereby these organizations say it's about security and really wanting to look at how they can regain more visibility and control over these applications."

In a survey conducted on behalf of Symplified by Qualtrics, 70 percent of the 200 IT decision makers questioned reported security as a motive for deploying SSO. That's compared to just 51 percent who named IT resource reduction, and 49 percent who cited user convenience as motives.

But done poorly, SSO deployments can actually make environments less secure and more susceptible to breaches, warns Deepak Taneja, CTO and founder of Aveksa.

"For example, if the sign-on entry point is breached, then the security of multiple applications and data resources associated with the SSO is at risk," Taneja says. "SSO combined with strong access controls for joiners, movers, and leavers within an organization fulfills the promise of both convenience and security."

According to Jim Hietala, vice president of security at The Open Group, SSO deployments require organizations to look closer at authentication and other end-point security controls.

"Improvements to security should be strongly considered along with any move to SSO," Hietala says, suggesting that multifactor authentication should be a part of the SSO discussion. "This is because SSO can reduce security by concentrating knowledge needed to access lots of applications into a single point of failure."

Part of SSO's bad rap is the fact that the term has become gummed up in the marketing works, so one person's SSO may be another person's simple password synchronization. One of the first steps toward using SSO as a security tool is making sure that the right mix of capabilities make it onto the acquisition short list.

"Some IT professionals label the process of synchronization of username and password across applications as single sign-on, meaning there is one username and password that is synchronized across applications. This view is a relic of the early years of distributed computing before true SSO solutions arrived on the market," says Kent Purdy, solution marketing manager for NetIQ. "When used properly, SSO increases security by enabling more complex authentication policies, randomizing passwords, [and] enabling reauthentication within an application as needed."

According to Symplified's Czarny, one of the biggest hurdles to establishing more advanced functionality across the application infrastructure is the opacity of authentication into cloud-based applications.

"In particular, with the growth of cloud-based applications, they're doing SSO to help with the convenience of authenticating users into those applications using their existing identity infrastructure, but they're really lacking the visibility of what users are really doing within those apps today," Czarny says.

The Symplified survey results show that only 37 percent of organizations had visibility into cloud-based applications through their current IAM and SSO infrastructure.

"That's where they're seeing a lot of deficiency in the existing legacy IAM products," he says. "They do a really good job with things like entitlements or hooking into some of the core legacy enterprise on-premise applications, but don't do a good job extending out through cloud-based applications."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

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-2014-7830
Published: 2014-11-24
Cross-site scripting (XSS) vulnerability in mod/feedback/mapcourse.php in the Feedback module in Moodle through 2.4.11, 2.5.x before 2.5.9, 2.6.x before 2.6.6, and 2.7.x before 2.7.3 allows remote authenticated users to inject arbitrary web script or HTML by leveraging the mod/feedback:mapcourse cap...

CVE-2014-7831
Published: 2014-11-24
lib/classes/grades_external.php in Moodle 2.7.x before 2.7.3 does not consider the moodle/grade:viewhidden capability before displaying hidden grades, which allows remote authenticated users to obtain sensitive information by leveraging the student role to access the get_grades web service.

CVE-2014-7832
Published: 2014-11-24
mod/lti/launch.php in the LTI module in Moodle through 2.4.11, 2.5.x before 2.5.9, 2.6.x before 2.6.6, and 2.7.x before 2.7.3 performs access control at the course level rather than at the activity level, which allows remote authenticated users to bypass the mod/lti:view capability requirement by vi...

CVE-2014-7833
Published: 2014-11-24
mod/data/edit.php in Moodle through 2.4.11, 2.5.x before 2.5.9, 2.6.x before 2.6.6, and 2.7.x before 2.7.3 sets a certain group ID to zero upon a database-entry change, which allows remote authenticated users to obtain sensitive information by accessing the database after an edit by a teacher.

CVE-2014-7834
Published: 2014-11-24
mod/forum/externallib.php in Moodle 2.6.x before 2.6.6 and 2.7.x before 2.7.3 does not verify group permissions, which allows remote authenticated users to access a forum via the forum_get_discussions web service.

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?