Code tampering is a software company’s worst nightmare. Unfortunately, code tampering is leading to new major software supply chain attacks nearly every month: SolarWinds, Accellion, Click Studios, PHP, CodeCov, Kaseya, Log4Shell - the list goes on.

These incidents make it clear that attackers are hitting DevOps tools and infrastructure just as hard as production applications, looking for any entry point into the victim’s SDLC. After gaining access, they seek to expand laterally across each phase to tamper with code and push it live into production without detection. Ironically, the same DevOps automation that increases release efficiency also makes it easier for attackers to move laterally as each system becomes more tightly interconnected.

This webinar examines code tampering risks, shares lessons learned from recent incidents and proposes a four-pillar approach to reducing code tampering risk through:

• Integrity validation: Confirming files and artifacts across each phase of the SDLC
• Anomaly detection: Connecting dots from disparate systems to identify breaches
• Critical code monitoring: Determining which code to monitor for any and all changes
• Defense-in-depth: Applying security and governance policies across DevOps tools and cloud infrastructure