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 Vulnerability Response remediation overview Vulnerability Response remediation progress monitoring Remediate Vulnerability Response groups

    Remediate Vulnerability Response groups

    • 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

    Remediate Vulnerability Response groups

    The flexibility inherent in Vulnerability Response allows you to remediate vulnerabilities in whatever way suits your security organization.

    Before you begin

    Role required: v10.3 sn_vul.vulnerability.admin or sn_vul.admin (deprecated)

    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.

    About this task

    Once you are notified that a change request is resolved, move the vulnerability group state to Resolved and wait for the next scan. Rescans are triggered automatically by the third-party import schedule configured in the Setup Assistant.
    Note:

    If state synchronization is enabled, vulnerability groups are automatically moved to the Resolved state after a change request associated with a VG is implemented and in theReview state. See Change management for Vulnerability Response.

    Procedure

    1. Navigate to Vulnerability > Vulnerabilities > Vulnerability Groups.
    2. Click a vulnerable group record that is in the Open state.
      The Open state indicates that the record has not yet been worked on. The form displays:
      • Vulnerability group information
      • Group Configuration details
      • Notes
      • Associated vulnerable items
      • Task SLAs
      • Change Requests
    3. Perform your analysis of the group.
    4. When you are ready to start working on the record, choose any of the following options:
      OptionDescription
      If the vulnerable item poses a risk to your IT environment, create a CHG record and escalate the issue to Change Management team. Assign the group to the appropriate group or individual and click Create Change.
      If the vulnerable item poses a potential security risk to your organization, create a security incident record and escalate the issue to the Security Incident Response team. Click Create Security Incident.

      This button is displayed only when Security Incident Response is activated. A business impact calculation is applied, the incident is assigned, and the security incident is created.

      After you create a change request, the appropriate record appears in the Change Requests related list on the Vulnerability Group form.
    5. If you determine that the issue is of low risk and can be deferred, click Close/Defer.
      For instructions, see Defer a vulnerability group.
    6. If you determine that the issue can be immediately closed without further analysis, click Close/Defer.
      For instructions, see Close a vulnerability group.
    7. A third-party integration scheduled job automatically updates and scans records at a set interval. The vulnerable items are scanned at the next scheduled date and time. Alternatively, you can manually initiate a vulnerability scan using the Scan for Vulnerabilities related link.

      If the scan again finds the vulnerability on the configuration item and does not mark it Fixed, the vulnerable item returns to the Under Investigation state. Contact IT Operations to reopen the change request.

      If the scan does not find the vulnerability and returns that the vulnerable item has been marked Fixed, the vulnerable item transitions to the Closed-Fixed state and is closed during import.

      Only when all vulnerable items in a group are in the Closed-Fixed state, does the vulnerability group close automatically. Vulnerability groups with vulnerable items in Closed states other than Fixed must be closed manually.

    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

      Remediate Vulnerability Response groups

      • 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

      Remediate Vulnerability Response groups

      The flexibility inherent in Vulnerability Response allows you to remediate vulnerabilities in whatever way suits your security organization.

      Before you begin

      Role required: v10.3 sn_vul.vulnerability.admin or sn_vul.admin (deprecated)

      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.

      About this task

      Once you are notified that a change request is resolved, move the vulnerability group state to Resolved and wait for the next scan. Rescans are triggered automatically by the third-party import schedule configured in the Setup Assistant.
      Note:

      If state synchronization is enabled, vulnerability groups are automatically moved to the Resolved state after a change request associated with a VG is implemented and in theReview state. See Change management for Vulnerability Response.

      Procedure

      1. Navigate to Vulnerability > Vulnerabilities > Vulnerability Groups.
      2. Click a vulnerable group record that is in the Open state.
        The Open state indicates that the record has not yet been worked on. The form displays:
        • Vulnerability group information
        • Group Configuration details
        • Notes
        • Associated vulnerable items
        • Task SLAs
        • Change Requests
      3. Perform your analysis of the group.
      4. When you are ready to start working on the record, choose any of the following options:
        OptionDescription
        If the vulnerable item poses a risk to your IT environment, create a CHG record and escalate the issue to Change Management team. Assign the group to the appropriate group or individual and click Create Change.
        If the vulnerable item poses a potential security risk to your organization, create a security incident record and escalate the issue to the Security Incident Response team. Click Create Security Incident.

        This button is displayed only when Security Incident Response is activated. A business impact calculation is applied, the incident is assigned, and the security incident is created.

        After you create a change request, the appropriate record appears in the Change Requests related list on the Vulnerability Group form.
      5. If you determine that the issue is of low risk and can be deferred, click Close/Defer.
        For instructions, see Defer a vulnerability group.
      6. If you determine that the issue can be immediately closed without further analysis, click Close/Defer.
        For instructions, see Close a vulnerability group.
      7. A third-party integration scheduled job automatically updates and scans records at a set interval. The vulnerable items are scanned at the next scheduled date and time. Alternatively, you can manually initiate a vulnerability scan using the Scan for Vulnerabilities related link.

        If the scan again finds the vulnerability on the configuration item and does not mark it Fixed, the vulnerable item returns to the Under Investigation state. Contact IT Operations to reopen the change request.

        If the scan does not find the vulnerability and returns that the vulnerable item has been marked Fixed, the vulnerable item transitions to the Closed-Fixed state and is closed during import.

        Only when all vulnerable items in a group are in the Closed-Fixed state, does the vulnerability group close automatically. Vulnerability groups with vulnerable items in Closed states other than Fixed must be closed manually.

      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