Common site vulnerablities and how to prevent them during development of a website for a client?

  • 3
    Validate all inputs. Validate stuff on server. Don't use technology that isn't maintained security wise.
  • 1
    XSS, html escape everything while storing or presenting.. validate all forms .. read the owasp guide to prevent such things.. pretty much standard if you are using any good framework which takes care of this for you.
  • 4
    why are your rants homework questions? -.-
  • 0
    Just using Dev rant for what it is meant to used.
  • 3
    Don't rely on client side validation, easy to bypass, if you want some client side validation as someone fills a form out, make sure you check when it gets to the server as well.
  • 1
    sql injection (similar attacks are possible with meteor/mongo if you don't check params to methods)
    shit password storage algorithms (try not to roll your own authentication in general)
    shit admin passwords
    not enforcing ssl (more a problem for the users)
    script injection
    exposing secret api keys
    no or wide-open spf/dkim/dmarc policies, enabling phishing
    server admin stuff
  • 2
    Hiring developers who can use google
  • 2
    Never trust client.
  • 1
    Hit at least staging, if possible Dev too, with w3af, zap or something similar. Don't go to production while it still finds something... That won't replace a proper pentest, but the absolutely basic and obvious security issues will be identified.
Your Job Suck?
Get a Better Job
Add Comment