Authenticated Dynamic Application Security Testing (DAST)¶
AccuKnox DAST now supports authenticated scans, enabling comprehensive security testing of protected application areas that require user authentication. This feature ensures thorough vulnerability detection by allowing the scanner to access content behind login pages, preventing false negatives that occur when crawlers cannot reach authenticated endpoints.
Why Authenticated DAST?
Authenticated DAST scans provide enhanced security testing capabilities by:
-
Toggling between authentication modes: Switch between authenticated and unauthenticated scan modes based on your testing needs.
-
Supporting credential-based authentication: Input username and password for applications requiring login.
-
Visualizing scan states: Real-time indicators show scan status as "Logged In," "Logged Out," or "Fallback."
-
Preventing false negatives: Access protected content that unauthenticated crawlers would miss, ensuring comprehensive vulnerability coverage.
Configuration Steps¶
Follow these steps to configure and run an authenticated DAST scan in AccuKnox:
1. Access the AccuKnox Platform¶
-
Log into the AccuKnox Platform.
-
Navigate to Settings → Collectors.

-
Click on "Add Collector".

-
Select "Web Application DAST Scan".

2. Configure Basic Settings¶
-
Collector Name: Provide a descriptive name for your DAST collector.
-
Click Next to proceed to the configuration parameters.
3. Configure Scan Parameters¶
| Parameter | Description | Example |
|---|---|---|
| Target URL | The primary target URL to scan. | https://example.com |
| Scan Type | Choose the scan depth: Baseline (quick scan) or Full (comprehensive scan). | Baseline or Full |
| Authentication Mode | Select authentication type: No Auth (default) or Auth Based (requires login). | No Auth / Auth Based |
| Login Page URL | The URL of the application's login page. | https://example.com/login |
| Login Credentials - Username | The username for authentication. | — |
| Login Credentials - Password | The password for authentication. | — |
| Include Path | URLs or patterns to include in scan scope (supports wildcards). | https://api.example.com/* |
| Exclude Path | URLs or patterns to exclude from scan (e.g., logout endpoints). | https://example.com/logout |
| Logged In Indicator | Keyword/phrase indicating successful login (e.g., Welcome, Dashboard, My Account). | Welcome |
| Logged Out Indicator | Keyword/phrase indicating logout or session expiration (e.g., Login, Sign In, Session Expired). | Login |
| Login Fallback URL | Post-login page URL to verify successful authentication. | https://example.com/dashboard |
| Label | Label for organizing scan results. See AccuKnox Labels. | — |
| Tags | (Optional) Tags for categorization and filtering. | — |

4. Configure Notifications¶
Enter your email address where you would like to receive scan notifications and press Enter.

5. Submit and Monitor Scan¶
-
After submitting the configuration, the scan will be automatically triggered.
-
You can monitor the scan progress on the same page.

-
Once the "Findings" column is populated, click on it to view detailed results.

6. View Findings¶
Clicking on the findings count will redirect you to the Findings page with:
-
Detected Vulnerabilities: List of security issues discovered during the scan.
-
Severity Ratings: Critical, High, Medium, and Low classifications.
-
Detailed Evidence: Request/response details, affected endpoints, and remediation guidance.
Best Practices
-
Use descriptive indicators: Choose logged-in and logged-out indicators that are unique and consistent across your application.
-
Test credentials separately: Verify that login credentials work before configuring the scan to avoid authentication failures.
-
Review exclude paths carefully: Ensure that logout endpoints and sensitive areas are properly excluded to maintain session stability.
-
Monitor scan notifications: Enable email notifications to stay informed about scan completion and critical findings.
Conclusion¶
Authenticated DAST scanning in AccuKnox enables comprehensive security testing of web applications with protected content. By configuring authentication parameters correctly, you can ensure thorough vulnerability detection across your entire application surface, including areas that require user login.