AI Prompt Feature | XSIAM Version 3.4

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AI Prompt Feature | XSIAM Version 3.4

L2 Linker

Hi All,

Does anyone tested the AI prompt feature in XSIAM version 3.4?

From our experience, only generic prompts seem to be working. When we try to use specific real-time case or issue data, it doesn't respond as expected.

We haven't been able to test out-of-the-box or custom prompts using input data like Issue ID or Issue Name, as the AI prompt can't access real-time data for analysis.

 

Has anyone else encountered this issue? 

5 REPLIES 5

L5 Sessionator

Hello @A.Velusamy ,

 

Greetings for the day.

 

In Cortex XSIAM version 3.4, the AI prompt feature (often associated with the Agentic Assistant or AgentiX) requires specific variable mapping and syntax to access real-time case or issue data. Based on internal investigations and engineering guidance, simply inputting a static Issue ID or Name is insufficient because the AI model needs a reference to the actual context object to perform analysis.

Key Requirements for Accessing Real-Time Data:

Use Correct Variable Syntax

When executing prompts like IssueSummaryAndRemediation, you must provide the path to the issue object in the context rather than a manual ID string. The required syntax (based on the AI Prompts playbook) is:

!IssueSummaryAndRemediation issue=${issue}
 

Execution Environment:

These prompts must be run from a location where the issue context is natively available, such as:

  • The Issue War Room

  • A Playbook within the issue's work plan

Running them from a Playground environment without a loaded context will result in failures or generic responses.

Core Integration Dependency

The AI Agent relies on the Cortex Platform - Core integration to interact with cases and issues.

Ensure that:

  • The Cortex Platform - Core content pack is installed from the Marketplace.

  • An integration instance is configured and enabled under Settings > Data Sources > Integrations.

If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution".

 

Thanks & Regards,
S. Subashkar Sekar

Hi,


@susekar wrote:

These prompts must be run from a location where the issue context is natively available, such as:

  • The Issue War Room

  • A Playbook within the issue's work plan


this is not true. I tested this just now in an arbitrary XQL tab in our environment (no issue context), and was able to access arbitrary issues, see screenshot. The !IssueSummaryAndRemediation issue=12345 was working for me, although the assistant did not recognize the command (no autocomplete). I'm not sure if the agentic assistants support the old !command syntax at all. 

@A.Velusamy There might be some setup steps still missing in your environment as mentioned by @susekar , we also needed to activate an additional integation for the Agentic Assistant to work. Would be nice if this information ("this option is not supported because the integartion xx is not enabled") would be a output from the assistant instead of "I can't do that", but hey. 

 

We are not really impressed by the Agentic Assistants so far. There are a couple of examples where the functionalities are really impressive, like the following prompt (which was also shown in a webcast):

This completed successfully including a completed XQL search (although the assistant did extract the links to other unit42 blocks as IOCs). 

 

On the other side, assistants currently fail to generate even the most basic xql queries that don't contain hallucinated commands, we have a support case open for this. 

 

Edit: "Fun" fact: if you use a different prompt for basically the same request, you get much more detailed summary, see second screenshot. 

L2 Linker

Yes, AI prompt is not working in the issue war room as well as  in the playbook but if we use this command -!IssueSummaryAndRemediation issue=1234 in Agentic Assistant it provides the summary. See the screenshot attached.  It won't be helpful if palo alto provides some proper information about this.

I have enabled and tested - Cortex Platform - Core. 

L0 Member

I don’t think running the command inside an Agentic Assistant chat is how AI Prompts it’s intended to be used. Agentic interprets the command as the task it needs to perform, rather than actually executing the prompt.

 

I had the same problem, and what @susekar recommended worked for me. I put the prompt into a playbook, and in the input I directly used ${issue}—I didn’t reference specific variables, I just passed the entire alert

So far it worked, whereas before it didn’t (I was getting the same issue as the creator of this topic.)

If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution".

 

Thanks & Regards,
S. Subashkar Sekar

  • 2533 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!