Skip to main content
All CollectionsIntegrate EverythingMicrosoft
Microsoft Defender for Endpoint
Microsoft Defender for Endpoint

Sometimes known as Microsoft Defender for XDR. Integrate Defender for Endpoint with Torq to automate threat detection and more.

Updated over 2 weeks ago

Microsoft Defender for Endpoint provides protection against spyware and other malicious software, with advanced threat detection.

Torq enables quick and easy integration with Microsoft Defender for Endpoint, so you can automate anything and everything within moments. Torq's public Microsoft Defender for Endpoint steps include:

  • Add or Update Indicator

  • Create Session

  • Delete Indicator

  • Execute Live Response

  • Get a File from Endpoint

  • +35 more...

If you don't see a step you need, you can create your own in various ways, such as using the Send an HTTP Request step or Torq’s Step Builder, and share it across your organization.

Look here if you want to use Microsoft Defender steps in a workflow.

Use Microsoft Defender for Endpoint Steps in a Torq Workflow

Step One: Create an App in Azure (Without a User)

  1. Create New App: Sign in to the Azure portal and navigate to Microsoft Entra ID > App registrations > New registration.

    1. Choose a name for your application (such as Torq Defender Endpoint).

    2. Under Supported account types select Accounts in this organizational directory only.

    3. There is no need to add a redirect URL.

    4. Click Register.

  2. Add Permissions: Go to Manage > API Permissions and click Add a Permission.

    1. Select APIs my organization uses and search for WindowsDefenderATP.

    2. Click on WindowsDefenderATP and click Application Permissions.

    3. Add all the permissions you want your Torq integration to access. For example, if you wish to use the Isolate Machine step in Torq, you must add the Machine.Isolate permission.

    4. To use Read Only steps in your workflows, you should enable the following permissions:

      Alert.Read.All 
      AdvancedQuery.Read.All
      Machine.Read.All
      User.Read.All
      Vulnerability.Read.All
      File.Read.All
      Machine.CollectForensics
      SecurityRecommendation.Read.All
    5. Steps that take Response or Remediation actions in your workflows require the following permissions:

      Alert.ReadWrite.All 
      Machine.ReadWrite.All
      Machine.CollectForensics
      Machine.Isolate
      Machine.RestrictExecution
      Machine.Scan
      Machine.Offboard
      Machine.StopAndQuarantine
      Machine.LiveResponse
      Ti.ReadWrite.All
  3. Apply Permissions: Click Add Permissions and then click Grant Admin Consent.

    1. Note that if you return later to grant more permissions to your Torq app, you must click Grant Consent again. Otherwise, your changes will not be saved, and the permissions will not be given to the Torq app.

  4. Add Secret: Go to Manage > Certificates & secrets and click New Client Secret.

    1. Give the secret a meaningful name.

    2. Give the secret an appropriate expiration time.

    3. Click Add.

    4. Copy the secret ID in a secure place, as you cannot access it again.

  5. Collect Final Details: Go to the Overview page and copy the application (client) ID and the directory (tenant) ID, which will be used in Torq later.

    1. We suggest saving the directory (tenant) ID in Torq as a workspace variable for easier access in steps later.

Step Two: Create a Microsoft Defender for Endpoint Step Integration in Torq

  1. Navigate to Integration: Go to Build > Integrations > Steps > Microsoft Defender for Endpoint and click Add.

    1. Give the integration a unique and meaningful name.

    2. Paste the Client ID (application ID) created earlier.

    3. Paste the Client Secret created earlier.

  2. Finalize: Click Add.


FAQs

Using Microsoft Defender for Endpoint Steps in a Torq Workflow

To use Microsoft Defender for Endpoint steps within a Torq workflow, you must first use the Create Session step under the Microsoft Defender for Endpoint. The created session will then be used with the rest of the workflow's steps to access Microsoft Defender for Endpoint.

To activate the Create Session step, you must insert your app's tenant ID. This is why we suggested saving it as a workspace variable (step 9.a) in Torq for easier access across all workflows.


Templates

Now that you've added your integrations check out these specially crafted templates by Torq's security experts. Visit Torq's template library for more.

Did this answer your question?