---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/impact

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Using real-time prevention monitoring

# Using real-time prevention monitoring {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

When working with application or configuration file types, if the real-time scanning functionality is configured and active, the Scan Engine displays information for the findings.

Finding levels of Review and Suggest are shown in blue, while Recommend and Act are shown in red. These information windows can contain the following fields, depending on their severity.
{#use-real-time-prevention-monitoring__table_ydc_zvk_hhc__entry__2}

| Field | Description |
|-|-|
| Finding level | The severity level of the finding, as well as a brief description of the finding. |
| Details | Generally, the line number the finding occurred on. |
| Steps to resolve issue | Some suggested steps the developer can follow to resolve the finding. |
| Exception reason required | If the finding is at the Recommend level, this field reminds developers they can submit an exception for the issue if they believe it is not a finding. |
| Supporting documentation | * If the definition this finding applies to contains a Supporting Documentation link, it appears here as a hyperlink that opens in a new browser tab. * This information can be linked to documentation, knowledge base articles, FAQs, and more. {#use-real-time-prevention-monitoring__ul_zdc_zvk_hhc} |
| Impact | * Lists the finding's impact level and Impact to Instance for the associated definition. * The impact to instance is a number between 1 and 10, where 10 is the most impactful. {#use-real-time-prevention-monitoring__ul_b2c_zvk_hhc} |
[ ]

{#use-real-time-prevention-monitoring__table_ydc_zvk_hhc}

Using the information provided, you can do one of the following:

* Correct the issue. If the issue is corrected, the Scan Engine will not return a new finding notice.
* In the case of a Recommend level finding, submit an exception, then Update the page. See [Submit exceptions for the Scan Engine findings](https://servicenow-prod.fluidtopics.net/lZdsXjXSWUYfM7proUZI5g "For Recommend level findings, developers can submit exception requests if they feel the issue should not be considered a finding.").

{#use-real-time-prevention-monitoring__ul_k5z_2dl_hhc}

Real-time messaging enforcement can be disabled with the Scan Engine properties page. By disabling enforcement, users will see the messaging but will not be required to make corrections for Act and Recommend findings.

In addition, visibility of real-time messaging for certain users can also be configured with the Scan Engine properties page. You can limit the users that will receive real-time messaging to a specific group if necessary.

For more information, refer to [Configure Scan Engine properties](https://servicenow-prod.fluidtopics.net/dJMsPAzmxuEiFIbk9LPe9w "Configure the primary scanning capabilities and configuration options for scheduled, on-demand and real-time scans.").