> ## 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 users with access to critical systems are authorized in Entra ID.

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

## About

When you connect Entra (Office 365) to DSALTA, the platform syncs your users and groups using read-only access to Microsoft Graph. DSALTA reads the app role assignments for your configured critical enterprise applications and verifies that every assigned principal is a member of the configured allowed groups. If a principal falls outside those groups, DSALTA activates this check.

## Why This Matters

Critical applications must be restricted to authorized users and groups only. 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 Entra (Office 365) integration is connected so DSALTA has the current list of users, groups, and app assignments.
* Confirm which enterprise applications are considered critical and which groups are allowed to access them.

**Restrict critical app access**

1. Go to the **Microsoft Entra admin center → Enterprise applications** and open the critical application.
2. Select **Users and groups**.
3. Remove any unauthorized user or group assignments.
4. Enforce **group-based assignments** so access is granted through the allowed groups rather than to individuals.
5. Set a recurring access review schedule (quarterly is recommended).

Once all principals assigned to critical applications are within the allowed groups, 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 Entra (Office 365) 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 Office 365 configuration?">
    No. DSALTA uses **read-only access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in the Microsoft Entra admin center.
  </Accordion>
</AccordionGroup>