Skip to content
This repository has been archived by the owner on Dec 14, 2024. It is now read-only.

Incorrect Field Mapping - PAN Threat - User Field (mapped with http category - Sender) #297

Open
dharmanr opened this issue May 25, 2023 · 3 comments

Comments

@dharmanr
Copy link

We have observed the props enabled with comma separated defined fields and its mapped with incorrect values..

User field mapped with the value (music-low risk, private IP addressed) which is actually http category and its mapped to sender.

https://splunkbase.splunk.com/app/2757

EVAL-user = case(SourceUser!="null",'SourceUser',SourceUserName !="null",'SourceUserName',src_user!="null",'src_user',dest_user!="null",'dest_user',recipient!="null",'recipient',sender!="null",'sender',true(),"unknown")

@welcome-to-palo-alto-networks

🎉 Thanks for opening your first issue here! Welcome to the community!

@dharmanr dharmanr changed the title Incorrect Field Mapping - PAN Threat - User Field (mapped with http category) Incorrect Field Mapping - PAN Threat - User Field (mapped with http category - Sender) May 25, 2023
@paulmnguyen paulmnguyen self-assigned this Jun 5, 2023
@paulmnguyen
Copy link
Contributor

Hi @dharmanr Could you please let me know what version of PANOS you are using?

@dharmanr
Copy link
Author

dharmanr commented Jun 8, 2023 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants