Skip to content

Setting Up Jenkins DAST with AccuKnox for Code Testing

Overview

The AccuKnox DAST Jenkins Plugin simplifies integrating dynamic application security testing (DAST) into Jenkins pipelines. This plugin allows you to perform ZAP-based scans on target URLs and seamlessly upload the results to AccuKnox SaaS for centralized investigation and analysis.

Key Features

  • Automated DAST Scans: Perform Baseline or Full Scans on target URLs directly from your Jenkins pipelines.

  • Seamless Integration with AccuKnox: Upload scan results to AccuKnox SaaS, enabling centralized management of DAST findings alongside SAST, IaC, and container security findings.

  • Customizable Build Parameters: Define parameters like target URL, scan type, severity thresholds, and AccuKnox authentication details.

Installation

  1. Download the plugin in .hpi format from here.

  2. Navigate to the Jenkins dashboard.

  3. Go to Manage Jenkins > Manage Plugins. image-20250124-041037.png

  4. Under the Advanced tab:

  5. Click Choose File and select the downloaded .hpi file. image-20250114-184732.png image-20250124-041316.png

  6. Click Deploy to install the plugin. image-20250124-041354.png

  7. Restart Jenkins if required.

Configuration

Job Configuration

  1. Open the configuration page of your Jenkins job.

  2. Under the Build section:

  3. Click Add build step.

  4. Select Run AccuKnox DAST Scan.

image-20250124-041651.png

Plugin Parameters:

The plugin provides the following configuration options:

Parameter Description Example
Target URL URL of the web application to scan. https://example.com
Scan Type Type of scan: baseline or full-scan. full-scan
Tenant ID Tenant ID associated with your AccuKnox account. my-tenant-id
AccuKnox Token Authentication token for AccuKnox SaaS. my-accuknox-token
Label A label to tag the scan results in AccuKnox SaaS. build-123
Severity Threshold Minimum severity level to trigger build failures (e.g., High). High

image-20250124-045000.png

Token Generation for AccuKnox

To generate the AccuKnox Token and obtain the Tenant ID:

  1. Log in to AccuKnox.

  2. Navigate to Settings > Tokens and create an AccuKnox token.

  3. Copy the generated token and store it securely for later use. For detailed steps, refer to How to Create Tokens.

Running the Scan

When you run the Jenkins job:

  1. DAST Scan Execution:

  2. The plugin performs a DAST scan (baseline or full) on the target URL.

  3. Results are saved as a report.json file in the workspace.

  4. Uploading Results to AccuKnox SaaS:

  5. The report.json file is uploaded to the specified AccuKnox tenant using the provided credentials.

Sample Console Output:

Running AccuKnox DAST Scan...
ZAP output: [ZAP Scan Logs]
Uploading DAST scan results to AccuKnox...
Results uploaded successfully.

Troubleshooting

  1. Missing AccuKnox Token or Tenant ID:

  2. Ensure both fields are provided in the Jenkins job configuration.

  3. Verify their accuracy in the AccuKnox SaaS dashboard.

  4. Scan Failure:

  5. Check the Jenkins console output for ZAP-specific errors.

  6. Verify that the target URL is accessible and not blocking scan requests.

  7. Upload Failure:

  8. Verify network connectivity to the AccuKnox SaaS endpoint.

  9. Double-check the Tenant ID and AccuKnox Token.

  10. Ensure the report.json file is generated correctly before uploading.

Conclusion

The AccuKnox DAST Jenkins Plugin simplifies the process of integrating dynamic application security testing into your CI/CD pipeline. By seamlessly combining ZAP-based scans with AccuKnox SaaS, you can ensure vulnerabilities are identified and managed in a centralized manner, improving the overall security posture of your application.

For further assistance, contact the AccuKnox support team or refer to the AccuKnox Documentation.