GitLab SAST and application security scanning
What GitLab security scanning gives on Free and Premium versus Ultimate: SAST analyzers, Advanced SAST, merge request findings and vulnerability management, and the runner capacity scans need.

GitLab capabilities that decide edition choice and implementation scope, from security scanning to self-hosted AI.
What GitLab security scanning gives on Free and Premium versus Ultimate: SAST analyzers, Advanced SAST, merge request findings and vulnerability management, and the runner capacity scans need.
Enforcing controls across projects with GitLab Ultimate: compliance frameworks, standards adherence and violations reports, merge request approval policies and separation of duties.
Recording administrator, group and project changes in GitLab and streaming audit events to a SIEM or storage, with the tier each capability needs.
Running GitLab Duo AI features against self-hosted models: add-on licensing, the self-hosted AI gateway, vLLM or cloud model platforms, and fully offline operation.
Running the GitLab container registry: storage backends, the metadata database and online garbage collection, cleanup policies and capacity planning for image storage.
Setting up advanced search on self-managed GitLab: supported Elasticsearch and OpenSearch versions, Amazon OpenSearch Service with IAM, cluster sizing rules and the indexing order before turning search on.
Deploying Zoekt for exact match and regex code search in self-managed GitLab: tiers, the supported Helm chart and Operator installs, storage for initial indexing and why Elasticsearch is still needed for other scopes.
Using the group-level dependency proxy as a pull-through cache for container images to cut Docker Hub rate limit hits in CI, and how administrators control it instance-wide.
Turning a GitLab project into an email support queue: tickets from customers without GitLab accounts, what self-managed needs for incoming email, and the fact that the feature is not under active development.
Running GitLab Pages on your own instance: wildcard DNS or single-domain path mode, unique domains, access control, custom domains with TLS or Let's Encrypt and moving deployments to object storage.
Storing OpenTofu state in GitLab instead of a separate backend: encryption at rest tied to db_key_base, role-based locking, versioning and the OpenTofu CI/CD component for pipelines.
Measuring deployment frequency, lead time, time to restore and change failure rate in GitLab Ultimate: production environment tiers, incident tracking requirements and recording pull-based deployments through the API.
The Premium approval settings auditors ask about: blocking author and committer approvals, locking approval rules, re-authentication as an electronic signature, removing approvals on new commits, and cascading from instance level.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.