reassign Vulnerable item to another assignment group?

[kris29]

Hi,

I wonder what happens if a vulnerable items were automatically assigned to the wrong assignment group during import?

What type of functionality should be implemented or configured when a Vulnerable item needs to be reassigned to another assignment group?

[Chris McDevitt · Accepted solution]

That is a different question altogether. 🙂

It depends on your organization. I have seen a few different approaches.

1. Place a button on the form to re assigns it to a central team.

2. Limit the groups that they can reassign it to (Lots of different ways)

3. Just let the remediation owner reassign the item.

In any event, you need to add a "reassignment count" field to the items to see how often this is happening. (Model it off of the one on the Incident table)

Best practices:

• Track the number of reassignments
• Understand why they are being reassigned and adjust your rules according
• Make sure the teams know that the reassignments are being tracked
• Reduces gaming the system
• Builds confidence in the system if you are proactively reviewing reassignments for process improvement 

[cmcclendon]

Flashback 2016!

Incident reassignment gaming taking place. Assignment group members caught reassigning incidents the day before SLAs are breached!

[Chris McDevitt]

@cmcclendon  You know... I really do want to think the best of people. 🙂 

[ntonetta etta]

Manually, using one of three options, to add vulnerable items to the group.
1) Add vulnerable items to the group by hand.

2) Use a Condition filter that automatically adds vulnerable items to the vulnerability group

3) Use a Filter group that automatically adds vulnerable items to the vulnerability group.

Note: Manually added vulnerable items are not automatically removed from vulnerability groups by vulnerability group rules or group conditions.

MyTHDHR.com