Running a scan
Run Scan
Run Scan starts a verification run for the selected integration, with our very fast testing and signal detection engine. When used at project level, it starts one verification run per active project item in the project and its subprojects; items already scanning or over quota are skipped. The scan should take a few seconds before you can view the results of your project item.
If a verification run cannot start, it is often because the integration or project item is inactive. For details, see Inactive integrations and project items.
Results
You will get sorted results from a severity perspective, which are low, medium, high and critical. Finding names and technology they are related to. Categories are default categorization labels telling you if the problem is SRE, DevOps, Security, Code quality or another type of issue. There are two types of remediations - Improvement and Must Have. Must Have is an action item we recommend to fix as soon as possible. The Improvement is something that you should put in your roadmap and it's still critical for implementation of proper DevSecOps.