Skip to main content

​
What this check does

DSALTA reads Defender-managed devices and checks that each device’s operating system is up to date.
This check does not currently run. The Microsoft Defender integration collects vulnerability findings only — it does not execute automated compliance checks, and it does not read the device or user data this check would need. The check is defined in DSALTA’s catalog but produces no result while this is the case, so it will stay at Not Run.
Passes when: Every Defender-managed device runs an up-to-date operating system.

​
Why this matters

Running an up-to-date operating system ensures known vulnerabilities are patched.

​
How to fix

Enforce OS updates
  1. Open the Microsoft Intune admin center.
  2. Navigate to Devices → Compliance policies → Create policy.
  3. Select the platform and set Minimum OS version to the latest stable release.
  4. Under Actions for noncompliance, mark devices noncompliant after a grace period.
  5. For Windows, create Update rings under Devices → Windows 10 and later updates to automate patching.
  6. For macOS, configure a software update policy under Devices → macOS.
Fixing this in your environment is still worthwhile, but DSALTA will not record a result for it until this integration can run checks.

​
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 Data Library → 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 Data Library → 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.