Module selection
By default, the Scanner will select any modules that contain entry points and are not a dependency of any other module in the compilation. For any module to even be selected at all, it must contain an entry point.
Sometimes customers will have a dependency that they actually need scanned in it's entirety and need to select it. To do this, they would need to click the "show dependencies" button and manually check off any of those modules. However, keep in mind that if a module is not selected, this does not mean that the Scanner does not touch that module, it just means that the Scanner is not going to scan every line of code within it. What it will do is scan only the code that is called upon by the modules that are selected, which is usually the best approach with dependencies, hence the default selection. Which is sometimes what is best for the app and the results of it since then they are more realistic, however this judgement call must be made by the developers since they know their own app.
Related Articles
Adding CSP Header- Allowing inline script using 'nonce' - Java example. Number of Views Is the customizable report available for the Sandbox scan? Number of Views Does Veracode's Dynamic Analysis support the scan of a Thick Client App? Number of Views .NET Remediation Guidance for CWE-601 Number of Views How to download only Dynamic scan result report only. Number of Views
This topic isn't available in this community.
Related Topics
Ask the Community
Get answers, share a use case, discuss your favorite features, or get input from the Community.
.png){kind=logo}
