-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat] PANW Module - SYSTEM and CONFIG logs #15603
Comments
Pinging @elastic/siem (Team:SIEM) |
And userid.. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
#19375 says this is fixed. I didn't have the time to reconfigure our PA syslog output to test this. Will be for 2021.. |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Hi! We're labeling this issue as |
Closing as we're about to begin development on additional PANW datasets and tracking in the integrations repo: elastic/integrations#2988 |
Currently, PANW module is only able to parse and forward THREAT and TRAFFIC pattern logs, other log types - SYSTEM and CONFIG are discarded. For them to be visible , user needs to run another instance of FileBeat, whitelist the events, develop patterns in Logstash for the logs and then send them to elastic search.
We'll also need to map the fields in these logs to ECS.
The text was updated successfully, but these errors were encountered: