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 screen lock is enabled on all devices managed by Microsoft Defender.

Why This Matters

Non-compliant endpoint devices — missing encryption, outdated OS, or disabled screen locks — are vulnerable to data theft if lost or stolen. Endpoint security policies are required by SOC 2, ISO 27001 (A.6.2.1), and HIPAA.

What DSALTA Checks

DSALTA connects to your Microsoft Defender for Endpoint 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 Defender for Endpoint.

How to Fix

If this test is failing, follow these steps to remediate:
  1. Open Microsoft Intune admin center.
  2. Navigate to Devices → Configuration profiles → Create profile.
  3. Select the platform (Windows/macOS/iOS) and choose Device restrictions.
  4. Under Password or Lock Screen, set Require a password/passcode to Yes.
  5. Set Maximum minutes of inactivity before screen locks (15 minutes or less recommended).
  6. Assign the policy to all device groups.
  7. Once all devices comply with the screen lock policy, DSALTA will update the test status to Passing.

Frequently Asked Questions

This test runs automatically every 24 hours when the Microsoft Defender for Endpoint 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 Defender for Endpoint.