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

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

## About

When you connect Bitwarden to DSALTA, the platform syncs your organization members using read-only API access. On every sync DSALTA compares the members on the Bitwarden **Access** page against your **People** directory, matched by email within your organization. The check passes when every Bitwarden member is an active employee on the People page.

## Why This Matters

Access to the organization's password manager must be limited to current, authorized employees. A password manager holds the keys to many of your other systems, so a stale or unauthorized member is an outsized risk. Access tends to accumulate over time as roles change, widening your attack surface and breaking the principle of least privilege. Regularly validating who can reach critical systems is a core control in SOC 2, ISO 27001, and PCI DSS.

## How to Fix

**Before you begin**

* Ensure the Bitwarden integration is connected so DSALTA has the current list of members.

**Review Bitwarden access**

1. In Bitwarden, go to **Admin Console → Members** and remove anyone who is not a current employee.
2. In DSALTA, open **People** and confirm each Bitwarden member exists and is active.
3. For any member whose access is no longer appropriate, remove them in Bitwarden.

Once every member with Bitwarden access 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 Bitwarden 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 every Bitwarden member matches an active employee, 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 Bitwarden configuration?">
    No. DSALTA uses **read-only API access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Bitwarden.
  </Accordion>
</AccordionGroup>