Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
ce5f0128
Commit
ce5f0128
authored
Mar 04, 2021
by
Lucas Charles
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
docs: Fix secret detection variable reference
Historic scan should reference the variables table for SD not SAST.
parent
e8a9a795
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/user/application_security/secret_detection/index.md
doc/user/application_security/secret_detection/index.md
+1
-1
No files found.
doc/user/application_security/secret_detection/index.md
View file @
ce5f0128
...
...
@@ -258,7 +258,7 @@ want to perform a full secret scan. Running a secret scan on the full history ca
especially for larger repositories with lengthy Git histories. We recommend not setting this CI/CD variable
as part of your normal job definition.
A new configuration variable (
[
`SECRET_DETECTION_HISTORIC_SCAN`
](
../sast/#vulnerability-filter
s
)
)
A new configuration variable (
[
`SECRET_DETECTION_HISTORIC_SCAN`
](
#available-variable
s
)
)
can be set to change the behavior of the GitLab Secret Detection scan to run on the entire Git history of a repository.
We have created a
[
short video walkthrough
](
https://youtu.be/wDtc_K00Y0A
)
showcasing how you can perform a full history secret scan.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment