BIOC Rule - CGO V/S Actor_process_image_name

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

BIOC Rule - CGO V/S Actor_process_image_name

L1 Bithead


I wanted to understand, if i want to see certain cmdline activities from "x" Process.

Want to know what will be more efficient putting the "x" process in "Causality_actor_process_image_name"

or in "actor_process_image" while creating a BIOC


L4 Transporter

Hi @meanmach, thanks for reaching us using the Live Community.


If you want to monitor the activity of the "X" process, when "X" is the process calling a cmdline for command execution, the right field is "causality_actor_process_image_name". The "causalty" prefix indicates the parent process in the execution chain, and should work in this case.

You can find some interesting information about all the xdr_data dataset fields here:


If this post answers your question, please mark it as the solution.


L1 Bithead

Thanks a lot for the information however i want to understand if i use the actor_process_image_name field is that logic wrong?  as in BIOC rule given by Palo Alto to detect recon Activity via Web shell they have used "actor_process_image_name" = "w3wp.exe"


  • 2 replies
  • 78 Subscriptions
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!