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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Create policies for Scan Engine

# Create policies for Scan Engine {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Policies let you determine how specific definition findings appear on analytics dashboards; you can ignore them completely or place them in a prioritized view.

## Before you begin

Role required: admin

You can choose to create policies that label these definition findings as:

* Acceptable as is: Findings remain in the Open Findings table but are excluded from dashboard metrics, health score calculations, and prioritization views. They aren't automatically closed.
* Prioritize: Findings will appear in the Prioritized findings module on analytics dashboards.

{#working-policies-scan-engine__ul_l4j_qrk_hhc}  
Note:  
Policies match findings based on the Definition field. When creating a policy from a finding, the policy automatically references that definition and will apply to all future findings from the same definition.

## Procedure

1. Navigate to AllImpactPlatform HealthOpen Findings.
2. Select the short description for a finding to open the record to assign a policy.
3. In the Related Links section, select Create a policy for this finding.
4. Set the following fields to configure the policy.  
   {#working-policies-scan-engine__table_ot3_tqp_zjc__entry__2}

   | Field | Description |
   |-|-|
   | Number | Auto-generated ID for the policy. |
   | Active | Enable the policy to display in the Finding Policies page (ALL \> Impact \> Platform Health \> Finding Policies). |
   | Status | Select one of the following: * None: The policy is defined but not currently affecting findings * Acceptable as is: Exclude findings from metrics * Prioritize: Highlight the finding in dashboards {#working-policies-scan-engine__ul_umh_hrp_zjc} |
   | Order | Policies are evaluated in order lowest to highest. The first policy that matches a finding is applied; subsequent policies aren't evaluated for that finding. Lower order values have higher priority. |
   | Reason for policy | Description of why the policy was created. |
   [ ]

   {#working-policies-scan-engine__table_ot3_tqp_zjc}
5. Select Submit.  
   When a policy is active, findings matching its criteria display its name in their Policy field. View all findings affected by a policy through the policy record's Findings related list, or navigate to ALL \> Impact \> Platform Health \> Finding Policies to manage all policies.

*[\>]: and then