> 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/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/classification-and-mapping/create-a-mapper.md). # Create a Mapper Mappers enable you to map the information from incoming events to the incident or indicator layouts that you have in your system. Mapping event attributes or indicator fields now takes place in two stages. At first, you map all of the fields that are common to all incident or indicator types in the default mapping. After that, you can map the additional fields that are specific for each incident or indicator type, or overwrite the mapping that you used in the default mapping. {% hint style="info" %} ### Note In the **Classification & Mapping** screen, the mappings do not indicate for which incident types they are configured. Therefore, when creating a mapper, it is best practice to add to the mapper name the incident types the mapper is for. For example, Mail Listener - Phishing. {% endhint %} {% hint style="info" %} ### Note When mapping a list, we recommend you map to a multi select field. Short text fields do not support lists. If you do need to map a list to a short text field, add a transformer in the relevant playbook task, to split the data back into a list. {% endhint %} Be aware that the following out-of-the-box fields are entirely controlled by Cortex XSOAR, and therefore cannot be mapped: | | | | | --------------- | --------------- | ------------- | | Type | Source Instance | Category | | DBot Status | Playbook | DBot Created | | DBot Closed | SLA | DBot Modified | | DBot Total Time | Close Reason | Close User | | Close Notes | Reminder | Labels | | Run Status | Dropped Count | Linked Count | | Feed Based | | | {% hint style="info" %} ### Note You can also configure mappers for indicators, by going to **Settings** → **OBJECTS SETUP** → **Indicators** → **Classification & Mapping**. {% endhint %} 1. Go to Settings → OBJECTS SETUP → Incidents → **Classification & Mapping**. 2. Click **New** and select the mapper that you want to create. * Incident Mapper (Incoming) - maps all of the fields you are pulling from the integrations to the incident fields in your layouts * Incident Mapper (Outgoing) - maps fields from Cortex XSOAR to the fields in the integration to which you are pushing the data. This is useful for mirroring. * Indicator Mapping (Incoming) - maps all of the indicator fields to their indicator layout.

Note

For indicators ingested with a Feed Integration, indicator classification and mapping is done in the integration code and not in the Cortex XSOAR Settings > OBJECTS SETUP > Indicators > Classification & Mapping tab. For example, see the FeedUnit42v2 integration.

3. Under **Get data**, select from where you want to pull the information based on which you will map the incident types. * Pull from instance - select an existing integration instance. Select schema - when supported by the integration, this will pull all of the fields for the integration from the database. This enables you to see all of the fields for each given event type that the integration supports. * Upload JSON - upload a formatted JSON file which includes the field you want to map. 4. Under **Incident Type**, start by mapping out the **Default Mapping**. This mapping includes the fields that are common to all of the incident types and will save you time having to define these fields individually in each incident type. 5. Click the event attribute to which you want to map. You can further manipulate the field using filters and transformers. You can click **Auto Map**to automatically map fields with common or similar names to fields in Cortex XSOAR. For example, Severity to Importance or Description to Description. 6. Repeat this process for the other incident types for which this mapping is relevant. 7. Click **Save**. 8. Go to Settings → Integrations → **Instances**. 1. Select the integration to which you want to apply the mapper. 2. In the integration settings, under **Mapper**, select the classifier you created and click **Done**. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/classification-and-mapping/create-a-mapper.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.