25.02.2014 by Martin Kuppinger
When looking at the core IAM (Identity and Access Management) market with its main product categories of Identity Provisioning and Access Governance, some customers and vendors currently raise the question of whether there is still a need to keep these product categories separate or whether a single, combined view on these is the better choice.
Looking at the vendor landscape, some vendors such as CA Technologies or Beta Systems still have two distinct offerings. Others merged their product line from either Access Governance towards integrated Identity Provisioning, such as SailPoint did, or the other way, by adding more and more Access Governance features to Identity Provisioning products. Dell is a good example of that. Oracle, as another example, focuses on increasingly integrating its product portfolio into one suite. Aside from that, there are various vendors that, for instance, have strong Access Governance capabilities with some Identity Provisioning, but also the opportunity to still integrate well with existing Identity Provisioning solutions of other vendors. Examples for that strategy include RSA/Aveksa and CrossIdeas.
But that is only the vendor view on what is happening in the market. The more important question is: What serves the customer’s needs best? There is not a single right answer on that question.
It depends, perhaps, on where these customers are today. Customers that have already successfully deployed an Identity Provisioning solution might opt for a separate Access Governance tool for various reasons, such as reducing vendor lock-in or just because the Access Governance capabilities of their Identity Provisioning solution are not good enough. However, replacing an established Identity Provisioning tool might be too huge an effort to be considered economically feasible.
I also see many organizations, including large organizations, that want to proceed step by step and feel that they should first do the Identity Provisioning basics right. On the other hand, there are many organizations that need a rapid solution for Access Governance, without all the overhead that the technical elements of Identity Provisioning might cost.
There are various other scenarios I have described in detail in a report on Access Governance architectures. My perspective and experience is that there are varying customer requirements. While some need only Identity Provisioning (for instance to replace existing products, having Access Governance already deployed), while others need integrated solutions or only Access Governance (for rapid deployment or to integrate with existing provisioning tools).
Aside from the different customer requirements, there are pros and cons of integrated solutions. On the positive side there is that customers only need one tool and that the potential complex integration of Identity Provisioning and Access Governance is already done. On the other hand, there are scenarios where it is about integrating with existing Identity Provisioning tools. Aside from that, solutions that try to cover everything have a tendency to become more complex, while sometimes lacking the depth of features specialized solutions provide. Some vendors manage that well, while others are not as perfect.
Beyond that, there is another argument that speaks for keeping Access Governance and Identity Provisioning separate. While Access Governance focuses on business users and bridging the gap between business and IT, Identity Provisioning is far more a technical solution for interfacing with target systems. There might be different owners; there are definitely different user requirements.
These are just some of the reasons why we still keep these segments separate. We are currently updating our Leadership Compass on Identity Provisioning and will do so for the one on Access Governance. We are also working on a Leadership Compass on IAM Suites, looking at the overall IAM market well beyond Provisioning and Access Governance.
Importantly, in both our Identity Provisioning and our Access Governance Leadership Compass, we already evaluate the strength of Identity Provisioning products to support Access Governance requirements and vice versa. However, that is just one view that is kept separate, allowing customers to make their own decisions, depending on their requirements. Putting everything into one basket appears, from our perspective, to be inadequate for that complex market.
24.02.2014 by Martin Kuppinger
A while ago, I wrote about the changing market for Secure Information Sharing. I also recently published a report on Microsoft Azure RMS, one of the most important products in that market segment, and further reports will follow.
The first question is: What is Secure Information Sharing (SIS) about? It is about technologies that allow sharing information across the boundaries of an organization in a secure manner. Such technologies ensure encryption of the document both in motion and at rest. Furthermore, they apply and enforce access control, restricting access to the documents and (ideally) enforcing entitlements for editing, printing, forwarding, etc.
SIS has been a requirement of many organizations for years now, especially organizations that need to share information with a broad number of business partners and have complex supply chains. Some, such as the automotive industry, aerospace & defense, or life sciences, have been looking for such solutions for several years. In some of these industries, collaboration networks that enable SIS are established. These industries also are the ones who have been most active in demanding improved IRM (Information Rights Management) solutions.
So why do we need SIS? There are some reasons:
- Agile, connected businesses lead to new requirements for collaboration. A good example is the life sciences industry, where success and time-to-market frequently depend on efficient collaboration with various external parties. Such collaboration, especially in a competitive environment with strong regulatory requirements and tough competition, requires the ability to securely share information.
- Regulatory compliance is a strong driver for SIS. The ever-increasing requirements push the demand for SIS in various industries – again life sciences is a great example.
- The fear of organizations regarding industrial espionage also increases the demand for solutions that seamlessly protect information at rest, in motion, and in use – and that’s where SIS comes into play.
- Finally, traditional IT security such as firewalls and Data Leakage Prevention (DLP) are not sufficient to fulfill these requirements. New types of solutions are required.
From my perspective, the potential for Secure Information Sharing (SIS) technologies is based on these considerations and the fact that SIS focuses on the right perimeter. This perimeter is not the server system, it is not the end user’s device, and it is not the firewall. It is the information. Information Security, as the name implies, is about securing information – and that is what SIS does.
My next post on this topic will dive a little deeper into the strengths and weaknesses of various approaches.
21.02.2014 by Martin Kuppinger
Microsoft Rights Management Services (RMS) is a solution that might help Secure Information Sharing become a topic for the masses, at least at the enterprise level. I just recently wrote a report on the product. However, as with any Information Security technology – especially ones that are Cloud-based – there are questions about security details.
For Microsoft Azure RMS specifically, it is worthwhile to look at this post. It describes in detail how RMS protects and consumes documents. The other document worth having a look at is a whitepaper Microsoft published a while ago. That whitepaper goes (among other topics) into detail regarding two important aspects:
- The various deployment options from fully Cloud to “pretty much on premises”
- The BYOK (Bring Your Own Key) approach that allows doing a lot of things based on local HSMs (Hardware Security Modules)
These might answer some of the questions you might have concerning security and confidentiality of Microsoft RMS.
20.02.2014 by Martin Kuppinger
In my new report “Entitlement & Access Governance”, published yesterday, I introduce a new term and abbreviation: EAG for Entitlement & Access Governance. Thanks to Dave Kearns for proposing that term – I like it because it reflects what this is about.
EAG describes approaches that some vendors currently call “Data Governance,” but enhanced and extended. It is about combining fine-grained entitlement management at the system level and the cross-system Identity Provisioning and Access Governance. We see an increasing number of vendors moving in that direction, closing the gap between Identity Provisioning and Access Governance on the one hand and the system-level, detailed management of entitlements on the other.
There always has been a predetermined breaking point between the Identity Provisioning layer (and the Access Governance layer on top of Provisioning) and the system-level entitlement management. While Identity Provisioning typically works on the level of, for instance, Active Directory global groups or SAP business roles, many systems (including Active Directory and SAP) have another system-specific hierarchical entitlement structure below that level. System administrators manage these. If a system administrator changes low-level entitlements – instance.g., the ACLs of a local group that is part of a global group – the Identity Provisioning system will not recognize that, at least not in most common deployments today. It will also become too complex to manage everything top-down, so there is a reason for system-level solutions.
EAG balances these requirements, by centralizing functions such as request and approval while leaving system-specific tasks local. I expect EAG to become the next big evolutionary step in core IAM, with some preliminary solutions already out there.
14.02.2014 by Martin Kuppinger
NIST (the US National Institute of Standards and Technology) has now released the final version of their Cybersecurity Framework for Critical Infrastructures. As requested, this is not a set of new regulations or fundamentally new concepts for security, but, to quote my colleague Prof. Dr. Sachar Paulus, a “well-written summary document incorporating different approaches (lifecycle views, maturity views, communication aspects, risk posture analysis…) that helps getting an operational grasp on the necessary activities, and therefore well-suited as a guideline or education piece for technicians / practitioners. It is by no means sufficient (nor meant) to replace an ISMS (Information Security Management System). So: good that it exists, but in essence nothing new.”
However, it is very likely that it will lead, in consequence, to new regulations. Sector-specific agencies are obliged to engage in a consultative process with various governmental agencies to determine whether current regulations are sufficient for the critical infrastructures sector. This in consequence most likely will lead to new regulations.
When looking at the framework and its Appendix A, the fact that there is nothing really new in this framework becomes obvious. That leads to a simple bit of advice: follow common good practices and standards such as ISO 27001:2013 and CoBIT 5. If there will be a need for new regulations in future, this will happen because too many organizations in critical infrastructures do not follow established good practices.
10.02.2014 by Martin Kuppinger
It is a common scenario in organizations that the marketing department, business development, or the sales department asks the IT department to support social logins on some of the corporate websites, including eCommerce sites. Admittedly, IT also sometimes proposes such functionality, having technology on hand that allows for simple integration of such social logins.
My colleagues and I have written about that topic before, primarily from an information security standpoint and as part of the BYOI (Bring Your Own Identity) theme. The main reason for social logins is that users want a simple way to login to applications. Social logins are convenient, but limited in their identity assurance.
However, there is another aspect of social logins I have not seen discussed so far, neither by IT nor by marketing people. It is about customer relationships, confidentiality, and competitive advantage.
So let us have a look at what happens when using social logins. Let us assume that there is a customer C that wants to access the eCommerce website E. He might use a social login, maybe using social network F or G. There might be an advertising service A as well in the game and another business B, which as well relies on social logins or works with that advertising service. Finally, there are other websites, let us call them D so that we have all letters A to G in that example.
C logs into F (in fact, he remains logged in there). C accesses E. When he does that, he has the social login and BYOI experience. However, at that time F learns that C is a customer of E. F uses, as part of its business model, that information to provide information to an advertising service A (depending on the social network, that might be its own or an external one). B relies on that service as well. Thus, when C starts looking at other websites (D) that also might work with A, he might see adverts for goods related to his interests – adverts of business E or business B. Even more information might flow, being available in F because C has left a comment somewhere or – as part of today’s or tomorrow’s business models – being sold by A or F to the competitor B.
This theoretical example shows that supporting social logins could be an excellent way to inform competitors about the interests of customers. Does this really make sense from a marketing perspective?
In essence, social logins obviously are not what marketing should request. But what are the alternatives for BYOI? FIDO Alliance, which we covered several times in our posts, might become a game changer in that area. They are not an IdP, but they support the flexible use of strong authentication methods. Combined for instance with integrated strong authentication in devices such as fingerprint readers in mobile devices, this is a way for users to easily register to websites with strong authentication, without relying on a social login. However, the FIDO Alliance does not provide the user’s attributes in a way social networks can do. Some of the authenticators could, other IdPs (Identity Providers) could also, based on a strong yet simple authentication.
BYOI is not about social logins only. It is about enabling the user to use their “own” identity – a preferred one, chosen by him – with various relying parties (RPs). From a marketing perspective, it might be well worth while to evaluate the alternatives to social logins when requesting support for BYOI.
Learn more about the challenges of social logins in our webinar next week (in German language): “Marketing will das Facebook-Login. Und was ist mit der Informationssicherheit?”
06.02.2014 by Martin Kuppinger
Recently, there have been various articles on the NSA and GCHQ (Britain’s Government Communications Headquarter) collecting date from “leaky apps”, including data from Angry Birds, Google Maps, Facebook, Flickr, or Twitter.
Look at another story in that context: There have been extensions to Google’s Chrome browser that have started to spam users with advertisements. What happened? Advertisement companies acquired the extensions and used them in a way unintended by the original developers. Once installed, there is no control over what extensions are allowed to do or not. The extensions are updated automatically. How simple would it be for criminals or for national intelligence services to do the same? Clearly, they would not push spam, but pull information.
Back to the apps (by the way, the same applies to the traditional web counterparts of these services, if there are ones)… The combination of a lack of security and the excessive collection of data about users and their behavior is what we would call a “gefundenes Fressen” in German. A ready-to-serve meal for the NSA.
Simply said: NSA and the others just piggyback on these services. Without companies such as Facebook, Google, or Apple, NSA would have a much harder play. The Reform Government Surveillance Alliance, driven by AOL, Apple, Facebook, Google, LinkedIn, Microsoft, Twitter, and Yahoo, probably is the most hypocritical alliance these days. Why did Apple not implement more user control of the collection of data by apps from the very beginning? Less data would have been available to the NSA. Instead of doing that, they removed apps helping the user in controlling app behavior from their appstore. Why did Twitter, Facebook et al not encrypt traffic from the very beginning? Some of the service providers do now, but most started far too late. NSA then still could have requested access to data, but it would have made the life and work of intelligence services tougher.
With more user control, more user consent, more built-in security, and options for the user to choose between free services (paid in the “privacy” currency) and paid services that ensure privacy, this situation would change. Yes, the companies would have to re-think their business models. But that is what will happen anyway, after Edward Snowden has opened the Pandora’s Box. Attention is still mainly on the behavior of intelligence services. But that will inevitably change.
When talking about hypocritical behavior, there are others to blame as well. The users that naively assume that there is such a thing as a free lunch when using free services on the Internet. There isn’t. If you know and accept this, fine. But then you shouldn’t blame the NSA for using that data as well.
However, my favorite example of hypocritical behavior is another one. My daily newspaper – and yes, I still read a print newspaper – is the local “Stuttgarter Zeitung”. Recently, they devoted the entire page 2 to the loss of privacy on the Internet. On the other hand, a few days ago they applauded themselves for having passed the number of 5,000 (or so) Facebook friends for their online presence. They have a Facebook plug-in on the website of their online edition. They support registering for commenting on articles in the online edition based on your Facebook account. Isn’t that the perfect example of hypocritical behavior: on one hand letting Facebook collect more data and on the other bashing on them?
It’s the decision each of us must make, which currency he wants to use to pay for services. However, we should have a choice. And the ones who are the enablers for the NSA collecting masses of data shouldn’t blame NSA – NSA just piggybacks on their business model. They could change this, starting with encryption of traffic and collecting only the minimum of required information, and ending with providing alternatives to “paying in the currency of privacy”. But we should end this hypocrisy. Bruce Schneier recently published two interesting articles that fit in the context here and here.
04.02.2014 by Martin Kuppinger
A recent discussion in the “Identity Management Specialists Group” on LinkedIn had the title “On point. Agree. Gartner says attributes are the new role for identity?”
I wondered a little about a rather old discussion appearing again. In fact, there rarely has been pure role-based access control. On the other hand, roles are one of the most important, if not the single most important attribute in attribute-based access control. There is no conflict, but we are just looking at the natural evolution.
I commented on another of these discussions nearly two years ago in another post. If you want more detail, have a look at the podcast recording of the KuppingerCole Webinar “Enterprise Role Management Done Right: Build the Bridge between Business and IT”.
We clearly will need some kind of abstraction – we might call that roles or something else. But clearly, the discussion about “attributes instead of roles” is an artificial one, miles away from practical experience and use cases.
19.12.2013 by Martin Kuppinger
On Monday this week, we have published the KuppingerCole Predictions and Recommendations for 2014. They differ from other publications of people looking into the crystal ball in one important aspect: we not only provide our predictions, but also recommendations. More on that below.
Information Security is in constant flux. With the changing threat landscape, as well as a steady stream of innovations, demand for Information Security solutions is both growing and re-focusing. Based on new offerings and changing demand, KuppingerCole predicts several major changes in the Information Security market. KuppingerCole specifically identified the following areas where we see massive change in 2014:
- Software Defined Networking (SDN) – Software Defined Computing Infrastructures (SDCI)
- Integrated Real-time Network Security Analytics
- Cloud IAM (Identity and Access Management)
- Digital, Smart Manufacturing & Smart Infrastructure: ICS & SCADA
- API Economy
- IoEE (Internet of Everything and Everyone)
- BYOI (Bring Your Own Identity) and Biometric Authentication
- Big Data
- Cloud Service Provider Selection and Assurance
- Ubiquitous Encryption
The document provides both predictions and recommendations. The latter focus on how organizations should react to the changes we predict. It is not always best to jump on every trend and hype – in many cases, it is about defining strategies first and performing organizational changes before starting to implement new types of technologies. Do not rely on predictions only.
Have a look at our document. The best place to learn more about these topics is the upcoming European Identity and Cloud Conference (EIC) 2014, Munich, May 13th to 16th. And don’t miss all our current and upcoming research on these topics.
13.12.2013 by Martin Kuppinger
I have read many predictions recently that SDN (Software Defined Networking) is the next big thing in IT. Wrong. It is not. It is just a small piece in a bigger story. And just looking at SDN is not sufficient.
The next big thing is SDCI – Software Defined Computing Infrastructure. This is about “software-defining” everything. Hardware virtualization – “software defining hardware”, so to speak – is a reality. Software Defined Storage is becoming increasingly popular. SDN is another element. A number of vendors, such as VMware, talk about a Software Defined Cloud Datacenter. I don’t like that term, because the “Cloud” element might be nice from a marketing perspective, but tends to narrow things down to a specific form of Computing Infrastructure. So I will use SDCI for now.
When looking at SDCI versus SDN, claiming that SDN is the next big thing is like inventing a locomotive but no rail infrastructure. It is only about solving a portion of the problem, from a technical, network-centric view.
However, SDCI is far more than that. It is about managing how business services are operated on a flexible computing infrastructure, which must include all elements of this infrastructure. It is about defining the policies for the entire infrastructure. This is an interesting challenge, because it is not about network, storage or other technical policies anymore, but about translating the business policies. Regulatory compliance, security requirements, availability, performance, but also the willingness of business to pay for a certain level of service – all that flows into policies that define how infrastructure is used and how to balance various requirements.
SDCI also will revolutionize security, in particular network security. In dynamic environments, there is no place for traditional firewalls anymore, but there are fantastic new opportunities for securing information. Such infrastructures allow us to manage security consistently across “machines”, storage, and network, in the context of business policies and in the context of identities. Instead of having multiple disparate approaches to security – a little bit of firewall here, a little bit of endpoint security here, some IAM there, etc. – we are heading towards integrated security. This integrated security still can be layered, but it will be layered in an integrated manner, unlike “layered” security today, which means using multiple levels of disparate security where no one really knows how good the combined result really is – just because there is no integration, no consistent view, no consistent policies.
The security aspect is another reason why SDNs for themselves are not what we need. SDNs are about continuing segregation. They allow us to repeat mistakes on a higher level. SDCI allows us to do things better. That’s the reason why SDCI is the next big thing – and it will become a real big thing.