Skip to main content
Checks that incidents detected in Microsoft Defender are closed and resolved.

​
About

When you connect Microsoft Azure to DSALTA, the platform retrieves the current security findings using read-only API access. DSALTA tracks their status and activates this check when action is required.

​
Why This Matters

Open security findings represent active or potential threats sitting in your environment. The longer they stay unresolved, the longer your exposure window. Detecting and closing findings promptly is required by the incident-response controls in SOC 2 and ISO 27001.

​
How to Fix

Before you begin
  • Ensure the Microsoft Azure integration is connected so DSALTA sees the current findings.
Resolve and close open findings
  1. Open your security findings in Microsoft Azure (GuardDuty, Security Command Center, or Defender).
  2. For each open finding, take the recommended remediation action (rotate credentials, patch, restrict access).
  3. Mark the finding as Resolved or Closed in the source system and document the action taken.
Once all findings are resolved and closed, 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 Microsoft Azure 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 the underlying configuration is fixed, 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 Microsoft Azure.