PANW Cortex XDR - Scan Endpoints

PANW Cortex XDR - Scan Endpoints triggers a scan on endpoints managed by Cortex XDR for:

  • Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

📘

Note


Required Fields

These fields must be configured to run the Enforcement Action.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values (optional) - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
  • Use stored credentials from the PaloAlto XDR adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.

    • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

      📘

      Note

      To use this option, you must successfully configure a Palo Alto Networks Cortex XDR adapter connection.

  • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Additional Fields

This Enforcement Action does not have additional optional fields.

⚠️

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

  • Cortex XDR Domain - The hostname of the Palo Alto Networks Cortex XDR API server. Example: api-CUSTOMER.xdr.us.paloaltonetworks.com
  • URL Base Path - The fully qualified domain name (FQDN). For more details, see Get Started with Cortex XDR APIs.
  • API Key ID - The API key ID of an Advanced Security Level API, as generated in Cortex XDR app. A standard API key will not work — this integration requires an Advanced Security level API key.
  • API Key - The API key of an Advanced Security Level API, as generated in Cortex XDR app.
  • Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

  • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

  • Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the Cortex XDR Scan Endpoints API - POST /public_api/v1/endpoints/scan

Required Ports

Axonius must be able to communicate via the following ports:

  • TCP port 80/443

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the necessary permissions to perform this enforcement action.

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

The following permissions and requirements are needed:

  • An Advanced Security Level API key must be generated in the Cortex XDR app. A standard API key will not work.
  • For details on generating an Advanced Security Level API, see Get Started with Cortex XDR APIs.
  • The API key must be associated with credentials that have the following permissions:
    • Endpoint Administration - Scan endpoints permission
    • Assets - Network config - View

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

VersionSupportedNotes
Cortex XDR 3.xYesTested with Cortex XDR REST API v1
Cortex XDR 4.xYesTested with Cortex XDR REST API v1
Cortex XDR 5.xYesTested with Cortex XDR REST API v1