> ## 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 Anthropic access is an active employee on the People page.

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

## About

When you connect Anthropic to DSALTA, the platform syncs your organization members using read-only API access. On every sync DSALTA compares the users on the Anthropic Access page against your **People** directory, matched by email within your organization, and activates this check when an Anthropic user does not map to an active employee.

<Note>
  Listing Anthropic members requires an **Admin API key** (`sk-ant-admin…`). If the Access page is empty, reconnect with an Admin key — a standard inference key exposes no members.
</Note>

## Why This Matters

Access to your organization's AI platform must be limited to current, authorized employees. Access tends to accumulate over time as roles change, leaving people with more than they need — which widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach a critical system is a core control in SOC 2 and ISO 27001, and governing access to AI systems is called out by the EU AI Act and the NIST AI RMF.

## How to Fix

**Before you begin**

* Ensure the Anthropic integration is connected with an **Admin API key** so DSALTA has the current list of members.

**Validate Anthropic access**

1. In the Anthropic Console, go to **Settings → Organization → Members** and remove anyone who is not a current employee.
2. In DSALTA, go to **People** and confirm each Anthropic user exists and is active.
3. In DSALTA, open **Data Library → Access** and filter for **Anthropic** to review each member against their current job function.
4. 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 every Anthropic 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 Anthropic integration is connected. You can also trigger a manual sync from **Integrations** in the sidebar.
  </Accordion>

  <Accordion title="Why is the Access list empty?">
    Listing organization members requires an **Admin API key** (`sk-ant-admin…`). A standard inference key connects but exposes no members. Reconnect with an Admin key created from the Anthropic Admin keys page.
  </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 Anthropic configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Anthropic.
  </Accordion>
</AccordionGroup>