Skip to main content

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.

The Tests page is the core evidence engine of DSALTA. It shows every automated compliance check running across your connected integrations — each test produces a pass or fail result that serves as audit evidence.

​
How tests work

When you connect an integration (e.g., AWS, Google Workspace, GitHub), DSALTA automatically generates compliance tests specific to that integration. For example, connecting Google Workspace generates tests like “MFA should be enabled for all users” and “Offboarded users should not have active access.” Tests run automatically on every sync cycle (typically every 24 hours). You do not need to configure or schedule them — they activate as soon as the integration is connected and data is synced.

​
Viewing your tests

The test list shows all active tests with:
ColumnDescription
Test NameWhat the test checks
IntegrationWhich connected system the test runs against
StatusPassing, Failing, or Not Configured
Last RunWhen the test last executed
SourceSystem (auto-generated) or Manual
Click any test to view the detail page with the full test result, history of past runs, and remediation guidance if the test is failing.

​
Test statuses

Each test produces one of three results:
  • Passing — The configuration meets requirements. No action needed. This result is stored as positive audit evidence.
  • Failing — The configuration does not meet requirements. The test detail page includes step-by-step remediation guidance specific to the platform.
  • Not Configured — The integration is connected but the specific service or feature the test checks has not been set up yet in the source system.

​
System tests vs. manual tests

DSALTA supports two types of tests: System tests are auto-generated when you connect integrations. They run automatically and produce evidence without manual intervention. These are the primary evidence source for auditors. Manual tests are checks that cannot be automated — for example, “Annual security training completed” or “Background checks performed for all employees.” You create these manually and update their status periodically. Manual tests show Source: Manual. Both types appear in the same list and carry equal weight during audits.

​
Working with failing tests

When a test fails:
  1. Click the test to open its detail page.
  2. Read the Why This Matters section to understand the security risk.
  3. Follow the How to Fix steps — these are specific to the platform (e.g., AWS Console steps, Google Admin Console steps).
  4. After making the fix in the source system, DSALTA detects the change on the next sync cycle and updates the test to Passing.
  5. You can also trigger a manual sync from Integrations in the sidebar to see the result sooner.

​
Excluding tests

If a test does not apply to your environment, you can mark it as Not Applicable with a written justification. For example, if you do not use AWS Redshift, you can exclude all Redshift-related tests. The exclusion and justification are documented for auditors.

​
Linking tests to controls

Tests are automatically linked to the compliance controls they provide evidence for. When a test passes, it satisfies part of the control requirement. You can see which controls each test supports on the test detail page.