Blomgren (Community Member) asked a question.
What does it mean, what is root cause, how to fix?
Almost 50 of our websites in our largest DAST scan returned this error despite the messaging in the DAST configuration page making it look like the URL was scanned with "Status Completed - Results Available" with a green check mark, connection successful, and over 5000 HTTP request/responses logged. There were even findings identified on the scans configuration page, but they do not show up in Triage Flaws and there is no log of the scan taking place in the app profile's SCANS tab. In many use cases, we rely on the SCANS tab for auditing purposes (and this is the only place app support teams are authorized to see their scan status/date/time). This shows no record of the scan taking place, despite the fact that it did. This is an issue from an auditing and logging perspective. I also need help troubleshooting the issue before our next recurring scan runs again. And yes we do have a support/engineering case open already.
.png){kind=logo}
Hi @Blomgren (Community Member) - Glad to hear that you sent in a support case, they will be more able to help you since they can look into more specifics about what's going on. I checked with a teammate and they said that it's unclear if this is an app linking issue or something else - our support will have to dig in and review.
Hi @Blomgren (Community Member) - I just checked and I don't see a support case from you on this issue. Please send us a Case here: https://community.veracode.com/s/contact-support
And if you could share a Scan link in your message, that will help our team determine what's going on.
Thanks!
Support Case Number: 00938849 (I was told the case was forwarded to an Engineering case, but they did not provide me with the ENG number.
Scan Link: https://web.analysiscenter.veracode.com/was/#/analysis/65bbf1dcc2678ee2abdb180bc2338358/scans
The case was opened on Monday. The reply I got today did not address the issue I originally raised and now they are trying to close the case prematurely before addressing my concern. They said the URL in question did not have enough time to complete and to just rescan with a longer time window. However, earlier, I made sure to asked them to include and investigate all 47 failed URLs that had Results Exports=Invalid, in addition to the one example URL I provided in the case. They did not comment at all on the Results Export issue. It has been frustrating...
Thanks for the update @Blomgren (Community Member) - I'll flag this for review and share these details with my teammate.