Feature Release

Kickstarting Vulnerability Investigations with Code Owner Context for GitLab + GitHub

Sarah Elkaim

Head of Product Marketing

September 11, 2025

Share

When a new vulnerability shows up in the cloud, often the hardest part for SecOps is knowing where to start. The detection itself is easy. The challenge is figuring out who owns the code, who pushed it, and who can fix it. That step usually takes time and slows everything down.

With Sweet Security’s new Code Owner capability, SecOps can instantly see which developer last updated the image where the vulnerability was found. You see the author, the commit message, and the Git project right next to the finding. That means the investigation starts with the right person and the right context: this is the vulnerable workload, this is the commit, and this is the engineer who touched it last

Link vulnerabilities to the exact developer, commit, and Git repo.

Code Owner + Sweet Score + Context Graph = <3 

Traditionally, vulnerability management has been plagued with inefficiencies like:

  • Ownership gaps: SecOps often have no idea which developer to involve
  • Prioritization struggles: High CVSS scores don’t always mean high risk in your environment
  • Context silos: Vulnerability data is separated from runtime and code insights

Our Code Owner feature directly addresses the first gap and when paired with the Sweet Score and Context Graph, it tackles all three.

The Sweet Score tells you whether a vulnerability is actually risky in your environment. CVSS alone doesn’t give that answer. For example, a Log4j bug with a base score of 9.8 might not load at runtime and might not be exposed. The Sweet Score can adjust that to a medium priority so you do not waste cycles.

The Context Graph shows where the vulnerability lives. You can see the affected image, the application it belongs to, where it runs, and now who owns the code. The graph turns a single finding into a complete picture of risk across the environment.

Put together, these pieces give SecOps three things. 

  1. What to fix first. 
  2. How to guide the fix. 
  3. Who to hand it to.

90% Reduction in Remediation Time

Sweet’s customers using this workflow report up to a 90% faster completion rate from the time a vulnerability is detected to the time it is remediated. And detection is only the first step. The value is in helping teams act on what they find and Sweet makes sure the path from detection to action is as short as possible.

To learn more about Sweet’s Vulnerability Management, book a demo today

Share the Sweetness