> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/generic-on-premise-data-collectors/xdr-collectors/xdr-collector-profiles/add-an-xdr-collector-profile-for-linux.md). # Add an XDR Collector profile for Linux Add a Linux XDR Collector profile for Cortex XSIAM. {% hint style="info" %} Ingestion of log events larger than 5 MB is not supported. {% endhint %} ### Profile types An XDR Collector Linux profile defines the data that is collected from a Linux collector machine. For Linux, you can configure a Filebeat profile and a Settings profile. ### Filebeat profile Use an XDR Collector Linux Filebeat profile to collect file and log data using the Elasticsearch Filebeat default configuration file, called filebeat.yml. To facilitate configuration, you can use out-of-the-box collection templates, or templates added by content packs installed from the XSIAM Marketplace. You can edit, combine, or add your own custom collection settings. #### Supported versions and architectures Cortex XSIAM supports the following Elasticsearch Filebeat versions with the operating systems listed in the Elasticsearch Support Matrix that conform with the collector machine operating systems supported by Cortex XSIAM: * **64-bit XDR Collectors**: Supports Filebeat version 9.3.2. * **32-bit XDR Collectors**: Supports Filebeat version 7.17.1. Cortex XSIAM supports the input types and modules available in Elasticsearch Filebeat. {% hint style="info" %} **Note** Fileset validation is enforced. You must enable at least one fileset in the module, because filesets are disabled by default. {% endhint %} #### Log format constraints * Cortex XSIAM collects all logs in either an uncompressed JSON or text format. * Compressed files, such as the gzip format, are not supported. * Cortex XSIAM supports logs in single line format or multiline format. For more information about handling messages that span multiple lines of text in Elasticsearch Filebeat, see [Manage Multiline Messages](https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html). #### Related information * [Elasticsearch Filebeat Overview Documentation](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-overview.html#filebeat-overview) * [Configure Filebeat Inputs in Elasticsearch](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-options.html) * [Configure Filebeat Modules in Elasticsearch](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-filebeat-modules.html) * [Elasticsearch Support Matrix](https://www.elastic.co/support/matrix) * [XDR Collector machine requirements and supported operating systems](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/generic-on-premise-data-collectors/xdr-collectors/xdr-collector-machine-requirements-and-supported-operating-systems.md) ### Settings profile Use an **XDR Collector Settings profile** to configure automatic upgrade settings for XDR Collector releases. #### Policy mapping To map your XDR Collector profile to a collector machine, you must use an XDR Collector policy. After you have created your profile, map it to a new or existing policy. ### How to configure XDR Collector profiles #### Filebeat configuration In the Filebeat Configuration File editor, you can define the data collection for your Elasticsearch Filebeat configuration file called `filebeat.yml`. Cortex XSIAM provides YAML templates for XDR Collector Logs, Linux (RHEL/CentOS), NGINX (Linux), Linux (Debian/Ubuntu), and any templates added by the content packs installed from the XSIAM Marketplace. 1. In Cortex XSIAM, select Settings → Configurations → XDR Collectors → Profiles → +Add Profile → Linux. 2. Select Filebeat, then click Next. 3. Configure the General Information parameters. * Profile Name: Enter a unique name to identify the profile. The name can contain only letters, numbers, or spaces, and must be no more than 30 characters. The name that you enter here will be displayed in the list of profiles when you configure a policy. * (Optional) Add description here: To provide additional context for the purpose or business reason for your new profile, enter a profile description. 4. In the Filebeat Configuration File editing box, type or paste the contents of your configuration file, or use a template. To add a template, select one from the list, and click Add. 5. Cortex XSIAM supports all sections in the `filebeat.yml` configuration file, such as support for Filebeat fields and tags. You can use the "Add fields" processor to identify the product/vendor for the data collected by the XDR Collectors, so that the collected events go through the ingestion flow (Parsing Rules). To configure the product/vendor, ensure that you use the default `fields` attribute (do not use the target attribute), as shown in the following example: ``` processors: - add_fields: fields: vendor: product: ``` For more information about the "Add fields" processor, see [Add\_fields](https://www.elastic.co/guide/en/beats/filebeat/current/add-fields.html). 6. To finish creating your new profile, click Create. Your new profile will be listed under the applicable platform on the XDR Collectors Profiles page. 7. Apply profiles to XDR Collector machine policies by performing one of the following: * Right-click a profile, and select Create a new policy rule using this profile. * Launch the new policy wizard from XDR Collectors → Policies → XDR Collectors Policies. #### Settings configuration You can configure automatic upgrades for XDR Collector releases. By default, this is disabled, and the Use Default (Disabled) option is selected. To implement automatic upgrades, follow these steps: 1. In Cortex XSIAM, select Settings → Configurations → XDR Collectors → Profiles → +Add Profile → Linux. 2. Select Settings profile, then click Next. 3. Configure the General Information parameters. * Profile Name: Enter a unique name to identify the profile. The name can contain only letters, numbers, or spaces, and must be no more than 30 characters. The name that you enter here will be displayed in the list of profiles when you configure a policy. * (Optional) Add description here: To provide additional context for the purpose or business reason for your new profile, enter a profile description. 4. Clear the Use Default (Disabled) checkbox. 5. For Collector Auto-Upgrade, select Enabled. Additional fields are displayed for defining the scope of the automatic upgrade. 6. Configure the scope of automatic upgrades: * To ensure the latest XDR Collector release is used, leave the Use Default (Latest collector release) checkbox selected. * To configure only a particular scope, perform the following steps: 1. Clear the Use Default (Latest collector release) checkbox. 2. For Auto Upgrade Scope, select one of the following options: | Option | More details | | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Latest collector release | Configures the scope of the automatic upgrade to whenever a new XDR Collector release is available including maintenance releases and new features. | | Only maintenance release | Configures the scope of the automatic upgrade to whenever a new XDR Collector maintenance release is available. | | Only maintenance releases in a specific version | Configures the scope of the automatic upgrade to whenever a new XDR Collector maintenance release is available for a specific version. When this option is selected, you can select the specific Release Version. | 7. To finish creating your new profile, click Create. Your new profile will be listed under the applicable platform on the XDR Collectors Profiles page. 8. Apply profiles to XDR Collector machine policies by performing one of the following: * Right-click a profile, and select Create a new policy rule using this profile. * Launch the new policy wizard from XDR Collectors → Policies → XDR Collectors Policies. ### Additional XDR Collector profile management options As needed, you can return to the XDR Collectors Profiles page to manage your XDR Collectors profiles. To manage a specific profile, right click anywhere in an XDR Collector profile row, and select the desired action: | Option | More details | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Edit | Lets you edit the XDR Collector profile | | Save As New | Copies the existing profile with its current settings, so that you can make modifications, and save it as a new profile with a unique name | | Delete | Deletes the XDR Collector profile | | View Collector Policies | Opens a new tab that displays the XDR Collectors Policies page, showing the policies that are currently associated with your XDR Collector profiles | | Copy text to clipboard | Copies the text from a specific field in the row of a XDR Collector profile | | Copy entire row | Copies the text from the entire row of a XDR Collector profile | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/generic-on-premise-data-collectors/xdr-collectors/xdr-collector-profiles/add-an-xdr-collector-profile-for-linux.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.