--- 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 --- # Understand scan results and findings # Understand scan results and findings {#ariaid-title1} * Release version: Australia * * Updated June 1, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Understand scan results and findings After running a scan in your ServiceNow instance, you can monitor its progress in real-time and review the completed scan results. This enables you to identify issues, understand their severity, and take appropriate remediation actions to maintain compliance and system integrity. Show full answer Show less Reviewing scan results involves two main steps: viewing the scan progress and results, and working with individual findings to resolve or manage them. ## Working with Scan Results and Findings * **View scan results:** Track active scans or open completed scan records to check status, duration, and batch progress. * **Work with findings:** Open specific findings to understand their enforcement level and impact, then apply fixes or submit exceptions. ## Evaluation of Findings Each finding is assessed using two key dimensions to help prioritize remediation: * **Enforcement Level:** Determines the required system action and if exceptions are allowed. Levels include ACT, RECOMMEND, SUGGEST, and REVIEW. * **Impact to Instance (Risk Rating):** A score from 1 (minimal) to 10 (critical) measuring the risk of leaving the issue unresolved within each enforcement level. The enforcement level dictates the action priority, while the impact rating orders findings within that level for remediation. ## Enforcement Levels and Actions | Level | Impact Range | Description | Enforcement Behavior | |-|-|-|-| | **ACT** | 1--10 | Critical issues that can break functionality, cause security vulnerabilities, or block upgrades. | Record cannot be saved until fixed. No exceptions allowed. Overrides require admin rights or disabling the definition. | | **RECOMMEND** | 1--10 | High severity issues potentially degrading performance, stability, or security. | Record cannot be saved until fixed or an exception with formal approval is submitted. | | **SUGGEST** | 1--10 | Moderate issues related to optimization, maintainability, or best practices. | Does not block progress; address during future development cycles. Option to exclude suggestions from display. | | **REVIEW** | 1--10 | Low impact, informational findings (e.g., unused fields). | Informational only; no blocking of saves. Monitor and optionally fix later. | ## Prioritization Guidance Enforcement level takes precedence over impact rating when prioritizing issues. For example, an ACT level finding with an impact of 1 is addressed before a RECOMMEND level finding with an impact of 10. ## Practical Implications for ServiceNow Customers * Critical issues (ACT) must be resolved immediately to proceed with saving records, ensuring system stability and security. * High severity issues (RECOMMEND) also require resolution or approved exceptions before saving to maintain compliance. * Moderate and low severity issues (SUGGEST and REVIEW) provide guidance for improvements without blocking development, allowing teams to optimize and clean up over time. * Understanding enforcement levels and impact ratings helps teams balance addressing critical vulnerabilities while maintaining development velocity. After a scan runs, you can monitor its progress in real-time, review the completed results, and then work with the findings to resolve issues in your instance. Reviewing scan results and acting on findings is a two-phase process. 1. View scan results: Monitor an active scan or open a completed scan record to see its status, duration, and batch progress. See [View scan results for Scan Engine](https://servicenow-prod.fluidtopics.net/igA7dvkRF2fOyKPBB2PuWQ "You can view scans in real-time as they run or after they're completed. "). 2. Work with findings: Open individual findings from the scan record to understand their enforcement level and impact, then apply fixes or submit exceptions for review. See [Use Real-time prevention monitoring while coding](https://servicenow-prod.fluidtopics.net/2u12Mrp4pctDa9dzpV15hw "As you write and save code, the Scan Engine detects violations in real-time and displays findings inline. You can then generate an AI-suggested fix before committing your changes."). {#understand-scan-engine-results-findings__ol_scan_results_findings_flow} ## How findings are evaluated {#understand-scan-engine-results-findings__section_enforcement_overview} Every finding in your instance is evaluated along two critical dimensions to help your team prioritize remediation efforts and maintain compliance standards. Level of finding (enforcement level) : The enforcement behavior is determined whether the system blocks an action, issues a warning, or provides informational guidance. Enforcement levels are ACT, RECOMMEND, SUGGEST, and REVIEW. The enforcement level determines the action the system will take and whether exceptions are available. Impact to instance (risk rating) : The business and technical risk of leaving the finding unresolved, rated from 1 (minimal) to 10 (critical) within each enforcement level. Higher values indicate findings that should be addressed first within that level. : Impact ratings operate independently within each enforcement level and don't create a global 1--10 scale across all levels. These two dimensions work together, enforcement level determines what action is required, while impact rating determines the order in which findings should be addressed within that enforcement level. ## Enforcement levels and risk impact {#understand-scan-engine-results-findings__section_ks5_hbx_53c} Depending on the level of the definition, users may be required to fix a finding before saving a record. {#understand-scan-engine-results-findings__table_scan_findings__entry__4} | Level of finding | Impact to instance (typical) | Severity description | Enforcement behavior / recommended action | |:-:|:-:|:-|:-| | ACT | 1--10 | Critical issues that can break functionality, cause security vulnerabilities, or block upgrades. | * The record can't be saved until the code is fixed to meet the requirements in the definition. * No exception reason option is available. * An override requires admin-level rights or the disabling of the definition. {#understand-scan-engine-results-findings__ul_nrp_q2k_ljc} | | RECOMMEND | 1-10 | High severity issues that may degrade performance, stability, or security. Exceptions are allowed with approval. | * The record can't be saved until the issue is resolved or and exception reason is provided formal approval. * For more information, refer to [Submit exceptions for Scan Engine findings](https://servicenow-prod.fluidtopics.net/XfC4GOWTWryU6elLn_1IuQ "For Recommend level findings, developers can submit exception requests if they determine the finding should not be considered an issue to deter development."). {#understand-scan-engine-results-findings__ul_orp_q2k_ljc} | | SUGGEST | 1-10 | Moderate issues, often related to optimization, maintainability, or best practices. | * Address during future development cycle * Does not block progress * Prompts to check for a better solution, if one is available. * Select whether to Exclude suggestion finding, which hides Suggestion level findings messages from displaying. {#understand-scan-engine-results-findings__ul_ebk_4dr_v3c} | | REVIEW | 1-10 | Low impact, informational findings with minimal impact (i.e., unused fields or minor UI inconsistencies). | * Monitor and optionally fix during future development cycles. * Displays an informational message without blocking saves or creating finding records. | [Table 1. Scan Engine finding levels, risk, and enforcement behavior] {#understand-scan-engine-results-findings__table_scan_findings} Important: Impact rating applies independently to each enforcement level. An ACT 1 finding is always higher priority than a recommend 10 level finding, even though the numbers appear reversed. Enforcement level takes precedence over impact rating in prioritization. The 1--10 scale within each level allows granular severity differentiation while maintaining the enforcement hierarchy. ## Examples {#understand-scan-engine-results-findings__section_rkz_kcx_53c} These two metrics work together to help teams balance enforcement and risk prioritization, ensuring critical issues are addressed first while maintaining development velocity. * ACT level finding with impact to instance of 9: Critical and must be fixed immediately before proceeding. No exceptions. * SUGGEST level with impact to instance of 8: High-risk but does not block development. Should still be prioritized for remediation. {#understand-scan-engine-results-findings__ul_dhz_lcx_53c} **Related tasks** * [View scan results for Scan Engine](https://servicenow-prod.fluidtopics.net/igA7dvkRF2fOyKPBB2PuWQ "You can view scans in real-time as they run or after they're completed. ")