Darktrace

Version: 1.7
Updated: Jan 10, 2025

Perform threat intelligence evidence gathering with Darktrace.

Actions

• Add To Watch List (Containment) - Adds external domains, hostnames, or IP addresses to Darktrace's internal watch list.
• Darktrace Breach Daemon (Daemon) - Automatically gather Breaches from Darktrace.
• Darktrace Incident Events Daemon (Daemon) - Automatically gather Incident Events from Darktrace (provides access to AI Analyst events - a group of anomalies or network activity investigated by Cyber AI Analysts).
• Get IOC (Enrichment) - Get IOC details by value.
• Get Model (Enrichment) - Returns a specific model that currently exist on the Threat Visualizer.
• Get Watch List (Enrichment) - Retrieves a list of indicators from a watch list.
• List Models (Enrichment) - Returns a list of all models that currently exist on the Threat Visualizer.
• List Tags (Enrichment) - List all available tags.
• Remove From Watch List (Containment) - Removes an external domain, hostname, or IP address from Darktrace's internal watch list.
• Search Breach (Enrichment) - Query breaches from Darktrace.
• Search Devices (Enrichment) - Search capacity to interrogate the list of devices has seen on the network.

Configure Darktrace in Automation Service and Cloud SOAR

Before you can use this automation integration, you must configure its authentication settings so that the product you're integrating with can communicate with Sumo Logic. For general guidance, see Configure Authentication for Automation Integrations.

How to open the integration's configuration dialog

1. Access App Central and install the integration. (You can configure at installation, or after installation with the following steps.)
2. Go to the Integrations page.
   Classic UI. In the main Sumo Logic menu, select Automation and then select Integrations in the left nav bar.
   New UI. In the main Sumo Logic menu, select Automation > Integrations. You can also click the Go To... menu at the top of the screen and select Integrations.
3. Select the installed integration.
4. Hover over the resource name and click the Edit button that appears.
   

In the configuration dialog, enter information from the product you're integrating with. When done, click TEST to test the configuration, and click SAVE to save the configuration:

• Label. Enter the name you want to use for the resource.

• URL. Enter your Darktrace server URL.

• Public Key. Enter a Darktrace public key.

• Private Key. Enter the private key corresponding to the public key.

• Verify Server Certificate. Select to validate the server’s SSL certificate.

• Connection Timeout (s). Set the maximum amount of time the integration will wait for a server's response before terminating the connection. Enter the connection timeout time in seconds (for example, 180).

• Darktrace Minutes. Enter your Darktrace minutes setting, for example, 10.

• Automation Engine. Select Cloud execution for this certified integration. Select a bridge option only for a custom integration. See Cloud or Bridge execution.

• Proxy Options. Select whether to use a proxy. (Applies only if the automation engine uses a bridge instead of cloud execution.)

  • Use no proxy. Communication runs on the bridge and does not use a proxy.
  • Use default proxy. Use the default proxy for the bridge set up as described in Using a proxy.
  • Use different proxy. Use your own proxy service. Provide the proxy URL and port number.

For information about Darktrace, see the Darktrace website.

Change Log

• January 15, 2021 - First upload
• February 11, 2021 - Updated Actions:
  • Get IOC
  • List Models
  • Get Models
  • Search Device
  • List Tags
• June 07, 2022 - New Actions:
  • Search Breach
  • Darktrace Breach Daemon
• February 17, 2023 (v1.2)
  • New Daemon: Darktrace Incident Events Daemon
• July 12, 2023 (v1.3) - Updated the integration with Environmental Variables
• January 29, 2024 (v1.4)
  • Updated resource: Resolved bug related to integration resource
• February 28, 2024 (v1.5) - Updated code for compatibility with Python 3.12
• March 4, 2024 (v1.5) - Updated code for compatibility with Python 3.12
• January 10, 2025 (v1.7) - Fixed timedelta related error in all actions