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
77c77f8c
Commit
77c77f8c
authored
Jun 08, 2020
by
Cameron Swords
Committed by
Russell Dickenson
Jun 08, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add documentation on how to debug DAST
parent
d59c77bb
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
0 deletions
+23
-0
doc/user/application_security/dast/index.md
doc/user/application_security/dast/index.md
+23
-0
No files found.
doc/user/application_security/dast/index.md
View file @
77c77f8c
...
@@ -526,6 +526,29 @@ variables:
...
@@ -526,6 +526,29 @@ variables:
The DAST job does not require the project's repository to be present when running, so by default
The DAST job does not require the project's repository to be present when running, so by default
[
`GIT_STRATEGY`
](
../../../ci/yaml/README.md#git-strategy
)
is set to
`none`
.
[
`GIT_STRATEGY`
](
../../../ci/yaml/README.md#git-strategy
)
is set to
`none`
.
### Debugging DAST jobs
A DAST job has two executing processes:
-
The ZAP server.
-
A series of scripts that start, control and stop the ZAP server.
Debug mode of the scripts can be enabled by using the
`DAST_DEBUG`
environment variable. This can help when troubleshooting the job,
and will output statements indicating what percentage of the scan is complete.
For details on using variables, see
[
Overriding the DAST template
](
#overriding-the-dast-template
)
.
Debug mode of the ZAP server can be enabled using the
`DAST_ZAP_LOG_CONFIGURATION`
environment variable.
The following table outlines examples of values that can be set and the effect that they have on the output that is logged.
Multiple values can be specified, separated by semicolons.
| Log configuration value | Effect |
|-------------------------------------------------- | ----------------------------------------------------------------- |
|
`log4j.rootLogger=DEBUG`
| Enable all debug logging statements. |
|
`log4j.logger.org.apache.commons.httpclient=DEBUG`
| Log every HTTP request and response made by the ZAP server. |
|
`log4j.logger.com.crawljax=DEBUG`
| Enable Ajax Crawler debug logging statements. |
|
`log4j.logger.org.parosproxy.paros=DEBUG`
| Enable ZAP server proxy debug logging statements. |
|
`log4j.logger.org.zaproxy.zap=DEBUG`
| Enable debug logging statements of the general ZAP server code. |
## Running DAST in an offline environment
## Running DAST in an offline environment
For self-managed GitLab instances in an environment with limited, restricted, or intermittent access
For self-managed GitLab instances in an environment with limited, restricted, or intermittent access
...
...
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