For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex XDR

AWS Security Hub finding format

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

Cortex XDR 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:

Issue field
ASFF field
Mapping

Issue ID

Id

issue/<issue_id>.

Issue name

Title

If the issue has no name, the value is Cortex Issue <issue_id>.

Issue description

Description

If the issue has no description, the value is the issue name.

Detection method and rule ID

GeneratorId

<detection_method>/<rule_id>.

Observation time

CreatedAt, FirstObservedAt, LastObservedAt

ISO 8601 timestamp.

Last modified time

UpdatedAt

ISO 8601 timestamp.

Severity

Severity, FindingProviderFields.Severity

Domain and category

Types, FindingProviderFields.Types

MITRE ATT&CK tactics and techniques

Types, FindingProviderFields.Types

TTPs/<tactic>. If the issue has exactly one tactic, each technique is added as TTPs/<tactic>/<technique>.

Asset IDs

Resources

One resource of type Other for each asset. If the issue has no assets, the resource ID is cortex/issue/<issue_id>.

Status

RecordState, ProductFields["cortex/progress"]

Resolved issues are ARCHIVED. All other issues are ACTIVE.

Remediation

Remediation.Recommendation.Text

Included only if the issue has remediation text.

Assignee and resolution comment

Note.Text

Included only if the issue has an assignee or a resolution comment.

Tags

ProductFields["cortex/tag/<tag_name>"]

The value is "true".

Custom fields

ProductFields["cortex/custom/<field_name>"]

The field value as a string.

Domain, category, detection method, rule ID, external ID, issue type

ProductFields["cortex/<field_name>"]

Included only if the issue field has a value.

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 XDR severity

Severity.Label

Severity.Normalized

Informational

INFORMATIONAL

0

Low

LOW

20

Medium

MEDIUM

50

High

HIGH

80

Critical

CRITICAL

95

The original Cortex XDR 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 XDR 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 XDR 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:

Last updated

Was this helpful?