# Owner assignment

GLOSSARY, read 10 Nov 2026

**Definition.** Owner assignment routes each finding to the person or team accountable for fixing it, by rule: asset tags, a configuration database field, a repository owner or a group lookup. Unassigned findings do not get fixed, so the share without an owner is a first-order program metric.

Rules run in order, and the first match applies in many platforms. Review the order after reorganizations.

Some platforms add machine-assisted attribution for missing owners, with a confidence threshold for human review.

## A sourced example

On 2026-11-10 ServiceNow's Vulnerability Response documentation described assignment rules that assign findings by user group, by the user group field on the configuration item, or by script, running in ascending order with the first match applying.

## Related terms

- [CMDB](/glossary/cmdb/)
- [Remediation grouping](/glossary/remediation-grouping/)
- [Bi-directional ticket sync](/glossary/bi-directional-ticket-sync/)
- [Remediation SLA](/glossary/remediation-sla/)

## Sources

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

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/owner-assignment/
