Skip to main content

​
What this check does

DSALTA takes every user with Active status on the GitGuardian Access page and matches it to your People directory by email address. A match whose person is terminated or offboarding is recorded as a serious issue. A GitGuardian member is Active unless the workspace has deactivated the account. Users with no People match are not counted.
This check also runs on 141 other integrations — see Offboarded users should not have active access for the full list.
GitGuardian’s own deactivation state is respected: a member the workspace has deactivated is synced as Inactive and is not counted as retaining access, even if their People record is offboarded. Deactivating a member restricts their access to the workspace without deleting the account.
Passes when: No Active user on the GitGuardian Access page matches a person who is terminated or offboarding on the People page. An Access page with no Active GitGuardian users passes.

​
Why this matters

Offboarded employees must not retain access to the organization’s GitGuardian workspace, which watches its repositories for leaked secrets and holds every incident found. A former employee who can still sign in to GitGuardian can read the exposed secrets it has detected, long after anyone expects them to have access.

​
How to fix

Remove access for offboarded users
  1. Sign in to the GitGuardian dashboard as the workspace Owner or a Manager.
  2. Open Settings → Workspace → Members and find each offboarded employee.
  3. Deactivate or remove each of them. Their personal access tokens stop working with the account.
  4. In DSALTA, go to People and confirm each of those employees is marked terminated with an end date.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Compliance → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Compliance → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.