Configure low route coverage policies
Configure a low route coverage policy to ensure your applications consistently meet your route coverage goals. By setting these thresholds, you gain visibility into missed areas where vulnerabilities might be hiding.
Automated notifications and tracking
If you integrated Contrast with bug tracker systems (such as Jira), Contrast automatically creates a ticket or work item when application route coverage falls below your configured policy.
Every 24 hours, applications discovered below the threshold will send an initial notification for low route coverage. This can be sent via bug tracker ticket, email, and the Contrast web interface.
Bridging the gap for developers
These automated alerts provide actionable information to help developers improve testing efficacy. When the policy triggers a notification, Contrast sends the following information:
The full list of untested routes: A clear inventory of what remains unverified
Testing guidance: Information on how to exercise those routes to improve coverage
Absolute route coverage policy
The absolute coverage policy determines the route coverage threshold that selected applications must meet all the time.
Steps
From the user menu, select .Organization settings
Select Applications.
Under Data management, go to Low route coverage policy.
Set the policy:
Select the Absolute coverage checkbox.
Specify a threshold percentage for route coverage.
Select the applications that must adhere to the policy.