Description
Initial DAST troubleshooting steps
Solution
Section 1: Collect software versions
Please gather the following information:
1). Is this either external or internal webapplication?
2). Did you scan this same web-application in the past properly? What has changed now from the past?
3). Are you able to scan a different web-application with similar configuration you are trying to scan?
4). Are you using Macro recorder? If so please provide all information described in this article:
SC DAST Login Macro initial troubleshooting info
Note: either Opentext support engineer or Ops can provide the following information:
5). SSC version:
6). SC DAST Sensor WebInspect version:
7). SC DAST Sensor Application Version:
Section 2: All Logs collection steps and analysis
1). In Fortify SSC go to ScanCentral | DAST
2). Gather the following information after you run one scan having Enabled traffic Monitor activated:
Scan Id
Sensor where the scan was running
3). At first, if the scan had Enabled traffic Monitor you check the traffic logs in case there is network connectivity issue to the website:
SSC SC DAST how do I see the scan logs after enabled traffic monitor?
https://support.cyberreshelp.com/hc/en-us/articles/25958996045975-SSC-SC-DAST-how-do-I-see-the-scan-logs-after-enabled-traffic-monitor
4). While checking the Scan you can click "Download" to get the following files:
Scan Result (if available, the below files are not needed, because below files are included in the Scan Results)
Scan Settings
Scan Logs
FPR
Note: depending of the issue/scenario that is happening, you may download one file or the other.
Section 3: Reproduction steps
Please provide a walkthrough of reproduction steps with files needed for the reproduction.