|
| 1 | +--- |
| 2 | +title: Protect your Mural environment | Microsoft Defender for Cloud Apps |
| 3 | +description: This article provides information about the benefits of connecting your Mural app to Defender for Cloud Apps using the API connector for visibility and control over use. |
| 4 | +ms.date: 05/06/2024 |
| 5 | +ms.topic: how-to |
| 6 | +--- |
| 7 | + |
| 8 | +# Protect your Mural environment (Preview) |
| 9 | + |
| 10 | +Mural is an online workspace that enables distributed, cross-functional teams organize and collaborate on projects. Mural holds critical data of your organization, and this makes it a target for malicious actors. |
| 11 | + |
| 12 | +Connecting Mural to Defender for Cloud Apps gives you improved insights into your users' activities and provides threat detection using machine learning based anomaly detections. |
| 13 | + |
| 14 | +## Main threats |
| 15 | + |
| 16 | +- Compromised accounts and insider threats |
| 17 | +- Data leakage |
| 18 | +- Insufficient security awareness |
| 19 | +- Unmanaged bring your own device (BYOD) |
| 20 | + |
| 21 | +## How Defender for Cloud Apps helps to protect your environment |
| 22 | + |
| 23 | +- [Detect cloud threats, compromised accounts, and malicious insiders](best-practices.md#detect-cloud-threats-compromised-accounts-malicious-insiders-and-ransomware) |
| 24 | +- [Use the audit trail of activities for forensic investigations](best-practices.md#use-the-audit-trail-of-activities-for-forensic-investigations) |
| 25 | + |
| 26 | +## Control Mural with policies |
| 27 | + |
| 28 | +| **Type** | **Name** | |
| 29 | +| ---------------------------------- | ------------------------------------------------------------ | |
| 30 | +| **Built-in anomaly detection policy** | [Activity from anonymous IP addresses](anomaly-detection-policy.md#activity-from-anonymous-ip-addresses) <br /> [Activity from infrequent country](anomaly-detection-policy.md#activity-from-infrequent-country) <br /> [Activity from suspicious IP addresses](anomaly-detection-policy.md#activity-from-suspicious-ip-addresses) <br /> [Impossible travel](anomaly-detection-policy.md#impossible-travel) <br /> [Activity performed by terminated user](anomaly-detection-policy.md#activity-performed-by-terminated-user) (requires Microsoft Entra ID as IdP) <br />[Multiple failed login attempts](anomaly-detection-policy.md#multiple-failed-login-attempts) <br /> | |
| 31 | +| **Activity policy** | Built a customized policy by using the [Mural Audit Log API](https://support.mural.co/s/article/audit-logs). | |
| 32 | + |
| 33 | +<!--check xrefs --> |
| 34 | +For more information about creating policies, see [Create a policy](control-cloud-apps-with-policies.md#create-a-policy). |
| 35 | + |
| 36 | +## Automate governance controls |
| 37 | + |
| 38 | +In addition to monitoring for potential threats, you can apply and automate the following Mural governance actions to remediate detected threats: |
| 39 | + |
| 40 | +| **Type** | **Action** | |
| 41 | +| --------------- | ------------------------------------------------------------ | |
| 42 | +| **User governance** | Notify user on alert (via Microsoft Entra ID)<br /> Require user to sign in again (via Microsoft Entra ID) <br /> Suspend user (via Microsoft Entra ID) | |
| 43 | + |
| 44 | +For more information about remediating threats from apps, see [Governing connected apps](governance-actions.md). |
| 45 | + |
| 46 | +## Connect Mural to Microsoft Defender for Cloud Apps |
| 47 | + |
| 48 | +This section provides instructions for connecting Microsoft Defender for Cloud Apps to your existing Mural account using the App Connector APIs. This connection gives you visibility into and control over Mural usage. |
| 49 | + |
| 50 | +**Prerequisites**: |
| 51 | + |
| 52 | +- A Mural enterprise account is a pre-requisite for this connection. You must be signed-in as an admin to Mural. |
| 53 | + |
| 54 | +**To connect Mural to Defender for Cloud Apps**: |
| 55 | + |
| 56 | +1. Sign into your [Mural](https://app.mural.co/) account and select your account icon > **Manage Company > Development > API keys > Create API key**. |
| 57 | +1. Select all checkboxes and then select **Create API Key** and then **Copy Key**. |
| 58 | +1. In the Microsoft Defender portal, select **Settings > Cloud Apps > Connected Apps > App Connectors > Connect an app > Mural**. |
| 59 | +1. In the connection wizard, enter your instance name, and then select **Next**. |
| 60 | +1. Paste the API key you'd copied from the Mural portal and then select **Submit**. |
| 61 | + |
| 62 | +Once the connection is successfully established, Defender for Cloud Apps starts fetching Mural audit logs. Since Mural's API logs are delayed by 48 hours, the audit log ingestion to Defender for Cloud Apps is similarly delayed. |
| 63 | + |
| 64 | +If you have any problems connecting the app, see [Troubleshooting App Connectors](/defender-cloud-apps/troubleshooting-api-connectors-using-error-messages). |
| 65 | + |
| 66 | +## Next steps |
| 67 | + |
| 68 | +> [!div class="nextstepaction"] |
| 69 | +> [Control cloud apps with policies](control-cloud-apps-with-policies.md) |
| 70 | +
|
| 71 | + |
| 72 | +[!INCLUDE [Open support ticket](includes/support.md)] |
0 commit comments