What is the impact in Vulnerability Response of leaving the CI "Owned by" field blank?

David Dietrich1
Tera Expert

What is the consequence of leaving the "Owned by" field blank on CIs as it relates to the Vulnerability Response application? I know that the "Managed by" field can be used to assign remediation tasks, but I'm not sure how Vulnerability Response uses the "Owned by" field, and the Participant Guide for the Vulnerability Response Implementer certification seems to think this field gets used by Vulnerability Response for something.

1 ACCEPTED SOLUTION

Ajay_Chavan
Kilo Sage

Main Problem: You lose a backup way to assign vulnerability fix tasks to people.
How ServiceNow assigns tasks:

  • First choice: Support Group (IT team that fixes things)
  • Second choice: Managed by Group (team that manages the system
  • Third choice: Owned by (business person who "owns" the system)
Glad I could help! If this solved your issue, please mark it as ✅ Helpful and ✅ Accept as Solution so others can benefit too.*****Chavan A.P. | Technical Architect | Certified Professional*****

View solution in original post

1 REPLY 1

Ajay_Chavan
Kilo Sage

Main Problem: You lose a backup way to assign vulnerability fix tasks to people.
How ServiceNow assigns tasks:

  • First choice: Support Group (IT team that fixes things)
  • Second choice: Managed by Group (team that manages the system
  • Third choice: Owned by (business person who "owns" the system)
Glad I could help! If this solved your issue, please mark it as ✅ Helpful and ✅ Accept as Solution so others can benefit too.*****Chavan A.P. | Technical Architect | Certified Professional*****