> 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/onboard-cortex-xsiam/post-deployment/data-and-log-forwarding/data-and-log-notification-formats/aws-security-hub-finding-format.md).

# AWS Security Hub finding format

How Cortex XSIAM maps issue fields, severities, finding types, and MITRE ATT\&CK data to AWS Security Finding Format (ASFF) findings forwarded to AWS Security Hub.

Cortex XSIAM forwards issues to AWS Security Hub as findings in the AWS Security Finding Format (ASFF).

### Issue to ASFF field mapping

The following table describes how issue fields map to ASFF fields:

<table><thead><tr><th>Issue field</th><th>ASFF field</th><th width="254">Mapping</th></tr></thead><tbody><tr><td>Issue ID</td><td>Id</td><td>issue/&#x3C;issue_id>.</td></tr><tr><td>Issue name</td><td>Title</td><td>If the issue has no name, the value is Cortex Issue &#x3C;issue_id>.</td></tr><tr><td>Issue description</td><td>Description</td><td>If the issue has no description, the value is the issue name.</td></tr><tr><td>Detection method and rule ID</td><td>GeneratorId</td><td>&#x3C;detection_method>/&#x3C;rule_id>.</td></tr><tr><td>Observation time</td><td>CreatedAt, FirstObservedAt, LastObservedAt</td><td>ISO 8601 timestamp.</td></tr><tr><td>Last modified time</td><td>UpdatedAt</td><td>ISO 8601 timestamp.</td></tr><tr><td>Severity</td><td>Severity, FindingProviderFields.Severity</td><td>See <a href="#severity-mapping">Severity mapping</a>.</td></tr><tr><td>Domain and category</td><td>Types, FindingProviderFields.Types</td><td>See <a href="#finding-type-mapping">Finding type mapping</a>.</td></tr><tr><td>MITRE ATT&#x26;CK tactics and techniques</td><td>Types, FindingProviderFields.Types</td><td>TTPs/&#x3C;tactic>. If the issue has exactly one tactic, each technique is added as TTPs/&#x3C;tactic>/&#x3C;technique>.</td></tr><tr><td>Asset IDs</td><td>Resources</td><td>One resource of type Other for each asset. If the issue has no assets, the resource ID is cortex/issue/&#x3C;issue_id>.</td></tr><tr><td>Status</td><td>RecordState, ProductFields["cortex/progress"]</td><td>Resolved issues are ARCHIVED. All other issues are ACTIVE.</td></tr><tr><td>Remediation</td><td>Remediation.Recommendation.Text</td><td>Included only if the issue has remediation text.</td></tr><tr><td>Assignee and resolution comment</td><td>Note.Text</td><td>Included only if the issue has an assignee or a resolution comment.</td></tr><tr><td>Tags</td><td>ProductFields["cortex/tag/&#x3C;tag_name>"]</td><td>The value is "true".</td></tr><tr><td>Custom fields</td><td>ProductFields["cortex/custom/&#x3C;field_name>"]</td><td>The field value as a string.</td></tr><tr><td>Domain, category, detection method, rule ID, external ID, issue type</td><td>ProductFields["cortex/&#x3C;field_name>"]</td><td>Included only if the issue field has a value.</td></tr></tbody></table>

### Fixed ASFF values

The following table lists ASFF fields that have fixed or account-derived values:

| **ASFF field** | **Value**                                                                            |
| -------------- | ------------------------------------------------------------------------------------ |
| SchemaVersion  | 2018-10-08                                                                           |
| CompanyName    | Palo Alto Networks                                                                   |
| ProductName    | Cortex                                                                               |
| ProductArn     | arn:\<partition>:securityhub:\<region>:\<account\_id>:product/\<account\_id>/default |
| AwsAccountId   | The Account Id configured in the AWS Security Hub instance.                          |

The partition is aws for commercial regions, aws-us-gov for AWS GovCloud (US) regions, and aws-cn for AWS China regions.

### Severity mapping

| **Cortex XSIAM severity** | **Severity.Label** | **Severity.Normalized** |
| ------------------------- | ------------------ | ----------------------- |
| Informational             | INFORMATIONAL      | 0                       |
| Low                       | LOW                | 20                      |
| Medium                    | MEDIUM             | 50                      |
| High                      | HIGH               | 80                      |
| Critical                  | CRITICAL           | 95                      |

The original Cortex XSIAM severity is preserved in **Severity.Original**. Unrecognized severities map to **INFORMATIONAL**.

### Finding type mapping

The following table describes the finding type mapping:

| **Issue domain**             | **Issue category** | **ASFF type**                                                       |
| ---------------------------- | ------------------ | ------------------------------------------------------------------- |
| Security                     | Vulnerability      | Software and Configuration Checks/Vulnerabilities                   |
| Security                     | Malware            | TTPs/Defense Evasion                                                |
| Security                     | Configuration      | Software and Configuration Checks                                   |
| Security                     | Identity           | TTPs/Credential Access                                              |
| Security                     | Data               | Sensitive Data Identifications                                      |
| Posture                      | Any                | Software and Configuration Checks/Industry and Regulatory Standards |
| Health                       | Any                | Software and Configuration Checks/Operational                       |
| Hunting                      | Any                | TTPs                                                                |
| IT                           | Any                | Software and Configuration Checks/Operational                       |
| Any other domain or category | Any                | Software and Configuration Checks                                   |

### Fields that Cortex XSIAM doesn't set

* **Workflow**: AWS Security Hub reserves this field for customer updates and adds it when it receives the finding.
* **UserDefinedFields**: AWS Security Hub reserves this field for customer updates. Cortex XSIAM sends tags and custom fields in ProductFields.
* **Region and ProcessedAt**: AWS Security Hub adds these fields when it receives the finding.

### Example ASFF finding

The following is an example of a finding for an issue with one MITRE ATT\&CK tactic and one technique:

```
{
  "SchemaVersion": "2018-10-08",
  "Id": "issue/862",
  "ProductArn": "arn:aws:securityhub:ap-northeast-1:123456789012:product/123456789012/default",
  "CompanyName": "Palo Alto Networks",
  "ProductName": "Cortex",
  "GeneratorId": "ANALYTICS_BIOC",
  "AwsAccountId": "123456789012",
  "Types": [
    "Software and Configuration Checks",
    "TTPs/Lateral Movement",
    "TTPs/Lateral Movement/Pass the Hash"
  ],
  "CreatedAt": "2026-10-04T21:08:03.986000Z",
  "UpdatedAt": "2026-10-04T21:08:03.986000Z",
  "FirstObservedAt": "2026-10-04T21:08:03.986000Z",
  "LastObservedAt": "2026-10-04T21:08:03.986000Z",
  "Severity": {
    "Label": "LOW",
    "Normalized": 20,
    "Original": "LOW"
  },
  "FindingProviderFields": {
    "Severity": {
      "Label": "LOW",
      "Original": "LOW"
    },
    "Types": [
      "Software and Configuration Checks",
      "TTPs/Lateral Movement",
      "TTPs/Lateral Movement/Pass the Hash"
    ]
  },
  "Title": "Suspicious SMB connection from domain controller",
  "Description": "DC1ENV4ADC02 has initiated a session to 172.16.4.133 over SMB (port 445).",
  "Resources": [
    {
      "Type": "Other",
      "Id": "cortex/issue/862"
    }
  ],
  "RecordState": "ACTIVE",
  "ProductFields": {
    "cortex/module_owner": "PLATFORM",
    "cortex/progress": "NEW",
    "cortex/domain": "SECURITY",
    "cortex/category": "Lateral Movement",
    "cortex/detection_method": "ANALYTICS_BIOC",
    "cortex/external_id": "ededc4b7-7cc4-4278-8640-ebe5183b6ee5",
    "cortex/tag/DOM:Security": "true",
    "cortex/tag/DS:PANW/XDR Agent": "true"
  }
}
```


---

# 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/onboard-cortex-xsiam/post-deployment/data-and-log-forwarding/data-and-log-notification-formats/aws-security-hub-finding-format.md?ask=<question>&goal=<user_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.
