Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Use Access Findings

You can use Access Findings to view the potential vulnerabilities that were discovered the last time access checks ran on your ServiceNow AI Platform.

Before you begin

Role required: admin

Procedure

  1. Navigate to All > Access Management > Access Findings.

    Note: You can also select Access Findings from the Access Management Console.

  2. Select Access Findings from the options on the left to view the current findings.

    The page provides the following details:

FieldDescription
NumberThe record of the finding itself. Select this to view more details.
CheckThe Access Check that found the issue.
PriorityThe severity level of the finding. Severity is divided into the following priority levels:- 1 - Critical - 2 - High - 3 - Moderate - 4 - Low
StatusThe current status of the finding.
SourceWhere the issue was found in your instance.
CreatedWhen the finding was created.
The Findings list page is the primary workspace for triaging access findings.

-   **Status tabs** -- Toggle between Open, Muted, and Resolved views. Each tab shows a count of findings in that state.
-   **Filtering** -- Filter by priority level, check type, or other finding attributes.
-   **Sorting** -- Sort by priority, date detected, status, or other columns.
-   **Export** -- Export findings for offline review or reporting.
  1. Select each record to learn more about the vulnerability and detailed resolutions, including:

    • Finding description and affected resource
    • Priority level and the check that detected it
    • Remediation guidance with documentation link
    • Related Security Tasks
    • Select any of the following remediation actions for managing the finding lifecycle:
ActionDescription
Mark as resolvedMark a finding as resolved when the underlying misconfiguration has been corrected. Resolved findings move to the Resolved status tab. The system verifies resolution on the next scan -- if the misconfiguration is no longer detected, the finding stays resolved. If the misconfiguration is still present, the finding is automatically reopened.
ReopenRestore a resolved finding to Open status. Use this if a resolved finding requires further investigation or if the remediation was incomplete.
MuteSuppress a finding from the active findings list. Use this for known exceptions or accepted risks that do not require remediation. Muted findings: - Move to the Muted status tab - Are excluded from the open findings count and the Overview donut chart - Remain visible in the Muted tab for audit purposes - Are not affected by auto-resolve or auto-reopen
UnmuteRestore a muted finding to open status. Use this when a previously accepted risk needs to be re-evaluated.
Create task

Create a Security Task (sn_vsc_security_task) from the finding to route remediation through your standard workflow.

  • Task type is auto-populated based on the finding
  • Description is auto-populated with finding details
  • The created task is shown on the finding detail page
  • The related finding is shown on the task record
  • Multiple tasks can be created from the same finding if remediation requires coordination across teams