|There's more than one way to do things|
Re^3: Web Application Security Vulnerability testingby afoken (Monsignor)
|on Nov 06, 2012 at 06:06 UTC||Need Help??|
Fortunately my company and boss know better than to trust me with actually implementing application security testing.
Nice. But make sure everyone learns that even constant security checks won't prevent a clever attacker from finding an obscure path through your system.
Once, one of my systems was tested by a well-known organisation for one of the clients. They found a problem with the login function: In a certain combination of operating system and database, it was possible to test account names for existence. So, an attacker could significantly reduce the number of combinations of names and passwords to be tested. Of course, this was not expected behaviour, and I removed that bug.
But: They did not find a way in, so they did not test anything else. The client was happy with that, the system earned its "tested by $organisation" stamp, and now it was "secure" and could be used.
It seems none of the testers even thought of calling technical support, pretending to be one of the users that (s)he found during the login tests and have the password of that account reset or revealed.
None of the testers asked for a test account to try to attack the system from the inside.
None of the testers asked for the source code.
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)