Things like ingest actions or even the new edge processor could this this.
However, one thing Id recommend if these fields are always null values in every event is that you can remove them from being being sent in the first place using log filters on the palo cortex side. You can pick and chose what fields are included in the HTTP export that is sent to Splunk.
You have to configure props.conf & transforms.conf to filter your data for reduction.
Check out following Splunk Docs and Splunk Answer thread with a similiar question.