It’s a fair point raised about the Disney compromise, and quite rightly I was picked up on credential stuffing as a vector last week.

← Back to Blog

It’s a fair point raised about the Disney compromise, and quite rightly I was picked up on credential stuffing as a vector last week. It raises a few questions on where does cyber testing sit within the Software Development Life Cycle (SDLC). With so many compromised UserIDs and passwords floating around, how do you test for amongst other things threats like credential stuffing. With seemingly legitimate IDs and Passwords used to authenticate users.

We are moving more and more into a place where Multi-Factor Authentication (MFA) is going to be the norm. Where an assessment of the risks of service integration is performed and security layered appropriately. Requiring some lateral thinking from product owners, marketing, customer services, developers and testers.

Disney may not be a hack, which is good news. But it may yet expose an issue which all digital services face; with so many credentials out there, who really is a legitimate user at the end of the metaphoric cable?

View Original Post
https://www.linkedin.com/feed/update/urn%3Ali%3Ashare%3A6603568739378094080