> ## 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.

# Inactive user accounts should be disabled

> Checks that Nebius tenant user accounts in a non-active state are disabled or removed.

Checks that Nebius tenant user accounts in a non-active state are disabled or removed.

## About

When you connect Nebius to DSALTA, the platform lists your tenant user accounts using read-only IAM access. DSALTA flags any account that is not in an **ACTIVE** state but remains provisioned. DSALTA evaluates this control on every sync.

## Why This Matters

Lingering inactive accounts widen the attack surface and break least-privilege — a dormant account is an unmonitored door into your cloud infrastructure. Timely removal of inactive access is expected by frameworks including SOC 2, ISO 27001:2022, NIST CSF, and CIS.

## How to Fix

**Before you begin**

* Review the tenant user accounts flagged as non-active in the DSALTA check details.
* Ensure you have **tenant admin** rights in the Nebius Console.

**Disable inactive accounts**

1. In the **Nebius Console**, go to **IAM → Users**.
2. Locate each account flagged as inactive.
3. Suspend or delete the account so it can no longer authenticate.
4. Remove the account from any groups or role bindings it no longer needs.

Once all non-active user accounts are disabled or removed, 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 Nebius 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 Nebius configuration?">
    No. DSALTA uses **read-only IAM access** and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Nebius.
  </Accordion>
</AccordionGroup>