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 New York Security Incident Management Security Operations Vulnerability Response Understanding the Vulnerability Response application Introduction to False Positive

    Introduction to False Positive

    • 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

    Introduction to False Positive

    A false positive is a condition wherein the scanner reports that a vulnerability exists in the system, but in reality there is no vulnerability. There can be multiple reasons like incorrect classification, improper logic or algorithm in the scanner. The remediation owner can mark vulnerable items (VIs) or vulnerability groups (VGs) as false positives.

    Life cycle of a false positive

    Meaning of false positive

    The scanner sometime gives a warning, when in reality there is no vulnerability. For example, if a configuration item has been decommissioned but the scanner is still raising an issue related to it, mark it as a false positive.

    Marking as a false positive

    For details on marking a VI or VG as a false positive, see Mark as a false positive.

    Working with the false positive
    Once a VI or VG is marked as a false positive, the state is updated to Closed and the substate is changed to False Positive. The following actions can be performed:
    • Reopen
    • Delete
    • Update the date in the Until field. This date is then used as the expiry date for the false positive.
    Note: If not approved, the VI or VG reverts to its previous state.
    Approving a false positive

    The approver can approve the false positive from their approval workflow.

    Reopening a false positive

    A VI or VG in a false positive substate can be reopened anytime.

    Tracking a false positive

    Use the State Change Approvals section to track the status of the false positive. Once approved, the state of the VI or VG is updated to Closed and the reason is False Positive.

    Expiry of a false positive

    Only the false positive approver can set an Until date for the false positive, for the VI or VG to expire. Also, only false positives for which the approver has provided an Until date can expire. This date can be provided after the false positive is approved.

    A false positive without an Until date is a permanent false positive. After the false positive expires, the state of the VI or VG moves back to Open.

    False positive approval process

    Life cycle of a false positive

    The approval process is automatic if all VIs pass the next scan. The VIs auto-close regardless of the current state. The VIs or, where applicable, the VG State fields change to Closed with the substate Fixed.

    Related concepts
    • Vulnerability Response personas and granular roles
    • Vulnerability Response assignment rules overview
    • Vulnerability Response groups and group rules overview
    • Vulnerability groups and group rules overview (Prior to v10.0)
    • CI Lookup Rules for identifying configuration items from Vulnerability Response third-party vulnerability integrations
    • 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
    • Introduction to Exception Management
    • Change management for Vulnerability Response
    • Software exposure assessment using Software Asset Management (SAM)
    • Domain separation and Vulnerability Response

    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

      Introduction to False Positive

      • 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

      Introduction to False Positive

      A false positive is a condition wherein the scanner reports that a vulnerability exists in the system, but in reality there is no vulnerability. There can be multiple reasons like incorrect classification, improper logic or algorithm in the scanner. The remediation owner can mark vulnerable items (VIs) or vulnerability groups (VGs) as false positives.

      Life cycle of a false positive

      Meaning of false positive

      The scanner sometime gives a warning, when in reality there is no vulnerability. For example, if a configuration item has been decommissioned but the scanner is still raising an issue related to it, mark it as a false positive.

      Marking as a false positive

      For details on marking a VI or VG as a false positive, see Mark as a false positive.

      Working with the false positive
      Once a VI or VG is marked as a false positive, the state is updated to Closed and the substate is changed to False Positive. The following actions can be performed:
      • Reopen
      • Delete
      • Update the date in the Until field. This date is then used as the expiry date for the false positive.
      Note: If not approved, the VI or VG reverts to its previous state.
      Approving a false positive

      The approver can approve the false positive from their approval workflow.

      Reopening a false positive

      A VI or VG in a false positive substate can be reopened anytime.

      Tracking a false positive

      Use the State Change Approvals section to track the status of the false positive. Once approved, the state of the VI or VG is updated to Closed and the reason is False Positive.

      Expiry of a false positive

      Only the false positive approver can set an Until date for the false positive, for the VI or VG to expire. Also, only false positives for which the approver has provided an Until date can expire. This date can be provided after the false positive is approved.

      A false positive without an Until date is a permanent false positive. After the false positive expires, the state of the VI or VG moves back to Open.

      False positive approval process

      Life cycle of a false positive

      The approval process is automatic if all VIs pass the next scan. The VIs auto-close regardless of the current state. The VIs or, where applicable, the VG State fields change to Closed with the substate Fixed.

      Related concepts
      • Vulnerability Response personas and granular roles
      • Vulnerability Response assignment rules overview
      • Vulnerability Response groups and group rules overview
      • Vulnerability groups and group rules overview (Prior to v10.0)
      • CI Lookup Rules for identifying configuration items from Vulnerability Response third-party vulnerability integrations
      • 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
      • Introduction to Exception Management
      • Change management for Vulnerability Response
      • Software exposure assessment using Software Asset Management (SAM)
      • Domain separation and Vulnerability Response

      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