Azure DevOps - Configure Priority Tags

Mik T
Mik T
  • Updated

When using Azure DevOps to track and monitor security issues, Vanta detects the priority from the Azure DevOps' Priority field.

Azure DevOps indicates priority value as “1, 2, 3, 4,” etc. Vanta handles priority values as P0, P1, P2, and P3.

Since Azure DevOps does not have an equivalent P0 option, Vanta accounts for this offset by mapping the priorities from Azure DevOps as follows: 

  • Priority 1 = P0 in Vanta (High)
  • Priority 2 = P1 in Vanta (Medium)
  • Priority 3 = P2 in Vanta (Low)
  • Priority 4 = P3 in Vanta (Lowest)

Common Issues 

Suppose you notice security issues in a test that does not represent their intended security priority. In that case, we recommend testing setting the Azure DevOps Priority field as the value that best matches the mapping above.

 

image (19).png