All Apps and Add-ons

Significant issues with props.conf in Splunk Add-on Cisco for ASA

ckurtz
Path Finder

The sourcetype declarations in default/props.conf are severely flawed, and would make changes far outside the scope of the app if implemented as they are now.

Each sourcetype includes unacceptable wildcards (such as "everything ending in asa" and ("all tcp/udp inputs") that are very dangerous. Examples for the file:

[source::....asa]
sourcetype = cisco:asa
[source::tcp*]
TRANSFORMS-x = force_sourcetype_for_cisco_asa
[source::udp*]
TRANSFORMS-x = force_sourcetype_for_cisco_asa

At the very least, these should be commented out and have instructions on how to specify the user's own cisco asa sourcetype.

1 Solution

jbsplunk
Splunk Employee
Splunk Employee

Agreed, these issues have been reported to Splunk internally and will be evaluated for the next major release of this particular app. At this point, no ETA exists.

View solution in original post

jbsplunk
Splunk Employee
Splunk Employee

Agreed, these issues have been reported to Splunk internally and will be evaluated for the next major release of this particular app. At this point, no ETA exists.

Get Updates on the Splunk Community!

Splunk Forwarders and Forced Time Based Load Balancing

Splunk customers use universal forwarders to collect and send data to Splunk. A universal forwarder can send ...

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...

Last Chance to Submit Your Paper For BSides Splunk - Deadline is August 12th!

Hello everyone! Don't wait to submit - The deadline is August 12th! We have truly missed the community so ...