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!

Improve Your Security Posture

Watch NowImprove Your Security PostureCustomers are at the center of everything we do at Splunk and security ...

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...