Investigating vulnerabilities

To investigate vulnerabilities for an impacted service

An operator or a site reliability engineer (SRE) can view the details of services impacted by vulnerabilities, assess the risks associated with these vulnerabilities, and quickly prioritize remediation.

1. On the BMC Helix AIOps console, click Risks and then click Vulnerabilities.
   
   
2. From the Top Impacted Services table, click a service to open the Service Details page and view the following details:
   
   
   • Risk Score
   • Number of critical vulnerabilities
   • Impacted assets
3. In the vulnerabilities section, view the following information:
   
   • Vulnerability name
   • CVE ID
   • Severity
   • CVSS Score: The CVSS V3 score is assigned by the NIST NVD.
   • Impacted assets: Click to view the details of impacted assets.
     
     
     • Asset name
     • Operating system
     • Remediation owner

     • SLA

       Important

       You can filter the list of impacted assets by entering the host name of a specific asset in the search box.

4. (Optional) Click and select the columns that you want to display in the Vulnerabilities section.
5. Continue with To investigate a vulnerability.

To investigate a vulnerability

An operator or a site reliability engineer (SRE) can view vulnerability details, such as the vulnerability summary, the CVSS score, and the number of impacted assets, and can assess the risks associated with these vulnerabilities to quickly prioritize remediation.

1. On the BMC Helix AIOps console, click Risks and then click Vulnerabilities.
   
2. From the Top Vulnerabilities table, click a vulnerability to open the Vulnerability Details page and view the following details:
   
   
   • If BMC HelixGPT is enabled, the following details are displayed:
     • A human-readable AI-generated summary of the vulnerability.
     • Best action recommendations, which is a list of suggested steps that can be used to remediate the vulnerability. Additionally, a BMC HelixGPT-driven wizard offers remediation automation code to accomplish individual steps on different platforms such as Ansible or .
   • Severity
   • CVE-ID
   • CVSS Score: The CVSS V3 score is assigned by the NIST NVD.
   • Impacted services
   • Impacted assets
3. In the impacted assets section, you can view the following information
   
   • Asset name
   • Operating system
   • Remediation owner
   • SLA
4. (Optional) Click and select the columns that you want to display in the Impacted Assets section.
5. Continue with To view best action recommendations.

To view best action recommendations for remediation

Best action recommendations are available if BMC HelixGPT is enabled. To enable BMC HelixGPT, contact BMC Support.

1. On the Vulnerability details page, review the AI-generated summary (short problem statement, brief summary, and detailed problem context) of the selected vulnerability.
   
2. In the Select OS field, select the appropriate operating system and version and click Generate Remediation.
   The Select OS field is populated with the operating systems linked to the affected assets. If multiple operating systems are listed in the field, select the appropriate operating system and version.
   The recommended steps to remediate the vulnerability are displayed.
   
3. (If available) Click Code wizard.
   For some manual steps, the Code wizard option is not available.
4. Select your preferred remediation target, such as Ansible or Powershell. The code is displayed based on your selection.
   BMC HelixGPT generates a code that can be used to run the recommended steps.
   

1. Click Copy to clipboard and use the code in your existing script to run the recommended remediation steps.
2. Close the code wizard.

3. Click Create change request to open a Change Request form in ; enter the relevant details; and submit the change request for approval.
   For more information, see Creating a change request.

   Important

   To be able to create a change request, as an administrator, install, subscribe to, and configure BMC Helix ITSM. For more information, see Setting up and going live.