> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# User access to Critical System should be valid

> Checks that everyone with ServiceNow access is an active employee on the People page.

Checks that everyone with ServiceNow access is an active employee on the People page.

## About

DSALTA compares the users on the ServiceNow Access page against your People directory, matched by email within your organization. It passes when every ServiceNow user is an active employee on the People page. This check is platform-internal — it runs on synced ServiceNow user data and your People records, and re-evaluates on every sync.

## Why This Matters

Access to the ITSM platform must be limited to current, authorized employees. Access tends to accumulate over time as roles change, leaving people with more reach than they need. Excess access widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach critical systems is a core control in SOC 2, ISO 27001, HIPAA, and PCI DSS.

## How to Fix

**Before you begin**

* Ensure the ServiceNow integration is connected so DSALTA has the current list of users.
* Ensure you have access to review users in ServiceNow.

**Review ServiceNow access**

1. In **ServiceNow**, go to **User Administration → Users**, review the users, and deactivate anyone who is not a current employee.
2. In **DSALTA**, go to **People** and confirm each ServiceNow user exists and is active.

Once every ServiceNow user is an active employee on the People page, DSALTA retrieves the change on the next sync and sets the check status to **Passing**.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How often does this check run?">
    This check runs automatically every 24 hours while the ServiceNow integration is connected. You can also trigger a manual sync from **Integrations** in the sidebar.
  </Accordion>

  <Accordion title="What happens if it keeps failing?">
    A failing check appears in your **Data Library → Tests** dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
  </Accordion>

  <Accordion title="Can I exclude this check?">
    Yes. If it does not apply to your environment, mark it as **Not Applicable** with a justification. The exclusion is documented for auditors.
  </Accordion>

  <Accordion title="Does DSALTA change my ServiceNow configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in ServiceNow.
  </Accordion>
</AccordionGroup>