Skip to main content
Checks that everyone with SentinelOne access is an active employee on the People page.

​
About

Access to the endpoint security console must be limited to current, authorized employees. On every sync DSALTA compares the users on the SentinelOne Access page against your People directory, matched by email within your organization. The check passes when every SentinelOne user is an active employee on the People page.

​
Why This Matters

The endpoint security console is a sensitive system — the people who can reach it can see and influence how your fleet is protected. Access tends to accumulate over time as roles change, leaving people with more than they need and widening your attack surface. Regularly validating who can reach critical systems is a core control in SOC 2, ISO 27001, HIPAA, and NIST CSF.

​
How to Fix

Before you begin
  • Ensure the SentinelOne integration is connected so DSALTA has the current list of console users.
Review SentinelOne access
  1. In SentinelOne, go to Settings → Users, review the console users, and remove anyone who is not a current employee.
  2. In DSALTA, open People and confirm each SentinelOne user exists and is active.
Once every user with SentinelOne 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

This check runs automatically every 24 hours while the SentinelOne integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once every SentinelOne user maps to an active employee, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in SentinelOne.