Prioritize risk mitigation with Affected Product Categorization

[#1]

Affected Product Categorization helps you allocate resources and prioritize risk mitigation efforts by organizing vulnerabilities according to their root causes and affected products.

This categorization uses three fields that make it easier to analyze and address vulnerabilities across your network:

• Category: Indicates the root cause type, which can be Software, OS or Hardware.

• Affected product: Lists the products affected by the vulnerability.

• Vendor: Identifies the vendors affected by the vulnerability.

The Category and Affected product fields are displayed by default as columns in the All vulnerabilities view. The Vendor field can be added as an optional column.

You can use these fields to filter, group, and sort vulnerabilities.

Use case: Find all CVEs affecting Microsoft Edge

Let’s explore a practical example of how you might use Affected Product Categorization to prioritize risk actions and allocate resources efficiently.

For this example, imagine you want to start addressing vulnerabilities that affect Microsoft Edge.

1. In your Lansweeper Site, go to Risk insights > Active vulnerabilities.

2. Select Filters.

3. Select Add filter.

4. From the dropdowns, select Affected product - Contains - Edge.

5. Select Apply.

6. Select Unsaved view > Save as new…

7. Enter a name for the view, for example, Microsoft Edge.

8. Optionally, add a description.

9. Select Save as new.

A list of relevant CVEs and their information is displayed. From here, you can refine your analysis even further. For example:

• Select the Risk score column to bring the highest-risk vulnerabilities to the top.

• Select the Patchable column so that any CVEs with patches appear first in the list.

After prioritizing your list, you can learn more about each CVE and its affected assets:

1. Go to the CVE’s vulnerability page.

2. If patch information is available, scroll to the Patch information section and follow the link.

3. Select Affected assets to view the specific assets impacted by the vulnerability.

From there, you can begin planning and implementing remediation actions to resolve the vulnerabilities.