You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 14, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: docs/user-guide/usage-examples/zap-bodgeit-example.md
+48-1Lines changed: 48 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ The following example contains a fully configured ZAP Scan for the BodgeIt Store
55
55
```json
56
56
[
57
57
{
58
-
"name": "Arachni BodgeIt Scan",
58
+
"name": "ZAP BodgeIt Scan",
59
59
"location": "http://bodgeit:8080/bodgeit/",
60
60
"attributes": {
61
61
"ZAP_BASE_URL": "http://bodgeit:8080/bodgeit/",
@@ -73,3 +73,50 @@ The following example contains a fully configured ZAP Scan for the BodgeIt Store
73
73
```
74
74
75
75
This scan should finish in about a minute and should return a couple of findings.
76
+
77
+
## Scan with a given sitemap (skip spider task)
78
+
79
+
It is also possible to run the zap scan process with a predefined sitemap. In this case the spider task will be skiped and the zap scanner microservice can start directly with the scan task.
The sitemap contains request objects in a HAR format. To generate the requests for your sitemap, you can:
121
+
* take the result of previous microservice zap spider tasks via camunda ui OR
122
+
* use a local running ZAP application as a proxy, browse manully through your target and import the recorded requests via "http://[your-local-zap]:[your-zap-port]/UI/core/other/messagesHar/"
0 commit comments