,
9 tweets,
1 min read
Read on Twitter
Next up at #NDCOslo is "making the most of security tests" by Paweł Krzywicki 
White box - secure code reviews
Black box - penetration testing, look at system interfaces, use fuzzing tools etc
Red team - simulate a threat actor
Black box - penetration testing, look at system interfaces, use fuzzing tools etc
Red team - simulate a threat actor
Risk = severity * likelihood * detection difficulty
Red team might not start from outside - maybe a workstation is already compromised
Disassemble client executable to identify endpoints
Gradually build up knowledge of what we can do in the application based on investigation and educated guesses
Red team has to think like an attacker - don't leave a trail that could lead to the attack being discovered
Breach, but don't break
Cheap to fix issues in design and development. More expensive to carry out penetration testing and even more expensive to run red team attacks
