News for hackers. Stuff that matters.
Re:Uber Database Breach Exposed Information of 50,000 Driver... by Rapzid on Saturday February 28, 2015 @02:21AM (#9123061)
Only you can prevent forest fires. The aggregate knowledge and concern for security needs to increase. A lot of these security auditors(but not all!) are just running automated tools and generating automated reports. They don't understand your environment like you do. Even a dedicated security guy at a large company can't be everywhere and doesn't know everything(or even understand, say, hypervisor security). I was lucky enough to work with/for somebody that was very security concious and involved in the security scene... It changes your thinking. This thinking while staying pragmatic is the key IMHO. Just like the mantra "everyone is responsible for quality" I believe everyone should be responsible for security. If this isn't specific enough well.. Consider some of the hacks mentioned before. It is at the same time completely obvious to some people what went wrong in hindsight, but obviously not apparent to the implementers that it could go wrong at the time. A cultural shift in thinking and better education in security is the way forward IMHO.
Re:Uber Database Breach Exposed Information of 50,000 Driver... by xerphn on Saturday February 28, 2015 @03:40AM (#9123189)
A lot of these security auditors(but not all!) are just running automated tools and generating automated reports.

Woah... A professional security auditor actually knows what to look for and would be flexible enough to understand (and manipulate) what your software is doing. If you are paying someone to run a script, you're not getting your money's worth.

Even a dedicated security guy at a large company can't be everywhere and doesn't know everything(or even understand, say, hypervisor security).

True, that's why ideally you'd want a team of people on this, not just one security guy to carry the globe.

I agree though, security needs to be thought out from the beginning and throughout the development process. The later you catch something, the harder it is to fix. But you need a fair amount of experience as a developer to see security issues thoroughly (because you often need to understand the platforms you are building on, not just your domain). So if you don't have that knowledge you can either teach yourself or if you don't have the time, let someone else do it.

Having a thorough understanding of what you are actually doing does take care of most of that. I doubt that's where a startup's priorities are, sadly. For most, speed > solid code