Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Security Operations
Table of Contents
Choose your release version
    Home Paris Security Incident Management Security Operations Vulnerability Response Understanding the Vulnerability Response application Change management for Vulnerability Response

    Change management for Vulnerability Response

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Change management for Vulnerability Response

    As an IT remediation owner, you can create and manage change requests (CHG) directly from vulnerability groups (VG) in the Vulnerability Response application. Change requests help you initiate and track change activities on your assets so that you can remediate your vulnerability groups and their corresponding vulnerable items.

    Change requests and the vulnerability workflow

    If you are not familiar with the Vulnerability Response application, for more information see Understanding the Vulnerability Response application.

    The following image illustrates the flow of information for Vulnerability Response, from integration (scanner) set up through automated triage and into investigation.

    Change requests and change management are part of the remediation process (Assess/Fix state) in the Vulnerability Response workflow shown in the following figure. During this phase, you might use change requests to initiate and track the remediation of vulnerabilities. You can create and manage change requests directly from the vulnerability group and list investigation and remediation tasks that include solutions for impacted assets for the configuration items (CI) in your CMDB.

    When to use change requests highlighted in overview.

    When to use change requests in vulnerability response

    As an IT remediation owner, you might create change requests from a vulnerability group if a manual and controlled process of any kind is required for modification or removal of supported configuration items (CIs) in your CMDB. Creating and managing change requests directly from a vulnerability group record helps you investigate and resolve vulnerabilities quickly. The VIs of a resolved vulnerability group can be scanned and verified during the next scheduled scan in your Now Platform and returned to the automated triage of the Vulnerability Response workflow. Manual interventions that might require change requests include the following examples:

    • A software patch, fix, or other task by IT that is required on vulnerable items prior to VG resolution.
    • You determine a subset of the vulnerable items in a vulnerability group requires further investigation or reassignment to another department.
    • You determine that a subset of vulnerable items in a VG with a large set of vulnerable items can be moved into a new vulnerability group.
    • You might associate a vulnerability group to an existing change request to avoid duplication of remediation tasks.

    Types of change requests for a VG

    The Vulnerability Response application utilizes the three types of service changes supported by the ITSM Change Management product on your Now Platform® instance — standard, emergency, and normal. The type of change you select determines which state model is invoked and the change process that must be followed. Change requests record the detailed information about the change, such as the reason of the change, the priority, the risk, the type of change, and the change category. See Change types.

    As a Vulnerability Response IT remediation owner, you have the following options for creating normal, standard, and emergency change requests directly from a vulnerability group:
    • You can create change requests that contain pre-populated information from the vulnerability group to streamline the process and save time.
    • You can associate a vulnerability group to an existing change request to avoid creating duplicate change requests that share similar information and vulnerable items.
    • Using a set of conditions, you can filter out a subset of vulnerable items and split a vulnerability group. The items that you select are automatically moved to a new VG.

    You can filter vulnerable items using values from any fields from a vulnerability group and apply the change request to only those items that match your filter criteria.

    Compatibility and system requirements

    Change management for the Vulnerability Response application is compatible with New York and Orlando v11.0, and the Paris family releases. The Vulnerability Response application is available on the ServiceNow Store.

    To verify an application is installed and activated on your instance, follow these steps.

    1. Navigate to Applications > System Applications > All Available ApplicationsAll.
    2. Search for the application you want. If not installed, click Install to install it.
    Related tasks
    • Create a change request from a vulnerability group
    • Associate a vulnerability group to an existing change request
    • Split a vulnerability group
    Related concepts
    • Vulnerability Response personas and granular roles
    • Vulnerability Response assignment rules overview
    • Vulnerability Response groups and group rules overview
    • Machine Learning solutions for Vulnerability Response
    • CI Lookup Rules for identifying configuration items from Vulnerability Response third-party vulnerability integrations
    • Creating CIs for Vulnerability Response using the Identification and Reconciliation engine
    • Discovered Items
    • Vulnerability Response group and vulnerable item states
    • Vulnerability Response calculators and vulnerability calculator rules
    • Vulnerability Response vulnerable item detections from third-party integrations
    • Vulnerability Response remediation target rules
    • Vulnerability Solution Management
    • Exception Management overview
    • Exception rules overview
    • False Positive overview
    • Software exposure assessment using Software Asset Management (SAM)
    • Domain separation and Vulnerability Response
    • State synchronization between change requests and vulnerability groups

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Change management for Vulnerability Response

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Change management for Vulnerability Response

      As an IT remediation owner, you can create and manage change requests (CHG) directly from vulnerability groups (VG) in the Vulnerability Response application. Change requests help you initiate and track change activities on your assets so that you can remediate your vulnerability groups and their corresponding vulnerable items.

      Change requests and the vulnerability workflow

      If you are not familiar with the Vulnerability Response application, for more information see Understanding the Vulnerability Response application.

      The following image illustrates the flow of information for Vulnerability Response, from integration (scanner) set up through automated triage and into investigation.

      Change requests and change management are part of the remediation process (Assess/Fix state) in the Vulnerability Response workflow shown in the following figure. During this phase, you might use change requests to initiate and track the remediation of vulnerabilities. You can create and manage change requests directly from the vulnerability group and list investigation and remediation tasks that include solutions for impacted assets for the configuration items (CI) in your CMDB.

      When to use change requests highlighted in overview.

      When to use change requests in vulnerability response

      As an IT remediation owner, you might create change requests from a vulnerability group if a manual and controlled process of any kind is required for modification or removal of supported configuration items (CIs) in your CMDB. Creating and managing change requests directly from a vulnerability group record helps you investigate and resolve vulnerabilities quickly. The VIs of a resolved vulnerability group can be scanned and verified during the next scheduled scan in your Now Platform and returned to the automated triage of the Vulnerability Response workflow. Manual interventions that might require change requests include the following examples:

      • A software patch, fix, or other task by IT that is required on vulnerable items prior to VG resolution.
      • You determine a subset of the vulnerable items in a vulnerability group requires further investigation or reassignment to another department.
      • You determine that a subset of vulnerable items in a VG with a large set of vulnerable items can be moved into a new vulnerability group.
      • You might associate a vulnerability group to an existing change request to avoid duplication of remediation tasks.

      Types of change requests for a VG

      The Vulnerability Response application utilizes the three types of service changes supported by the ITSM Change Management product on your Now Platform® instance — standard, emergency, and normal. The type of change you select determines which state model is invoked and the change process that must be followed. Change requests record the detailed information about the change, such as the reason of the change, the priority, the risk, the type of change, and the change category. See Change types.

      As a Vulnerability Response IT remediation owner, you have the following options for creating normal, standard, and emergency change requests directly from a vulnerability group:
      • You can create change requests that contain pre-populated information from the vulnerability group to streamline the process and save time.
      • You can associate a vulnerability group to an existing change request to avoid creating duplicate change requests that share similar information and vulnerable items.
      • Using a set of conditions, you can filter out a subset of vulnerable items and split a vulnerability group. The items that you select are automatically moved to a new VG.

      You can filter vulnerable items using values from any fields from a vulnerability group and apply the change request to only those items that match your filter criteria.

      Compatibility and system requirements

      Change management for the Vulnerability Response application is compatible with New York and Orlando v11.0, and the Paris family releases. The Vulnerability Response application is available on the ServiceNow Store.

      To verify an application is installed and activated on your instance, follow these steps.

      1. Navigate to Applications > System Applications > All Available ApplicationsAll.
      2. Search for the application you want. If not installed, click Install to install it.
      Related tasks
      • Create a change request from a vulnerability group
      • Associate a vulnerability group to an existing change request
      • Split a vulnerability group
      Related concepts
      • Vulnerability Response personas and granular roles
      • Vulnerability Response assignment rules overview
      • Vulnerability Response groups and group rules overview
      • Machine Learning solutions for Vulnerability Response
      • CI Lookup Rules for identifying configuration items from Vulnerability Response third-party vulnerability integrations
      • Creating CIs for Vulnerability Response using the Identification and Reconciliation engine
      • Discovered Items
      • Vulnerability Response group and vulnerable item states
      • Vulnerability Response calculators and vulnerability calculator rules
      • Vulnerability Response vulnerable item detections from third-party integrations
      • Vulnerability Response remediation target rules
      • Vulnerability Solution Management
      • Exception Management overview
      • Exception rules overview
      • False Positive overview
      • Software exposure assessment using Software Asset Management (SAM)
      • Domain separation and Vulnerability Response
      • State synchronization between change requests and vulnerability groups

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login