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
32908e09
Commit
32908e09
authored
Mar 31, 2020
by
celdem
Committed by
can eldem
Apr 06, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document detection logic changes DS when switching no-DinD mode
parent
ff4a5178
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
17 additions
and
0 deletions
+17
-0
doc/user/application_security/dependency_scanning/index.md
doc/user/application_security/dependency_scanning/index.md
+8
-0
doc/user/application_security/sast/index.md
doc/user/application_security/sast/index.md
+9
-0
No files found.
doc/user/application_security/dependency_scanning/index.md
View file @
32908e09
...
...
@@ -216,6 +216,14 @@ variables:
This will create individual
`<analyzer-name>-dependency_scanning`
jobs for each analyzer that runs in your CI/CD pipeline.
By removing Docker-in-Docker (DIND), GitLab relies on
[
Linguist
](
https://github.com/github/linguist
)
to start relevant analyzers depending on the detected repository language(s) instead of the
[
orchestrator
](
https://gitlab.com/gitlab-org/security-products/dependency-scanning/
)
. However, there
are some differences in the way repository languages are detected between DIND and non-DIND. You can
observe these differences by checking both Linguist and the common library. For instance, Linguist
looks for
`*.java`
files to spin up the
[
gemnasium-maven
](
https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium-maven
)
image, while orchestrator only looks for the existence of
`pom.xml`
or
`build.gradle`
.
## Interacting with the vulnerabilities
Once a vulnerability is found, you can interact with it. Read more on how to
...
...
doc/user/application_security/sast/index.md
View file @
32908e09
...
...
@@ -194,6 +194,15 @@ variables:
This will create individual
`<analyzer-name>-sast`
jobs for each analyzer that runs in your CI/CD pipeline.
By removing Docker-in-Docker (DIND), GitLab relies on
[
Linguist
](
https://github.com/github/linguist
)
to start relevant analyzers depending on the detected repository language(s) instead of the
[
orchestrator
](
https://gitlab.com/gitlab-org/security-products/dependency-scanning/
)
. However, there
are some differences in the way repository languages are detected between DIND and non-DIND. You can
observe these differences by checking both Linguist and the common library. For instance, Linguist
looks for
`*.java`
files to spin up the
[
spotbugs
](
https://gitlab.com/gitlab-org/security-products/analyzers/spotbugs
)
image, while orchestrator only looks for the existence of
`pom.xml`
,
`build.xml`
,
`gradlew`
,
`grailsw`
, or
`mvnw`
.
#### Enabling kubesec analyzer
> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/12752) in GitLab Ultimate 12.6.
...
...
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