Security analysis is uses framed as finding bugs. There's a few main ways of doing this when searching for bugs in C/C++ code: * Design consultations early in

Security analysis is uses framed as finding bugs. There's a few main ways of doing this when searching for bugs in C/C++ code: * Design consultations early in development to address insecure or risky designs. * Reading risky parts of the code line by line hunting for buffer overflows and many other things. If you don't have access to the source, you can read the disassembly too, and people find a lot of bugs doing that! * Fuzzing. Basically hooking up the program to a harness which throws random data at its attack surface until the program crashes, although it can get a lot more nuanced than that. * Running static analysis tools to search for problematic code patterns. The C/C++ code which powers all major operating systems and web browsers is rife with security issues. There are also whole other sub-disciplines auditing websites, corporate networks, and cryptography implementations, which generally use analogous techniques.