The Security Issue That Killed a Financial Product Launch - Nicola Sedgwick
Security issues can be identified using the stock-and-trade critical thinking skills of a tester.
Some time ago I had the pleasure of taking part in a security bug hunt for a new financial product. This was a product ready to go to market, a product that had passed all penetration tests and was now being handed to a crowd of external testers for a final attempt to 'hack' the product.
Against all their confidence I was able to 'hack' that product and use funds to which I should not have had access. However, once I reported the vulnerability, I wasn't believed and I was asked to repeat the 'hack' multiple times until the 'experts' believed I was achieving what I was reporting - they simply couldn't believe that their penetration test result was wrong.
Like many security talks I will tell you all about the tool I used to perform this 'hack'; Unlike many security talks this is not a tool you can install, rent or purchase - because it's my brain, but your brain is capable of doing the same.
- security issues can be identified by all team members not just security experts
- critical thinking and the human brain are amazing tools for finding security issues
- security testing should take place throughout development and not just pre-release
8 Bit Pro - A Gamer's Guide to Testing - Dan Billing00:36:23
Navigating Without a Map: A Software Tester’s Journey in VR Hardware Development - Nick Pass00:36:44
The Testing Game - Mike Talks00:28:03
Compliance is Dead, Long Live Compliance - Mrinal Mukherjee00:27:48
Visual Testing: More than Just a Pretty Face - Angie Jones00:25:18
99 Second Talks - TestBash Australia 201900:20:32