DEV Community

Discussion on: Cryptographically protecting your SPA

Collapse
 
kbirgerdev profile image
Kirill Birger

You pretty much took the words out of my mouth. It seems like all that was really necessary was to fix the APIs that were improperly secured.

Collapse
 
matpk profile image
Matheus Adorni Dardenne

The problem is that "fix the APIs that were improperly secured" doesn't mean much. Sure, we fixed that endpoint and a couple of others after that, but we can't opperate in damage-control mode. We don't know all the insecurities that we don't know, and this is why we called the ethical hackers in the first place.

They're the experts and pointed out that this was a common vector of attack and a critical issue that needed to be fixed, I am just the developer who was tasked with fixing it. They said that being able to easily explore and modify the UI leads to security breaches in minutes, because it is very easy to overlook use-cases that "should" never happen.

Now automated "fuzzing" seems to be a good thing to implement and continuously improve upon, but the issue was critical, now it is solved, and we can implement fuzzing without fear of an attacker breaking our application in minutes.