White Paper: Five Reasons Why SSO Projects Fail
By completing this form you are opting into emails from Secon Cyber. You can unsubscribe at any time.
Identity is the fundamental security control in the multi-perimeter Enterprise world. Verizon’s Data Breach Investigations Report recently found that 81% of hacking-related data breaches leveraged were either stolen, weak, or default passwords. This is putting identity firmly at the heart of data breach risk. Identity sprawl and outdated password policies that expect end-user self-policing and rely on their ability to create strong, unique passwords and maintain best practices every day are leaving organisations exposed. Norton reported that in the first half of 2019, there was an increase of 58% in data breaches with some 3,800 publicly reported and around 4.1 billion records exposed.
Now, with Single Sign-On solutions that work with all application types, including Windows desktop apps and virtualised apps, there is the ability to truly cover all application types with centralised identity. A well-executed Single Sign-On (SSO) strategy: mitigates the risk of credential-based attack vectors and insider threat; eliminates password-related reset costs and downtime; improves user experience, authentication processes; and puts the organisation firmly in control of user access.
Norton reported that in the first half of 2019, there was an increase of 58% in data breaches.
However, there are many expensive pitfalls in the journey from SSO as a concept to a successful SSO implementation. Challenges as a result of identity sprawl, an evolving technology & corporate roadmap, scalability and integration complexity can result in these expensive failures.
This paper summarises the main SSO pitfalls to be aware of and the actions you can take to mitigate these.