> ## 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 systems should be valid

> Checks that users with access to critical systems are authorized in Netlify.

Checks that users with access to critical systems are authorized in Netlify.

## About

When you connect Netlify to DSALTA, the platform syncs your users, roles, and access settings using read-only API access. DSALTA evaluates this control on every sync. If the requirement is not met, DSALTA activates this check.

## Why This Matters

Access tends to accumulate over time as roles change, leaving people with more 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 and ISO 27001.

## How to Fix

**Before you begin**

* Ensure the Netlify integration is connected so DSALTA has the current list of users.

**Validate user access**

1. In DSALTA, go to **Data Library → Access** and filter for **Netlify**.
2. Review each user's role and permission against their current job function.
3. For any user whose access is no longer appropriate, remove it in Netlify or adjust their role.
4. In DSALTA, mark each reviewed user as **In Scope** (valid) or **Not in Scope** (to be revoked), and record the reviewer.
5. Set a recurring access review schedule (quarterly is recommended).

Once all users have valid, documented access, DSALTA 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 Netlify 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 Netlify configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Netlify.
  </Accordion>
</AccordionGroup>