One of the most high-profile security threats in recent times was the Blaster worm which was first seen on July 14, 2003, infected at least 100,000 Microsoft windows systems, and cost millions in damage. According to some commentators, the W32.Blaster worm may have contributed to the cascading effect of the blackout in the US north-east that year.

This paper explains how SAST (Static Analysis/Application Security Test) tools can help you find such security vulnerabilities early in the secure software development lifecycle (SSDLC), minimizing opportunities for bad actors when the software is deployed.