bandit

If you're interested in reviewing Python code for potential security issues, here's a related project: https://github.com/openstack/bandit (I'm one of the devs) It will actually pick up a number of security issues listed in the post. It's useful in real world too - led to a number of CVEs being reported.

Do a lot of reading and reviews. And then more reading. Start here: https://www.owasp.org/ Specifically the TOP 10 webapp issues may be helpful: https://www.owasp.org/index.php/OWASP_Top_Ten_Cheat_Sheet Read your framework's security guide and adjust the settings properly. (for example https://symfony.com/doc/current/security.html - every framework should have one) Scan your dependencies for known security issues (gemnasium, sensiolab/security-checker, etc). Scan your code with tools reporting security issues (like https://github.com/openstack/bandit for python, or https://github.com/HewlettPackard/gas for go). Based on OWASP make sure bad things are banned in your code - no unparametrised queries, no manual crypto, no cookies without httponly, only modern, salted hashing for passwords, etc. Reuse as much as possible from the framework, b

This article's interesting. But my biggest takeaway is the existence of Bandit [1]. It looks really neat. This "try_except_pass" check for example [2], is a great one. It might be rated "Low" severity from a security context. But from a functionality point-of-view, it's high on my list. It masks NameError among many others. You very nearly always want NameError to propagate, lest you conceal a glaring design error. [1] https://github.com/openstack/bandit [2] https://github.com/openstack/bandit/blob/430dfceca9cebd7ebe4...