Managing Cross-Functional Work for Vulnerability Items (VITs) Without Transferring SLA Ownership

Viji Rohan
Tera Contributor

Hello,

 

We're looking for guidance on how other organizations handle cross-functional work on Vulnerability Items (VITs) when SLA accountability remains with a single owning team.

A VIT is assigned to and owned by a specific team with the remediation SLA. However, remediation often requires work from other teams such as:

  • Firewall teams
  • Network teams
  • Infrastructure/Patching teams
  • Other supporting technical groups

These supporting teams are not accountable for the VIT SLA, so assigning the VIT directly to them is not desirable. As a result, the owning team often coordinates the work manually through chats, emails, phone calls, and meetings.

Question: How are other organizations tracking and managing these dependencies within VRM/Vulnerability Response?

In ITSM, we have mechanisms such as:

  • Change Tasks
  • Problem Tasks
  • Catalog Tasks

that allow work to be delegated and tracked while ownership remains with the parent record.

For VITs, I'm aware of Affecting Tasks, but these extend the generic Task table and seem to be intended more for linking records such as Incidents or Changes to a VIT. I'm not referring to Remediation Tasks in this discussion.

Is there an out-of-the-box approach for creating and tracking work items against a VIT while retaining SLA ownership with the primary team? Or have most organizations addressed this through:

  • Custom task tables (e.g., a VIT Task table)
  • Related Change/Incident records
  • Other patterns or best practices?

I'd be interested to hear how others have implemented this and what has worked well in practice.

Thanks in advance for any insights.

 

Regards,

Viji

 

3 REPLIES 3

kmohammed
Tera Guru

Hi Viji,

 

Short answer first: there is no out-of-the-box VIT equivalent of a Change Task / Problem Task. Vulnerability Response does not ship a sub-task table for a Vulnerable Item, and Remediation Tasks are a different concept — they group VITs for an owner, they do not delegate work to other teams.

 

The pattern that works while keeping SLA ownership with the VIT owner is:

 

1. Keep the VIT exactly where it is. The VIT assignment group, remediation target/SLA and state stay with the accountable team for its whole life. Never reassign the VIT itself to a supporting team just because they owe you a piece of work — that is what breaks SLA reporting.

 

2. Delegate through linked ITSM tasks, recorded as Affected Tasks. For each supporting team, raise the task type that team already works in — a Change (with Change Tasks) for a firewall rule change, an Incident/Catalog Task for a patching or network action — assigned to that team with its own due date, and link it to the VIT via Affected Tasks. You are right that Affected Tasks are just the linking mechanism, but that is intentional: it lets each team work in its own process while the VIT remains the single source of truth for the vulnerability.

 

3. Drive closure from the VIT, not from the child tasks. Add a simple rule/process step: the VIT cannot move to Resolved/Closed until its linked Affected Tasks are complete, and have the supporting teams put their outcome in the linked task, not in the VIT work notes. The VIT owner reviews and closes — ownership of the SLA decision never moves.

 

4. Only go custom if reporting forces it. If you need hard SLA-style reporting per supporting team (breach per dependency, not just due dates), that is the one case where a small custom task table extending Task, with a parent reference to the VIT, is justified. Weigh it carefully: you inherit state models, notifications, workspace support and upgrade maintenance that the Affected Tasks + ITSM task route gives you for free.

 

So, in order of preference: linked ITSM tasks via Affected Tasks first, custom VIT Task table only if per-team SLA reporting is a firm requirement.

Hi, thanks for your inputs.

 

My understanding is that one approach would be to allow the VIT remediation teams to create a record in an appropriate task-extended table, link it back to the VIT, and assign it to the relevant team.

The key consideration would then be choosing an existing task table that fits the VIT use case. There are different task types and need to choose something relevant to Vul scope. Universal Task may also be worth exploring here. I haven't worked with it previously, so I'll need to look into whether it would be suitable for this scenario.

 

I also think there is an opportunity to automate the creation of these tasks based on information already available in the VIT. Requiring remediation teams to manually create and route a separate task for every VIT could introduce significant operational overhead. Automating that step, where possible, would make this model more practical.

kmohammed
Tera Guru

Hi Viji, thanks for following up - you're welcome, and yes, both points you raise are the right next steps to test.

 

On choosing an existing task table, I'd score the candidates against a short checklist before committing: (1) can the supporting team work it in the workspace/list they already use, (2) are the ACLs workable, so a firewall or network engineer can update it without needing full VR roles or visibility of the whole VIT, (3) can it hold a live reference back to the VIT so reporting and closure checks stay simple, and (4) does it already have a sensible assignment, state and priority model you don't have to fight. Universal Task is worth a look for exactly the reason you suggest, but validate it against point (2) in a PDI first - it was not built specifically for VR, so check the scope and VIT visibility before assuming it fits.

 

On automating creation: agreed, this removes most of the overhead, with two guards. First, de-duplicate - before creating, check whether an open task of the same type already exists for that VIT and supporting group, otherwise re-scans and re-assignments will create repeats. Second, create at the right grain: automate per Remediation Task / group of related VITs rather than one task per VIT, otherwise high-volume vulnerabilities will generate thousands of child tasks nobody can manage. A Flow Designer flow triggered when the VIT (or its Remediation Task) is assigned, with template-style mapping of the vulnerability, CI and remediation target date into the child, plus a due date slightly before the VIT target, is a good pilot - start with one predictable pattern, e.g. firewall-rule VITs to the network security group, and expand once the pattern proves out.

 

Hope that helps you narrow the evaluation.