About
When you connect Microsoft Defender for Endpoint to DSALTA, the platform retrieves the list of resources in your environment using read-only API access. DSALTA then checks whether this configuration is in place. If it is not, DSALTA activates this check so you can remediate it.Why This Matters
Data stored without encryption can be read by anyone who gains access to the underlying storage — through a misconfiguration, a stolen disk, or improper decommissioning. Encryption at rest renders that data useless without the key and is required by SOC 2, ISO 27001, HIPAA, and PCI DSS.How to Fix
Before you begin- Ensure you have administrator access to Microsoft Defender for Endpoint.
- Open the encryption settings for the affected resource in Microsoft Defender for Endpoint.
- Enable encryption at rest using a KMS-managed or customer-managed key.
- Verify encryption is active in the resource configuration.
Frequently Asked Questions
How often does this check run?
How often does this check run?
This check runs automatically every 24 hours while the Microsoft Defender for Endpoint integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
What happens if it keeps failing?
What happens if it keeps failing?
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.
Can I exclude this check?
Can I exclude this check?
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
Does DSALTA change my Microsoft Defender for Endpoint configuration?
Does DSALTA change my Microsoft Defender for Endpoint configuration?
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Microsoft Defender for Endpoint.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)