Home / Companies / GitLab / Blog / Post Details
Content Deep Dive

Full security scanner coverage of your codebase in minutes

Blog post from GitLab

Post Details
Company
Date Published
Author
Michael Omokoh
Word Count
1,449
Company Posts That Month
21
Language
English
Hacker News Points
-
Post removed?
No
Summary

GitLab 19.0 introduces security configuration profiles, which offer a centralized approach to managing security scanners across multiple projects, addressing the scalability issues faced by CI/CD platforms as organizations grow. These profiles enable teams to apply static application security testing (SAST), dependency scanning, and secret detection uniformly across all projects from the outset, eliminating the need for manual configuration via individual .gitlab-ci.yml files. Default profiles come preconfigured, activating scan triggers such as merge request and branch pipelines, ensuring consistent security coverage and addressing vulnerabilities, compromised dependencies, and exposed secrets efficiently. This approach is particularly beneficial given the rapid code velocity driven by AI, reducing the drift between code development and security measures. The profiles are available on GitLab Ultimate and can coexist with existing scanner configurations, providing flexibility for users during transition periods.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Secrets Management 3 2,324 403 114 +18%
Real-time 2 6,790 1,736 269 -9%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.