Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PA firewall logs ingested in Splunk Cloud without field extractions #325

Open
dchen-ae opened this issue Mar 21, 2024 · 2 comments
Open
Labels

Comments

@dchen-ae
Copy link

Describe the bug

PA firewall logs ingested in Splunk Cloud without field extractions.

Expected behavior

pan:firewall sourcetype should be transformed into pan:traffic, pan:threat, pan:system, pan:config with fields extracted

Current behavior

pan:firewall sourcetype is not being transformed and field extractions are not working in Splunk Cloud

Possible solution

If I send the logs from PA -> syslog server -> heavy forwarder -> Splunk Cloud then the logs get fields extracted.
But sending directly from PA -> syslog server -> Splunk Cloud does not work. Fields are not extracted.

Fix PA addon to transform logs when indexed in Splunk Cloud

Steps to reproduce

  1. Configure syslog server to receive logs from PA firewalls
  2. Install Palo Alto Networks Add-on & App in Splunk Cloud
  3. Configure log forwarding in PA firewall to send logs to syslog server
  4. Configure Splunk Universal Forwarder on the syslog server to send PA firewall logs to Splunk Cloud

Context

Would like to send the firewall logs directly to Splunk Cloud and remove the dependency on a heavy forwarder.

Your Environment

Splunk Cloud Version: 9.1.2308.203
Palo Alto Networks Add-on for Splunk: 8.1.1
syslog-ng: 4.6
PA firewall: 10.2.7-h3

Palo Alto - Syslog Server Profile
Transport: TCP
Port: 514
Format: BSD
Facility: LOG_USER
Custom Log Format: Default

@dchen-ae dchen-ae added the bug label Mar 21, 2024
@arcsector
Copy link

arcsector commented May 1, 2024

What does your data look like?

@dchen-ae
Copy link
Author

dchen-ae commented May 3, 2024 via email

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

No branches or pull requests

2 participants