Over a million developers have joined DZone.

What the Galactic Empire Could Learn From OWASP

DZone 's Guide to

What the Galactic Empire Could Learn From OWASP

Whether you're building the Death Star or defending the future of the galaxy, it's always a good time to review those OWASP top ten. Use the Force of basic security principles and avoid having any ''bad feelings'' about anything.

· Security Zone ·
Free Resource

Security is crucial for any project, whether you’re building a hobby application on the terrestrial internet or a fully operational battlestation in a galaxy far, far away. That said, security isn’t easy. Every few years, the OWASP group publishes the Top Ten list, which reviews the most common security mistakes in applications across the internet. The same few vulnerabilities have been at the top of the list for years: SQL injection, broken session management, cross-site scripting (XSS) vulnerabilities.

The details of these attacks have been well-known for over a decade, but they still top the list. Even when we know better, it’s easy to keep making the same mistakes over and over again.

These mistakes can have profound implications. Verizon’s multi-billion dollar purchase might fall apart because of Yahoo’s knack for setting records with really big data breaches. A Russian hacker claims to have breached the U.S. Election Assistance Commission because of an unpatched SQL injection flaw.

I Find Your Security Vague and Unconvincing

In the Galaxy Far, Far Away, these same types of security mistakes led directly to the data leak that doomed the Death Star. (Be warned: spoilers for Rogue One ahead.)

  • Strong authentication and session management 
    In a recommendation straight from OWASP, the stolen freighter should have never been allowed through the shield gate on Scarif with expired credentials. Whether it’s access tokens or callsigns, the ability to enter a highly secure system should be properly expired. And, when the client (or ship) presents authentication tokens through an untrusted connection, the tokens should be validated to make sure they haven’t been forged or tampered with.
  • Multifactor authentication
    At any point during or after the initial intrusion, requiring multiple types of authentication would have prevented the data breach. This is multifactor authentication in a nutshell: sometimes it’s possible to steal a password (or a freighter), but stealing a password and a second factor is much more difficult.

If these basic security principles had been followed, it would have been impossible for the  rebel scum  crew of Rogue One to leak the critical information that led to the outcome of the Battle of Yavin. (Whether that’s good or bad depends entirely on your point of view, of course.)

How to Do Security Right

If you’re building a battlestation, make sure you hire competent security professionals and don’t make the same mistake three times in a row.

If you’re building something a little closer to home, you’ll need to securely handle authentication and identity management. If you don’t want the risk of building it yourself, we can be a useful ally.

And don’t forget to review the OWASP Top Ten list, no matter how you’re building your application. Nothing less than the future of the galaxy could be at stake.

security ,security best practices ,multifactor authentication ,user authentication ,session management ,password management

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}