Best practices for hybrid analysis
Because the testing approaches are so different, however, the correlation percentage can be relatively low. The challenges and strengths for each type of analysis differ, as depicted in this table.
Dynamic analysis | Static analysis |
---|---|
Awareness | Over approximation |
Code coverage | Code/path coverage |
Source-free | Limited to given code |
HTTP awareness only | More than HTTP validations |
Multi-component support | Support per language/framework |
Requires deployed application | No need to deploy application |
Few prerequisites | Support partial applications |
Works as a remote attacker | Integration/deployment issues |
For best correlation results:
- Pre-filter the SAST issues to the highest severity setting on the Definitive, Suspect issues.
- Save a partial assessment or configure the filter to be applied automatically before you publish to AppScan® Enterprise.
- With DAST, make sure you explore as much of the application as possible, and use the most comprehensive security test policy that makes sense for the application.
- Make sure you analyze the same version of the web application with both approaches.