The customer identity space is in a dynamic phase, with lots of activity around mergers and acquisitions (M&A) and investment. One notable event was the SAP acquisition of Gigya in late 2017. Now that a year has gone by, existing Gigya contracts are ending. Engineers are probably thinking that everything’s fine and that not much has changed with their customer identity solution. But as a leader, you should be worried. The Gigya technology may not have changed (yet) but the company that delivers it has changed significantly.
Whatever the cause of the breach, the fact that it flew under the radar for so long tells me that securing customer accounts was not the number one priority for Marriott’s board and CEO. Now they’re also facing down a security mess caused by their own negligence. So what must companies do to avoid data breaches like Marriott’s?
Login methods may come and go, but customer identity is here to stay. In the aftermath of two massive data exposures at Facebook and Google+ that were amplified by social login, I want to talk about the implications for B2C enterprises. Are the privacy and security risks of social login still worth the convenience? And what steps should companies take to protect customer data and maintain public trust? Let’s start with some history.
Today, I’m very excited to announce that LoginRadius has raised $17 million Series A funding, led by ForgePoint Capital and Microsoft’s venture fund, M12. In connection with the funding, both companies will also be joining our board to further our partnership, product and innovation cycles.