Protect your Mural environment | Microsoft Defender for Cloud Apps
In brief
The documentation now states that the Activity performed by terminated user policy requires Microsoft Entra ID as the identity provider and that Mural audit-log ingestion is delayed by 48 hours. It also includes wording, heading, and navigation updates.
What Defender admins need to know
Administrators should account for the identity-provider prerequisite and 48-hour delay when configuring and monitoring Mural in Defender for Cloud Apps.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
How Microsoft Defender for Cloud Apps helps protect your Mural environment (Preview)
Mural is an online workspace that enables distributed, cross-functionalwhere teams can organize and collaboratework together on projects. Mural holds criticalkey data offor your organization, and that exposurewhich makes it a target for malicious actors.
ConnectingWhen you connect Mural to Defender for Cloud Apps givesApps, you improved insightsget better visibility into your users' activities and providesuser activity. You also get threat detection usingwith machine learning based anomaly detections.
Main threats to your Mural environment
Connecting Mural without adequate protection exposes your organization to the following threats:
Control Mural with policies
The following table lists theYou can use these policy types you can use to monitor and control Mural:Mural.
For more information about creating policies, see Create a policy. Automate governance controls
Connect Mural to Microsoft Defender for Cloud Apps
Prerequisites
|
