Hello @AChristie579654 (Community Member)​ ,

Thanks for your question. It sounds like the third party DLL may have been selected as an entry point. For the most optimal, relevant and actionable findings we recommend only selecting first party modules without an entry point or with an entry point that is user facing. This typically means that you should not select modules with a library entry point (such as microsoft.reportviewer.winforms.dll). I recommend only selecting components that are part of your application which interface with the outside world, and not any application dependencies. Whilst we need the dependencies of the application to be included in the scan to provide the greatest coverage, they should not usually be selected as being entry points.

You may wish to read this community article for more information on tuning the module selection: https://community.veracode.com/s/article/What-are-Modules-and-how-do-my-results-change-based-on-what-I-select.

If however the correct entry points have been configured, it could potentially be a flaw within the microsoft.reportviewer.winforms.dll library, which you may wish to report to Microsoft since third party flaws still pose risk to your application.

I hope that answers your question.

Kind regards,

Anthony Fielding