Security tools

Static Application Security Testing (SAST) is designed for white-box source code analysis and can range from a package-based approach (e.g. bandit) designed for a specific language to more complex scanners such as Contrast Security’s SAST tool. Other Software Composition Analysers (e.g. Snyk) are designed to catch known vulnerabilities in third-party components. However, when it comes to understanding the internal logic of compiled native binaries, we need proper tools like IDA Pro, Binary Ninja, or Radare 2. These help reveal all the code paths that an application may take without executing the application itself. 

Dynamic Application Security Testing (DAST) checks the runtime behaviour of applications without accessing their source code. Veracode is an example of a vendor which offers such solutions. Modern approaches include Runtime Application Self Protection (RASP), which  provides runtime protection to keep applications from being exploited (e.g. Contrast Security’s RASP solution). Fuzzers such as AFL help manipulate executable inputs to trigger potential security bugs. Others, such as the Unicorn CPU Emulators, allow for emulating binaries cross platform.

In order to protect your code against the most critical web vulnerabilities, you first need to use proper frameworks such as Angular, Django, or Laravel that help eliminate the most obvious security issues. Other tools, such as Bleach or CSP evaluator can add an extra layer of security against XSS as long as they are bug-free. However, it’s still best to be prepared against all the vectors that OWASP top 10 collected.

The main objective of these tools is to intercept or record network traffic and allow analysts to monitor, analyse, or modify the requests on the go. This category includes Wireshark to capture packets, Burp Suite to scan for web vulnerabilities, nmap to discover networks, and SIEMs (Security Information and Event Management) such as OSSIM to collect network traffic from different sources to detect malicious activity.