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 Installation of Vulnerability Response and supported applications Optional Vulnerability Response setup tasks Configure the vulnerable item key

    Configure the vulnerable item key

    • 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

    Configure the vulnerable item key

    Configure the granularity of the vulnerable item (VI) key in the Vulnerability Response application to define what makes a vulnerable item (VI) in your organization.

    Before you begin

    Role required: admin

    Starting with v10.3, persona and granular roles are available to help you manage what users and groups can see and do in the Vulnerability Response application. For initial assignment of the persona roles in Setup Assistant, see Assign the Vulnerability Response persona roles using Setup Assistant. For more information about managing granular roles, see Manage persona and granular roles for Vulnerability Response.

    Key terms

    Configuration item (CI)
    An existing asset listed on your CMDB.
    Vulnerability
    A record of a known vulnerability imported from the National Institute of Standards and Technology (NIST), National Vulnerability Database (NVD), Common Vulnerabilities and Exposures (CWE), or third-party integrations with Vulnerability Response.
    Vulnerable item
    A vulnerable item is created when an imported vulnerability matches a configuration item in your CMDB.
    Detection
    A single, distinct occurrence of a vulnerability as reported by the scanners of your third-party integrations. Detections are imported and displayed on both the detection and the vulnerable item records in your instance. Also referred to as a Vulnerable Item Detection.

    By default, a vulnerable item is a unique combination of a configuration item (CI), a vulnerability, and an integration instance. To create vulnerable items with more granularity, add unique ports from vulnerable item detections to help you manage remediation of vulnerabilities at the level you feel is most effective for your organization.

    If you want to create vulnerable items with more granularity, configure the vulnerable item key so that it includes port. When Include port is enabled, vulnerable items are created by unique ports from vulnerable item detections.

    Choose an option from the following table to enable the Include port option.

    Table 1. Three scenarios for enabling the Include port option with the VI key for the first time
    If... Description
    One or more of the following conditions is true:
    • You are upgrading from a version of Vulnerability Response prior to v10.0 that did not support vulnerable item detections.
    • You are a new customer and you have no Vulnerability Response data (vulnerable items or vulnerable item detections) in your Now Platform® instance.
    • You have already deleted all your vulnerable item records and related data in your instance and you are ready to build all your Vulnerability Response data starting with a fresh import to include VIs distinguished by unique port.
    Enable Include Port.

    After Include port is enabled, imported detections create vulnerable items that include VIs distinguished by unique port starting with the next import.

    Both conditions are true:
    • You have v10.0 or later of Vulnerability Response and you have existing Vulnerability Response data (vulnerable items or vulnerable item detections) in your instance that you want to preserve.
    • You want to start creating new vulnerable items to include VIs distinguished by unique port.
    Enable Include port. Your existing detections and their associated vulnerable items will be preserved.

    After Include port is enabled, new detections create new vulnerable items that include VIs distinguished by unique port starting with the next import.

    Both conditions are true:
    • You have v10.0 or later of Vulnerability Response.
    • You have existing Vulnerability Response data (vulnerable items or vulnerable item detections), but you do not want to preserve your existing data, because you prefer to build your vulnerability data starting from a fresh import and you want to include VIs distinguished by unique port.
    1. Delete all your vulnerable item records and related data from your instance.
    2. Enable Include port.

      After Include port is enabled, new detections create new vulnerable items that include VIs distinguished by unique port starting with the next import.

    Note:

    If the Include port option is enabled, more than one vulnerable item may be created for a configuration item. For example, if a vulnerability exists for two ports on a configuration item, ports 80 and 443, two unique VIs are created, one for each port starting with the next import.

    Note: Be sure you want to create VIs to include VIs by unique ports before you enable this feature. Once you enable the VI key to include port, you must first delete your Vulnerability Response data before you can disable Include port and return to importing vulnerability data using the default VI key granularity, that is, where VIs are created for port but not distinguished by a unique port. For more information about deleting your vulnerability data, See Delete all your vulnerable item records and related data in Vulnerability Response.

    Procedure

    1. Navigate to Vulnerability Response > Administration > Configure VI granularity.

      The Last Updated field displays the date the VI key was last configured.

    2. Click the Include Port check box to enable it.
    3. Click Save.
      The Confirmation dialog is displayed.

      If you have no vulnerable item detection records in your instance, both vulnerable item detections and vulnerable items are created by unique port starting with your next import.

      If you have existing vulnerable item detections and vulnerable items in your instance, existing detections and associated vulnerable items will be preserved. New detections create new vulnerable that include VIs distinguished by unique port starting with the next import.

    What to do next

    Verify vulnerable items by port are displayed on the vulnerable item detection and vulnerable item records. For more information, see View Vulnerability Response vulnerable item detection data.

    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

      Configure the vulnerable item key

      • 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

      Configure the vulnerable item key

      Configure the granularity of the vulnerable item (VI) key in the Vulnerability Response application to define what makes a vulnerable item (VI) in your organization.

      Before you begin

      Role required: admin

      Starting with v10.3, persona and granular roles are available to help you manage what users and groups can see and do in the Vulnerability Response application. For initial assignment of the persona roles in Setup Assistant, see Assign the Vulnerability Response persona roles using Setup Assistant. For more information about managing granular roles, see Manage persona and granular roles for Vulnerability Response.

      Key terms

      Configuration item (CI)
      An existing asset listed on your CMDB.
      Vulnerability
      A record of a known vulnerability imported from the National Institute of Standards and Technology (NIST), National Vulnerability Database (NVD), Common Vulnerabilities and Exposures (CWE), or third-party integrations with Vulnerability Response.
      Vulnerable item
      A vulnerable item is created when an imported vulnerability matches a configuration item in your CMDB.
      Detection
      A single, distinct occurrence of a vulnerability as reported by the scanners of your third-party integrations. Detections are imported and displayed on both the detection and the vulnerable item records in your instance. Also referred to as a Vulnerable Item Detection.

      By default, a vulnerable item is a unique combination of a configuration item (CI), a vulnerability, and an integration instance. To create vulnerable items with more granularity, add unique ports from vulnerable item detections to help you manage remediation of vulnerabilities at the level you feel is most effective for your organization.

      If you want to create vulnerable items with more granularity, configure the vulnerable item key so that it includes port. When Include port is enabled, vulnerable items are created by unique ports from vulnerable item detections.

      Choose an option from the following table to enable the Include port option.

      Table 1. Three scenarios for enabling the Include port option with the VI key for the first time
      If... Description
      One or more of the following conditions is true:
      • You are upgrading from a version of Vulnerability Response prior to v10.0 that did not support vulnerable item detections.
      • You are a new customer and you have no Vulnerability Response data (vulnerable items or vulnerable item detections) in your Now Platform® instance.
      • You have already deleted all your vulnerable item records and related data in your instance and you are ready to build all your Vulnerability Response data starting with a fresh import to include VIs distinguished by unique port.
      Enable Include Port.

      After Include port is enabled, imported detections create vulnerable items that include VIs distinguished by unique port starting with the next import.

      Both conditions are true:
      • You have v10.0 or later of Vulnerability Response and you have existing Vulnerability Response data (vulnerable items or vulnerable item detections) in your instance that you want to preserve.
      • You want to start creating new vulnerable items to include VIs distinguished by unique port.
      Enable Include port. Your existing detections and their associated vulnerable items will be preserved.

      After Include port is enabled, new detections create new vulnerable items that include VIs distinguished by unique port starting with the next import.

      Both conditions are true:
      • You have v10.0 or later of Vulnerability Response.
      • You have existing Vulnerability Response data (vulnerable items or vulnerable item detections), but you do not want to preserve your existing data, because you prefer to build your vulnerability data starting from a fresh import and you want to include VIs distinguished by unique port.
      1. Delete all your vulnerable item records and related data from your instance.
      2. Enable Include port.

        After Include port is enabled, new detections create new vulnerable items that include VIs distinguished by unique port starting with the next import.

      Note:

      If the Include port option is enabled, more than one vulnerable item may be created for a configuration item. For example, if a vulnerability exists for two ports on a configuration item, ports 80 and 443, two unique VIs are created, one for each port starting with the next import.

      Note: Be sure you want to create VIs to include VIs by unique ports before you enable this feature. Once you enable the VI key to include port, you must first delete your Vulnerability Response data before you can disable Include port and return to importing vulnerability data using the default VI key granularity, that is, where VIs are created for port but not distinguished by a unique port. For more information about deleting your vulnerability data, See Delete all your vulnerable item records and related data in Vulnerability Response.

      Procedure

      1. Navigate to Vulnerability Response > Administration > Configure VI granularity.

        The Last Updated field displays the date the VI key was last configured.

      2. Click the Include Port check box to enable it.
      3. Click Save.
        The Confirmation dialog is displayed.

        If you have no vulnerable item detection records in your instance, both vulnerable item detections and vulnerable items are created by unique port starting with your next import.

        If you have existing vulnerable item detections and vulnerable items in your instance, existing detections and associated vulnerable items will be preserved. New detections create new vulnerable that include VIs distinguished by unique port starting with the next import.

      What to do next

      Verify vulnerable items by port are displayed on the vulnerable item detection and vulnerable item records. For more information, see View Vulnerability Response vulnerable item detection data.

      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