Blog

Evolution of Authentication Since the inception of authentication, password has served as the foundation to provide secure login to protected resources. As time went on, password breach got easy and it continues to grow easier daily. As a result, businesses started pushing for complex password requirements, which makes it challenging for consumers to generate and […]

So you continuously build and deploy your software. You might even have some security scanning integrated in your CI/CD pipelines that checks the libraries you use for vulnerabilities. But what’s the use of that scanning when your application is not being deployed frequently? And your container images? What about vulnerabilities in libraries that are used by vendor-delivered software that you use?

As you may know when you’re working in Tech (like me) you are probably at least somewhat familiar with the high failure rate of big tech projects and the most important reasons why. Since I’ve had the privilege of being the project manager of a very large and SUCCESSFUL (boasting a bit, sorry) tech project – implementing Customer Single Sign On (SSO – the means by which you can use one login for multiple apps / services) in a very large organization – I’d like to share a few learnings and potentially speed up the journey of others.