Your application written in C and C++ is tested functionally, so you are done, right? But did you consider feeding in incorrect values? 16Gbs of data? A null? An apostrophe? Negative numbers, or specifically -2^32? Because that's what the bad guys will do – and the list is far from complete.Testing for security needs a remarkable software security expertise and a healthy level of paranoia, and this is what this course provides: a strong emotional engagement by lots of hands on labs and stories from real life.A special focus is given to finding all discussed issues during testing, and an overview is provided on security testing methodology, techniques and tools.So that you are prepared for the forces of the dark side.So that nothing unexpected happens.Nothing.
C/C++ developers and testers
General C/C++ development
Consequences of insecure software
Categorization of bugs
Assembly basics and calling conventions
Memory management vulnerabilities
Best practices and some typical mistakes