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

Perform advanced Identity Security investigations using XQL

Use XQL in Cortex XSIAM to investigate Cloud Identity Security permissions, identity risks, and access data.

Requires a Cloud Posture Security, Cloud Runtime Security, or Cortex XSIAM Premium license.

Overview

Use Cortex Query Language (XQL) in Cortex XSIAM to investigate Cloud Identity Security permissions, access, identity risks, findings, and issues. Query identity datasets to identify security gaps and guide remediation.

For more information, see Get started with XQL.

You can use the following identity-related datasets:

Dataset
Description

ciem_permissions_with_last_access

Contains the permissions of each identity that is discovered in your environments, including the time of their last access when applicable.

asset_inventory

Contains an inventory of all the assets that are discovered in your environments. For more information, see Asset management.

issues

Contains the issues that are related to the assets in your environments. For more information, see Issues.

findings

Contains the findings that are associated with the assets that are found in your environments. For more information, see Findings and events.

Investigate Cloud Identity Security in Cortex XSIAM

To run queries on your Cloud Identity Security datasets:

  1. In Cortex XSIAM, in the navigation pane on the left, click Investigation & Response, then under Search, click XQL Search.

  2. On the XQL Search screen, under XQL Query, in the text box, start typing your query. Alternatively, you can search for existing queries on the Query Library tab.

  3. When you have finished entering your query, click Run. The results appear on the Query Results tab.

For more information, see Build XQL queries.

Example XQL queries for Identity Security

Use these XQL queries in Cortex XSIAM to investigate your identity security posture:

1. Count the number of admin sources per account
2. Azure service principals granting write permissions on the subscription level
3. Group permissions on production assets
4. Users without MFA and sensitive S3 and EC2 permissions
5. Azure VM with data write permissions on the subscription levels
6. Policies granting wildcard permissions
7. Administrative roles open to third-party vendors and external unknown accounts
8. Show identities with unused permissions
9. Unused permissions by lambda functions
10. Get all the non-admin sources that can assume an admin role
11. Administrative permissions granted to EC2 instances that can access multiple services

Last updated

Was this helpful?