3 ms·
Sadly, yes :-( At this point I'm nearly an old man yelling at a cloud, but anytime a junior engineer starts I try to go over a handful of basic security things
by freedomben 4y ago
Sadly, yes :-(
At this point I'm nearly an old man yelling at a cloud, but anytime a junior engineer starts I try to go over a handful of basic security things. Seems that most people coming out of school are aware of SQL injection and XSS, but the concept of client-side security is no security is not sinking in, even after it's been explained.
I've spent a lot of time trying to figure out why, and the best I can come up with is that they just think something like the following myths:
* Nobody would ever do that.
* Nobody would ever hit the API directly.
* It would be too hard to do that for somebody who isn't the developer.
* The need for an auth token would make it impossible to hit it with curl or another client.
* Nobody can change the client code because it's obfuscated and unreadable for humans.
Doing it on the server side is harder and a pain in the ass, so there's a lot of incentive to do it on the client and not worry about the server. It particularly doesn't help that as an industry now we're obsessed with speed and quality be damned. We can always fix it/do it right later (spoiler alert: you never do and you never have time because there will always be important new features that are high priority).
- BeefWellington 4y agoThere's a bigger problem in that schools are doing a terrible job of teaching programmers proper development practices. If you're lucky, as a student, your school might have an add-on course for secure development. The problem is, secure development practices shouldn't be an afterthought but rather a baked-in core philosophy.
- Kalium 4y agoI think the simplest explanation is that it doesn't occur to many developers that if they can develop a client, someone else can too.