🌙☀
 

Subscribe to the Taegis™ XDR Documentation RSS Feed at .

Learn more about RSS readers or RSS browser extensions.

AWS Data Collector

data collectors integrations amazon aws


Secureworks® Taegis™ XDR has a collector that can be set up in an Amazon Web Service (AWS) instance. The XDR for AWS is provided as an Amazon Machine Image (AMI). During provisioning a valid AWS account number (9 digit number) and AWS region are required so that the appropriate AMI is authorized for your AWS account. Each collector is uniquely identified by its configuration. Configuration data is injected into an AWS EC2 instance via user data. For convenience, a sample AWS CloudFormation template is generated for your XDR Collector upon completion of the provisioning process. This sample template creates the following resources:

XDR provides options to download the sample template or launch it directly. The sample template should work in most VPC environments but should be carefully reviewed to ensure it conforms to all network and security policies. Advanced users may extract the AMI ID and user-data from the template to incorporate into their own IaC or automation tools. If you opt to use the sample template provided, the CTPxCollectorDnsName template output provides the DNS name to use for your syslog devices to send traffic.

Configuration Notes ⫘

Note

The XDR Collector can support up to 200K EPS (events per second) for properly configured cloud and on-premises collectors.

Note

Third-party tools or applications cannot be installed on any XDR Collector.

Connectivity Requirements for Data Collectors ⫘

Regions

XDR Regional Configuration ⫘

Some configuration specifics of XDR depend on the region you are deployed in (US1, US2, US3, EU).

Any device that uses its own SSL certificate, including Cloud-based and On-Premises Data Collectors, must safelist the following destination IP addresses or domains in order to avoid conflict. If using an AWS data collector, please refer to the AWS table.

For Most Data Collectors ⫘

Source Destination Port/Protocol Notes
Data Collector IP or hostname
US1
collector.ctpx.secureworks.com
18.217.45.178/32
3.16.4.173/32
18.224.219.97/32
13.59.146.90/32
3.16.16.254/32
18.223.74.238/32
US2
collector.delta.taegis.secureworks.com
52.14.113.127/32
3.141.73.137/32
3.136.78.106/32
US3
collector.foxtrot.taegis.secureworks.com
44.229.101.49
35.166.77.47
34.214.135.78
EU
collector.echo.taegis.secureworks.com
18.158.143.139/32
35.159.14.37/32
52.59.37.234/32		 TCP/443 Safelisting device access to XDR
Data Collector IP or hostname NTP severs IP/Hostnames provided during provisioning UDP/123 Safelisting device access to NTP servers

This rule is only necessary when custom NTP servers are provided during provisioning.
Data Collector IP or hostname 0.pool.ntp.org
1.pool.ntp.org
2.pool.ntp.org
3.pool.ntp.org		 UDP/123 Safelisting device access to default NTP server.

This rule is only necessary when custom NTP servers are not provided during provisioning.
Data Collector IP or hostname DNS server IPs provided during provisioning UDP/53
TCP/53		 Safelisting device access to DNS servers

Note

If using local NTP, the access must be safelisted both to and from the data collector on those networks.

For AWS Data Collectors ⫘

Source Destination Port/Protocol Notes
AWS Data Collector IP or hostname
US1
collector.ctpx.secureworks.com
18.217.45.178/32
3.16.4.173/32
18.224.219.97/32
13.59.146.90/32
3.16.16.254/32
18.223.74.238/32
US2
collector.delta.taegis.secureworks.com
52.14.113.127/32
3.141.73.137/32
3.136.78.106/32
US3
collector.foxtrot.taegis.secureworks.com
44.229.101.49
35.166.77.47
34.214.135.78
EU
collector.echo.taegis.secureworks.com
18.158.143.139/32
35.159.14.37/32
52.59.37.234/32		 TCP/443 Safelisting device access to Taegis XDR via hostname
AWS Data Collector IP or hostname NTP severs IP/Hostnames provided during provisioning UDP/123 Safelisting device access to NTP servers

This rule is only necessary when custom NTP servers are provided during provisioning.
AWS Data Collector IP or hostname 169.254.169.123 UDP/123 Safelisting device access to default NTP server.

This rule is only necessary when custom NTP servers are not provided during provisioning.
AWS Data Collector IP or hostname DNS server IPs provided during provisioning UDP/53
TCP/53		 Safelisting device access to DNS servers

Proxy Support ⫘

Cloud-based and On-Premises Data Collectors attempt to discover local proxy settings on the host if they are unable to connect directly to the internet.

Cloud-based and On-Premises Data Collectors also support a hard-coded proxy. If you need to create a data collector that contains a hard-coded proxy, please submit a support request with the following required information:

If the proxy is configured but is unavailable or not reachable, the data collector will fall back to a direct connection.

Note

Cloud-based and On-Premises Data Collectors do not support hard-coded authenticated proxies at this time. A proxy with man in the middle (MITM) capability needs to safelist the above network connections.

Install and Configure an XDR AWS Collector ⫘

Start the process to configure your XDR AWS Collector in XDR from Integrations > Data Collectors. It will create a template for you, then forward you to your AWS Console to complete the configuration.

  1. From XDR, select Integrations from the left-hand navigation and then choose Data Collectors.
  2. Select Actions > Add Collector from the top right.

Add New Collector

Add New Collector

  1. Select Cloud-Hosted as the collector type and then select Next.
  2. Fill in the required name and hostname fields, and the optional description, host proxy, and NTP servers fields, and then select Create Collector.

Note

You have the option to specify your own NTP servers if desired, and to add an HTTP proxy address, which must follow the following format: [http\[s]://\[user:pass@]hostname\[:port]|http://<hostname>[:port]].

Note

Default and custom NTP settings are only used during initial Data Collector setup. Once connectivity is established, the Data Collector synchronizes time via the XDR backend connection.

Create Cloud Collector

Create Cloud Collector

Tip

To add the eStreamer app to the collector to retrieve all security event logs from your Cisco Firepower Threat Defense (FTD) device, see eStreamer App. For more information, see the Cisco FTD Firewall guide.

  1. The Install Collector section displays the following options:

    • Amazon Web Services (AWS) — This option is for deploying the XDR Collector to AWS.
    • Google Cloud Platform (GCP) — This option is for deploying the XDR Collector to GCP.
    • Microsoft Azure — This option is for deploying the XDR Collector to Azure.

  2. Select Amazon Web Services (AWS).

  3. Enter your AWS Account ID.
  4. Select the AWS region you want to deploy from.
  5. Select Launch Console.

AWS Collector

AWS Collector

Note

You can also download the .yaml template for your XDR AWS Collector and then use that template to configure the collector in your AWS account by selecting Download. Read the Configuration Notes for more information on what the template provides.

  1. The AWS console displays the CloudFormation Create stack page in a new browser window with a preloaded CloudFormation template (YAML) that includes parameters for the collector image, in addition to AWS resource information like load balancing, etc.

Create stack

Create stack

You need to configure the parameters particular to your instance, however:

  1. Give your new collector a name in the CollectorName field.

Collector Name

Give the Collector a Name

  1. Under Subnets select the subnet(s) in your VPC that you want to deploy the XDR AWS Collector on.

Select a subnet

Select a subnet

  1. If you want to configure which subnet(s) in the VPC can access the Collector, add a firewall rule in SyslogIngress following IP syntax. For example, if you put in 0.0.0.0/0 it would allow everything, or you can limit it to your VPC subnet, etc.
  2. Add the VpcId of the VPC you want to deploy.
  3. The InstanceType for your deploy is preset at c5.xlarge. Note that c5.xlarge has a virtual system of 4 CPUs and 8GiB memory.
  4. You may optionally add a KmsCmkArn if you want to enforce EBS Encryption.
  5. Select Next. The Configure stack options page displays.
  6. Select and confirm any options you want to add.
  7. When you are satisfied with the options, select Create stack to create the instance. It automatically launches the deployment.
  8. It may take a few minutes for the collector to build and deploy. You can confirm the collector status from Integrations > Data Collectors in XDR.

Note

AWS assigns IPs for the XDR AWS Collector dynamically, so the IP address for the collector will not appear in the Address column of the XDR Integrations Collectors table.

Note

If using EBS Encryption, the key policy must be set up correctly. If your ASG is cycling instances with the error Client.InternalError: Client error on launch, check that the key policy has the correct requirements for EBS encryption.

Access Troubleshooting Console ⫘

The Admiral console allows you to access information about a deployed XDR Collector locally. The tools provided within Admiral assist in device setup and troubleshooting of common problems such as network connectivity. For more information, see Admiral Console.

Edit Your XDR Collector Configuration ⫘

Important

Making changes to the XDR Collector configuration of a live system carries the risk of rendering the device inoperable. The XDR Collector will make every attempt possible to rollback to the previous configuration when a configuration change is unsuccessful. XDR Collector configuration changes should be treated with the same level of caution used for any other kind of change in your environment according to your risk and change management guidelines. You should always be prepared to redeploy the device.

Certain configuration parameters of a running and healthy XDR Collector can be changed on a live collector. To edit these parameters, select Actions and choose Edit Collector Configuration from a collector details page. Editable fields include the hostname, proxy settings, and NTP server. If you require a change to the network interface configuration, it is required to provision a new XDR Collector.

Edit Collector Configuration

Edit Collector Details

Edit Collector Configuration Slideout

Edit Collector Configuration

After submitting a XDR Collector configuration change, a banner will appear to indicate that the change is pending and the edit action will no longer be available until the change has completed. The pending changes will be pushed to your XDR Collector where they will be applied and connectivity testing conducted.

Edit Collector Configuration Pending

Edit Collector Configuration Pending

If the pending changes result in the XDR Collector no longer able to successfully connect, the change will be rolled back to the previous configuration and a failure message will appear in the banner.

Edit Collector Configuration Rolled Back

Edit Collector Configuration Rolled Back

If the change is successful, you will receive a successful message in the banner once the change has completed.

Edit Collector Configuration Success

Edit Collector Configuration Success

In rare circumstances, it’s possible that the configuration change and rollback are both unsuccessful. Example scenarios include, but are not limited to, changes to the underlying network during the change or network connectivity failures to the backend during an inflight change. In these circumstances, you will see a failure banner and the XDR Collector will need to be redeployed.

Edit Collector Configuration Failed

Edit Collector Configuration Failed

Once the change is complete, download the new AWS CloudFormation and apply the updates to your current AWS CloudFormation Stack. This ensures that your new configuration is used when and if the instance is replaced in AWS.

Manage Integrations Collector Downloads

Manage Integrations Collector Downloads

 

On this page: