Stop Bad Code From Ever Deploying With Datadog

Most teams do not have a vulnerability detection problem so much as a "which of these 7,000 findings actually matters" problem.

In this session, RapDev's Jason Fox (SOC Manager) and Kenna Skoczen (SOC Analyst) walk through Datadog Code Security: how to stop vulnerable code from merging in the first place with PR Gates, and how to use runtime and production context to prioritize the findings that are genuinely exploitable.

What we cover:

• The three-part model: prevent at development time, pinpoint with application context, prioritize by real impact
• Building a PR Gates rule in Datadog, from source and scope through severity conditions
• Turning the gate into a required status check so risky pull requests cannot merge
• Narrowing 7,000+ vulnerabilities down to the handful that are in production, exploitable, and exposed to attack
• Reading a finding end to end: the what, the where, the affected service, and the remediation path
• The service page you already know, now carrying security context alongside performance