We’d like to thank our special “guest” assistant and end user sources for help on this blog.
SSO Becoming a Key Security Convergence Component. With chief security officers at enterprises finding that physical security and IT infrastructure becoming more and more complex and harder for individual departments to manage, so-called “Single-sign On” (SSO) has become a hot topic in the IT world, leaking out to the physical world, as well. Just like video analytics, SSO is not a new notion, nor has it been immune like video analytics from hype and subsequent end user disappointment. However, the growth of SSO use among end users who accept what it can and cannot do, (similar to the growth of video analytics), based on more realistic notions of what it can an cannot do, has created a much more accepting user community for the technology. This is an important take-away as we begin to look at the market, the companies providing SSO solutions, and the possibility of who might want to team up with, or even acquire the better SSO providers. We would reiterate, while we don’t ultimately view SSO as a “industry” unto itself, we see it as one of the very key components for end users in the move toward convergence between physical and logical security.
Compliance, Efficiency, Security and Total Cost of Ownership. Not only can single-sign on help an organization in regulatory compliance (i.e., HIPAA and SOX) but it can also lower the total cost of ownership (TCO) of the security systems infrastructure being considered for upgrade or new installation. For those that are just getting up to speed on this, SSO is a method of authentication which allows a user at the enterprise to log on to the security infrastructure once (primarily IT today, but becoming increasingly converged with physical systems) and gain access to multiple security systems without being prompted multiple times to “log on.” By logging into the infrastructure once, the individual systems can take the infrastructure authentication and automatically apply it to their own individual authentication systems.
SSO environment can benefit a CSO along with their IT and physical security departments in many ways. It can limit the complexity of the user provisioning process, if user information is stored in a single central area. IT Departments will have more time to focus on pressing and high risk issues – for inst, as having an SSO can limit the number of help desk calls. (User: “Hello, I’ve forgotten my password to XYZ application”). This in turn can reduce IT costs. Additionally, (which is everyone’s favorite benefit) having an SSO will significantly decrease the amount of passwords a user is required to remember.
More benefits to SSO include Compliance Reporting – If all user data is in a central place, I can get a single report from the SSO environment rather than having to get one from each individual application. This, in turn, reduces end-user time as they don’t need to log on every time.
Another important aspect of SSO is the “push” it gives to the convergence of logical and physical security environments. Many SSO software packages allow for physical and logical security to work seamlessly together. When a user’s access is terminated in the SSO environment, their physical access card can be automatically disabled, as well.
The ROI Issue. A recent end-user study by Spire Security LLC, found that SSO generated ROI by (1) substantial reduced costs and improved efficiencies on existing accounts, (2) reduced costs on new and departing employee account management.
The Hurdles that Have Prevented Major SSO installations up until now.
So why hasn’t an obvious benefit to convergence been implemented en masse up until now? The biggest and most obvious bugaboo for SSO is security. Primary among them is authentication. SSO environments must incorporate some sort of strong authentication mechanism. Without strong authentication mechanisms, risk of a security breach might be increased exponentially. For instance, if strong password settings are not established in the SSO system, a ‘hacker’ who discovers the IT administrator password could possible have a ‘key to the kingdom” and gain high-level access to not just the security system, but theoretically nearly all of IT systems. This is why from a CSO’s point of view, reference-site based proof of strong authentication is so important. By implementing authentication mechanisms, such as smart cards, RSA key fobs, and biometrics, these risks to giving up the “keys” can be minimized. The mechanisms for doing this are beyond the scope of this blog, but are certainly available from numerous consultants, ranging from individual practitioners like Steve Hunt to giant consultants, like KPMG.
One of the responses to the “keys to the kingdom” argument has been that SSO providers also provide much stronger password protection protocols, including eliminating common password selections, and various means to permanently prevent users from writing down passwords. The mere fact that end users can focus on one password, one sign on , can eliminate the common passwords and ID’s that come from user-password overload.
Complexity. In addition to the risks – and partially because of them, SSO environments are becoming increasingly complex and complicated to set up. Typically organizations do not have a homogeneous IT infrastructure, and probably and even more piecemeal physical security infrastructure. My former organization is a true leader in attempting to integrate logical and physical security, and yet that is a task that is far from completed. An organization may employ multiple applications, on multiple types of environments with multiple security settings and parameters for both physical and logical security. We have found in talking to end users that too many IT departments still treat each of these environments as silos and may lack the understanding on how to incorporate authentication technology between them – and this is before even tackling the physical/logical convergence issue.
Conclusion: Despite the continued challenges of complexity and security facing end users implementing single sign-on, we believe we are now at a level of maturity, integration, and end user acceptance that we have not seen before. We think after hearing about it for a decade, and watching large numbers of venture and private equity investors waiting (…and waiting) for returns on their investment, the time for this segment appears to be arriving. We would not be surprised to see a wave of joint ventures and industry consolidation.
Here is a short list of companies that offer SSO, along with their leading investors:
Private Companies and their Major Investors:
Imprivata: (SAP Ventures, Polaris Venture Partners, Highland Capital Partners
Sentillion: (HealthCare Specific): Merrill Lynch Investors, Dresdner Kleinwort Capital,
First Consulting Group, Intersouth Partners, Newbury Ventures
Passlogix: Hanseatic Corp., Union Square Ventures
Enterasys: Gores Group LLC, Tennenbaum Capital Partners
Courion: Questmark Partners, Riggs Capital, JMI Equity
Shibboleth: Internet2 Middleware Initiative, under the National Science Foundation
MetaPass: Sunnyvale, CA
Atlassian : Sydney, Australia
Public Company:
ActivIdentity (ACTI)
Divisions of Larger Public Companies:
Microsoft (Identity and Access Management Series)
CA (Identity & Access Management Solution)
Hitachi ID Systems
Novell
Oracle
SAP