Connecting to a Microsoft Defender for Endpoint asset data source

The Microsoft Defender for Endpoint Connected Assets and Risk connector can be run in the IBM Security QRadar® Suite Software cluster. The connector incrementally synchronizes the contents of the Microsoft Defender for Endpoint asset databases with the data that is managed by the Connected Assets and Risk service.

1. Log in to IBM Security QRadar Suite Software.
2. From the menu, click Connections > Data sources.
3. On the Integration data sources page, on the Microsoft Defender for Endpoint tile, click Set up a connection.
4. On the Connection services page, select the Connected assets & risk service tile, and then click Enable.
   The available connection services include:

   1. Connected assets & risk
   2. Federated searches

   Note: If there are multiple data sources to connect, select the connector from the Sources list, and then click Enable.
5. Click Next.
6. On the Connection details page, configure the following parameters.
   1. Configure the connection to the data source.

      Table 2. Connection parameters

      Parameter	Description
      Data source name	Enter a unique name to identify the data source connection. You can create multiple connections to a data source, so it is useful to clearly set them apart by name. Only alphanumeric characters and the following special characters are allowed: - . _
      Data source description	Enter a description to indicate the purpose of the data source connection. You can create multiple connections to a data source, so it is useful to clearly indicate the purpose of each connection by description. Only alphanumeric characters and the following special characters are allowed: - . _
      Edge gateway	If you have a firewall between your cluster and the data source target, use the Edge Gateway to host the containers. In the Edge gateway field, specify an Edge Gateway to host the connector. It can take up to five minutes for the status of newly deployed data source connections on the Edge Gateway to show as being connected.
      Frequency	Set how often the connector imports data from the data source, in minutes. The value must be an integer. For example, a value of 5 causes the connector to run every 5 minutes. If the data source doesn't have many assets, or you don't want to import data often, reduce the frequency.

   2. Click Next.
   3. If Microsoft Azure is configured with a self-signed Security Sockets Layer (SSL) certificate, add a connection certificate.

      To confirm that you have a self-signed certificate, you can search the web for 'ssl decode', then copy and paste your certification into a Certificate Decoder. If the value in the Common Name field is local, for example: yourlocalhost.yourlocaldomain, it indicates a self-signed certificate.

      If the value of your hostname or IP address does not match the common name value in your certificate, add the hostname to the server that hosts the Edge Gateway.

      Table 3. Adding your hostname to the Edge Gateway server

      If you are running the Edge client

      If you are not running the Edge client

      Run the following command: manageAppHost dns --set --ip <ip_address> --hostname <hostname1> --hostname <hostname2> Tip: The <ip_address> is the address of the server that you want to access, and <hostname> is the name of the server. If a server has multiple names, you can add each name by using --hostname. You can use --show to see the defined hostnames and --clear to remove a hostname previously set with the manageAppHost command.

      Add the hostname to the server that hosts the Edge Gateway by adding entries to Pod /etc/hosts with HostAliases. To edit the Universal Data Insights worker deployment, run the following command: oc edit deployment udi-udiworker Add the following information to the host deployment HostAliases, in the spec.template.spec section: hostAliases: - hostnames: - qradar.iseccs.local ip: <1.2.3.4> For more information, see Adding entries to Pod /etc/hosts with HostAliases (https://kubernetes.io/docs/tasks/network/customize-hosts-file-for-pods/).

   4. Copy the certificate details and paste it in the space that is provided.
   5. Click Next.
7. On the Connection configurations page, configure identity and access.
   1. Click Add a configuration.
   2. In the Configuration details window, configure the following parameters.

      Table 4. Configuration parameters

      Parameter	Description
      Configuration Name	Enter a unique name to describe the access configuration and distinguish it from the other access configurations for this data source connection that you might set up. Only alphanumeric characters and the following special characters are allowed: - . _
      Configuration Description	Enter a unique description to describe the access configuration and distinguish it from the other access configurations for this data source connection that you might set up. Only alphanumeric characters and the following special characters are allowed: - . _
      Subscription ID	Enter your Microsoft Azure subscription ID.
      Tenant ID	Enter your Microsoft Azure tenant ID (a UUID).
      Client ID	Enter the client ID for your Microsoft Azure tenant (a UUID).
      Client secret	Enter the client secret for your Microsoft Azure tenant.

   3. To save your configuration and establish the connection, click Save.
8. Click Next.
9. Click Finish.
10. To manage your active connections, complete the following steps:
    1. On the Integration data sources page, on the tile of the relevant data source, click Manage <x> of <x> active connections.
    2. On the Connection status page, on the tile of the relevant data source, you can edit, refresh, or delete your data source connection.