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.

Checks that Microsoft Defender for Cloud is enabled on the Azure subscription.

​
Why This Matters

Unresolved security findings indicate active or potential threats in your environment. Threat detection services identify compromised credentials, unusual API activity, and policy violations. Leaving findings unresolved extends your exposure window and violates incident response requirements in SOC 2 (CC7.3) and ISO 27001 (A.16.1).

​
What DSALTA Checks

DSALTA connects to your Microsoft Azure environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → Microsoft Azure.

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Navigate to your security findings dashboard in Microsoft Azure.
  2. Review each open finding or incident.
  3. For each finding, take the recommended remediation action (e.g., rotate credentials, patch vulnerability, restrict access).
  4. Update the finding status to Resolved or Closed in the source system.
  5. Document the resolution, including what action was taken and by whom.
  6. DSALTA monitors the status of findings — once all findings are resolved and closed in the source, DSALTA will update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the Microsoft Azure integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in Microsoft Azure.