When to use SAST versus an LLM security scanner

From the source: GitLab Blog

You're probably running some version of this experiment already: Point a frontier model at a merge request and ask it to double as a vulnerability scanner. On a single merge request, it often works well. The model reads the code, reasons about what it's supposed to do, and catches real issues, sometimes ones a pattern-based scanner misses entirely. So the next thought is reasonable: If a model…

Read the full story on GitLab Blog
Originally published by GitLab Blog on 16 Sept 2026. Techarda links to the original rather than republishing it. Read the full article →

Ask the square

The story is what was announced. If it raises a question for your team, ask the people who run this technology day to day. Your post links back to this story, so the next reader finds it too.

Recent threads in DevOps & Platform Engineering

Something wrong or out of date? Suggest a correction. We reply within 5 business days.

More from GitLab

Recent updates from GitLab, so you can tell whether this is a one-off or part of a pattern.

All GitLab news →

More in DevOps & Platform Engineering

What other companies in DevOps & Platform Engineering are doing. The category page shows who’s active, side by side.

Compare companies in DevOps & Platform Engineering →