What are the best practices for setting up a remediation workflow?
This article describes how to prioritize vulnerabilities and configure a remediation workflow, including ticket routing integrations. The goal is to create a closed-loop process where findings are reviewed, assigned, fixed, and verified.
Prioritization framework
Not all vulnerabilities are equal. Avoid trying to fix everything at once, as this can lead to paralysis. Use the following model as a starting point.
| Priority: | CVSS: | Target SLA: | Criteria: |
|---|---|---|---|
| P1, Critical | 9.0-10.0 | 24-72 hours | Internet-exposed, a known exploit is available, or there is active exploitation in the wild. |
| P2, High | 7.0-8.9 | 7 days | High CVSS with exploit code available, or medium CVSS on a critical asset. |
| P3, Medium | 4.0-6.9 | 30 days | Exploitable under specific conditions, with no current active exploitation. |
| P4, Low | 0.1-3.9 | 90 days or risk-accept | Minimal impact, but document and address during planned maintenance. |
Remediation rules configuration
Remediation rules automatically assign findings to the right team based on tag, asset group or vulnerability type, so you do not need to route tickets manually.
- Map each business unit tag to a ticket queue or assignee group. For example, a finding on a finance-tagged asset should route automatically to your finance IT team.
- Set reminders at a maximum of 14 days.
- Create a default rule for untagged assets, so findings never silently go unassigned.
- Review rule coverage after your first scan cycle. Check for findings with no assigned owner and adjust your rules accordingly.
Integration-specific configuration
Below are our most used integrations but more alternatives, including webhooks, are available under Integrations in Security Center.
| Integration: | Key configuration points: |
|---|---|
| Jira | Use a dedicated Jira project for security findings. Map severity to Jira priority. Set up a webhook to update finding status when a Jira ticket is closed. Make sure the service account has "Create Issue" and "Transition Issue" permissions. |
| ServiceNow | Map to the Incident or Problem module depending on your process. Confirm the assignment group naming convention matches exactly, as mismatches fail silently. Enable bidirectional sync so resolved tickets close findings. |
| TopDesk | Use the REST API connector. Confirm API key permission scope with your TopDesk admin. Test with a manual trigger before enabling scheduled auto-creation. |
| Only use this option when no integration is available. It requires Security Center access for the sending account and correct RBAC so recipients can log in and acknowledge findings. |