Mapping vulnerability scan results to a server environment

This use case demonstrates how to map server assets and vulnerabilities detected in a vulnerability scan to the servers and remediation content you are managing with TrueSight Server Automation. This mapping process is a prerequisite before you can use TrueSight Vulnerability Management to correct any vulnerabilities revealed in the scan.

This topic includes the following sections:

The following video demonstrates how to use TrueSight Vulnerability Management to map server assets and vulnerabilities detected in a scan to servers and remediation content managed with TrueSight Server Automation.

 https://youtu.be/7pln8tFNLZs

Introduction

This use case describes how to associate servers included in a vulnerability scan (known in TrueSight Vulnerability Management as assets) to servers managed with TrueSight Server Automation (known as endpoints). It also describes how to associate vulnerabilities identified in the vulnerability scan to remediation content that is available through TrueSight Server Automation. This process of associating—or mapping—must occur before you can perform any remediation based on a vulnerability scan. 

TrueSight Vulnerability Management can perform an automatic mapping of assets based on their DNS server and IP address. However, after auto-mapping some assets may remain unmapped. When that occurs, you can manually find endpoints in your managed environment and associate them with assets in the vulnerability scan.

TrueSight Vulnerability Management can also perform an automatic mapping of vulnerabilities to patches in TrueSight Server Automation patch catalogs. Mapping is based on the Common Vulnerabilities and Exposures (CVE) number. Only patches can be auto-mapped. Vulnerabilities requiring other types of remediation content must be manually mapped.

After assets and vulnerabilities are mapped, you can examine the Security Dashboard and the Operator Dashboard and then create a Remediation operation that corrects server vulnerabilities. That process is described in Using TrueSight Server Automation to remediate server issues detected in a vulnerability scan.

What do I need to get started?

  • You must have a user ID that can access and use TrueSight Vulnerability Management. 
  • You must have the results of a vulnerability scan in an XML format that can be imported into TrueSight Vulnerability Management.  If you have access to a vulnerability management system, such as Qualys, Nessus, or Rapid7, you can export the results to XML. For more information, see Importing scan files.

How to map vulnerability scan results

 ProcedureExample screen
1

Using TrueSight Vulnerability Management, import a scan file exported from a vulnerability scanning product and automatically map assets in the scan to endpoints (that is, servers) managed in TrueSight Server Automation. Auto-mapping matches the IP address and domain name server (DNS) of assets in the vulnerability scan to servers managed by TrueSight Server Automation.

  1. Select TrueSight Vulnerability Management > Import.
  2. From Select Vendor, choose the type of vulnerability management system used to create the scan file you want to import.
  3. In Scan Report, click Browse and navigate to a scan file you want to import. The file must be in an XML format.
    Note that exports from Nessus must have a file ending of .nessus.
    Optionally, you can also choose filters that are applied during the import, but in this example we accept the default values.
  4. NEW IN 3.0.01 In IP Address (CIDR Format), specify the IP addresses in the Classless Inter-Domain Routing (CIDR) format, for which you want to import data. From the scan file, data only for the servers that belong to the specified IP address range is imported. Default value of this option is 0.0.0.0/0, which imports data for all the assets from the scan file.

  5. Select the file and click Import Scan.

2

To check the status of the import, click Activity Status, in the menu bar at top right.

A window lists long running activities, such as scan imports, and shows their status. If the import is successful, its status says Successful.

3

 

 

For assets that remain unmapped after auto-mapping, you can perform a manual mapping procedure.

  1. Select TrueSight Vulnerability Management > Assets to display a list of assets. 
  2. For Security Groups, select a group that you want to use while mapping devices. In this case we select BLAdmins.
    The security group must have permissions to access the servers you want to use for mapping in TrueSight Server Automation. 
  3. Select one or more assets that require mapping.
    If necessary, use the filtering capability at the top of each column to find assets. For example, if you are looking for assets with names that include the string "win10," enter win10 in the filter box at the top of the Scan Host column.
  4. At top right, click the  Actions  menu and select Map.
    The Map Endpoint to Scanned Hosts page opens. It provides two tabs: Selected Scanned Hosts and Endpoints. The asset(s) you selected in the previous step are listed on the Selected Scanned Hosts tab.

Select one or more assets that need mapping.


When you click Map, the asset(s) you selected appear on the Map Endpoint to Scanned Hosts page.

4

Specify a server managed in TrueSight Server Automation that should map to the selected asset(s).

  1. Select an asset on the Selected Scanned Hosts tab and click the Endpoints tab. 
  2. Use the text search or browse capabilities on this tab to find the server to be mapped.
    Click here to display a page that describes search and browse capabilities. 

  3. Select a server to map to the asset selected on the Selected Scanned Hosts tab and click Save.
    A message says that mapping has occurred. The Assets page shows the name and IP address of the mapped server in TrueSight Server Automation.
    In some situations you may need to map multiple scanned assets to a single server. Or, you may need to map a single asset to multiple server. Click here for details.
  4. Use the same procedure to map additional assets.

Select an asset to map and then click the Endpoints tab.


Assets page shows name of mapped endpoint.

5

Display a list of vulnerabilities in the vulnerability scan. Then perform auto-mapping, which  matches any vulnerabilities that can be corrected by patches with patches that already exist in TrueSight Server Automation patch catalogs.

  1. Select TrueSight Vulnerability Management > Vulnerabilities to display the list of vulnerabilities.
  2. Click Auto-map to perform an automatic mapping of vulnerabilities identified in the vulnerability scan to patches in TrueSight Server Automation patch catalogs.

6

For vulnerabilities that remain unmapped after auto-mapping, perform a manual mapping procedure. You can match vulnerabilities to any type of depot content that can be used for remediation, such as BLPackages, software packages, and NSH scripts.

  1. Select a vulnerability that requires mapping.
    If necessary, use the filtering capability at the top of each column to find vulnerabilities. For example, you can filter by name or severity.
    In this example, we filtered by Mapping Status and Vulnerability ID.
  2. At right, click the Actions menu in the highlighted row and select Map.
    The Map Remediation to Vulnerability page opens.

7

Using the Search and Browse tabs, select a remediation package. After selecting a rule, click Save.

Click here to see a page with detailed instructions for using using search and browse capabilities.

8

Define rules that apply when you later deploy the remediation content to target servers. This capability is typically used to deploy one remediation content item to a certain type of target, such as Windows servers, and another type of remediation content to another type of target, such as Red Hat servers.

  1. Click Use Target Rules.
    A set of options appear that you can use to establish rules for deploying the remediation content.
  2. Select Any or All to specify whether all the criteria you establish must be met for deployment or any one of the criteria is sufficient.
    In this example, we select Any
  3. For OS, enter text that identifies the OS type. For example, we enter Windows.
  4. Click Add Criteria.
    A new row appears for defining another criteria. 
  5. In the first field, select OS Platform. In the last field, enter a text string that identifies the platform. We enter x86_64 to indicate this package should be deployed to 64-bit systems.
  6. To set another set of target rules, select another remediation content item and click . Then, repeat the previous steps to define a new set of target rules for the selected content.

9

Click Save.

A message says that mapping has occurred. The Vulnerabilities page shows the remediation content that was selected and the remediation type, such as a BLPackage or Windows Hotfix. If you have a long list of vulnerabilities, use the Remediation Type filter and the Mapping Status filter (at the top of the page) to find the vulnerability you just mapped. 

Repeat the same procedure to map additional vulnerabilities to remediation packages.

Wrapping it up

In this topic you used TrueSight Vulnerability Management to perform all the preliminary mapping necessary to remediate network vulnerabilities detected by an external vulnerability management system, such as Qualys, Nessus, or Rapid7.

Where to go from here

After all necessary mapping is complete, you can use the Security Dashboard  and Operator Dashboard to analyze the vulnerabilities detected in a scan. Then you can use the Operator Dashboard to create a Remediation operation that corrects vulnerabilities in your server environment. Another use case describes that process.

Was this page helpful? Yes No Submitting... Thank you

Comments