-
Notifications
You must be signed in to change notification settings - Fork 46
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #457 from owasp-noir/closed-351
Update community articles and add DAST pipeline documentation
- Loading branch information
Showing
3 changed files
with
35 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
--- | ||
title: Pipeline for DAST | ||
parent: Tips | ||
has_children: false | ||
nav_order: 3 | ||
layout: page | ||
--- | ||
|
||
## Proxy Tool Integration | ||
|
||
This command automates the use of a proxy tool in a security testing pipeline. noir is used with the `-b` option to specify the base directory (.) and -u to target a local application (http://localhost.hahwul.com:3000). The --send-proxy parameter directs traffic to a proxy server running on http://localhost:8090. This setup allows for monitoring and intercepting HTTP requests through tools like ZAP, Caido, or Burp Suite during the testing process. | ||
|
||
```bash | ||
noir -b . -u http://localhost.hahwul.com:3000 --send-proxy "http://localhost:8090" | ||
``` | ||
|
||
## ZAP Integration | ||
|
||
The process begins with endpoint discovery using noir, which scans the application source code in the specified directory (~/app_source), generates an OpenAPI specification (doc.json), and saves it in JSON format. | ||
|
||
Next, the doc.json file is used in an automated ZAP scan. The zap.sh script, with the `-openapifile` option, loads the generated endpoints and uses `-openapitargeturl` to specify the target URL for testing. The `-cmd` and `-autorun` options allow for automated execution of ZAP commands based on zap.yaml, along with any additional configuration parameters. This setup enables comprehensive vulnerability assessment across discovered endpoints in the target application. | ||
|
||
```bash | ||
# Discovering endpoints | ||
noir -b ~/app_source -f oas3 --no-log -o doc.json | ||
|
||
# Automation scan with endpoints | ||
./zap.sh -openapifile ./doc.json \ | ||
-openapitargeturl <TARGET> \ | ||
-cmd -autorun zap.yaml <any other ZAP options> | ||
``` | ||
|
||
For further details on integrating Noir and ZAP for enhanced DAST capabilities, refer to the [Powering Up DAST with ZAP and Noir](https://www.zaproxy.org/blog/2024-11-11-powering-up-dast-with-zap-and-noir/) ZAP blog post. |
This file was deleted.
Oops, something went wrong.