# Remediation grouping

GLOSSARY, read 10 Nov 2026

**Definition.** Remediation grouping bundles many findings that one action fixes, for example a patch that closes forty CVEs on a host, into a single task. It reduces tickets and matches how IT works. Grouping rules decide the unit of work, so they shape workload more than the ranking does.

Common grouping keys are the patch or fix, the asset, the owner and the business unit. A group inherits the highest priority of its members in most designs.

Check what happens to the group when one member is accepted as an exception.

## A sourced example

On 2026-11-10 ServiceNow's documentation stated that remediation task rules group vulnerable items into tasks automatically using up to six grouping conditions.

## Related terms

- [Owner assignment](/glossary/owner-assignment/)
- [Bi-directional ticket sync](/glossary/bi-directional-ticket-sync/)
- [Finding](/glossary/finding/)
- [Mean time to remediate](/glossary/mean-time-to-remediate/)

## Sources

- Source for the example: Remediation grouping: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/OIaWSs90vzTiHXZ6Pj6KUw/content (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/remediation-grouping/
