table of contents
| glab(1) | glab(1) |
NAME¶
glab-security-config-disable - Disable a security scan profile for a project. (EXPERIMENTAL)
SYNOPSIS¶
glab security config disable [flags]
DESCRIPTION¶
Detach a security scan profile from a project.
Prerequisites:
- •
- At least the Maintainer role or the Security Manager role for the project.
For <profile>, use one of the following identifiers:
- secret_detection: Secret detection.
- sast: SAST.
- dependency_scanning: Dependency scanning.
- dependency_scanning_post_processing: Dependency scanning auto-remediation.
- business_logic: Business logic.
- skillguard: SkillGuard.
- triage_and_remediation_conservative: Automated triage and remediation, Conservative preset.
- triage_and_remediation_standard: Automated triage and remediation, Standard preset.
- triage_and_remediation_proactive: Automated triage and remediation, Proactive preset.
- For a custom profile, the numeric part of the profile ID. For example, 123 for gid://gitlab/Security::ScanProfile/123.
This feature is an experiment and is not ready for production use. It might be unstable or removed at any time. For more information, see https://docs.gitlab.com/policy/development_stages_support/.
OPTIONS INHERITED FROM PARENT COMMANDS¶
-h, --help[=false] Show help for this command.
-R, --repo="" Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.
EXAMPLE¶
# Disable dependency scanning on the current project $ glab security config disable dependency_scanning # Disable SAST on a specific project $ glab security config disable sast -R gitlab-org/cli # Disable auto-remediation for vulnerable dependencies $ glab security config disable dependency_scanning_post_processing
SEE ALSO¶
| Nov 2026 | Auto generated by spf13/cobra |