Ubiquiti add-on for Splunk
Overview
Details
To make this TA work fully CIM compliant follow the instructions on routing the different Sourcetypes to their individual indexes.
If you have any questions or would like to see additional field extract please reach out to me.
More info here:
https://github.com/fwijnholds/ta-ubiquiti-support/wiki/Ubiquiti-Support
Installing and configuring Ubiquito add-on for Splunk
To use this TA with Enterprise Security some configuration is required. Datamodel acceleration at scale requires from the deployment that data is assigned to indexes by it's cardinality. As Sourcetype is assigned by input in Splunk there are 2 ways achieving this split. One is using transforms.conf in conjuction with a props.conf, the other is by having an intermediate like a syslog server do the splitting into files. A UF can assign sourcetype input.
Method 1:
If you want to use this add-on on a single instance, with full CIM compatability follow these steps:
Download transforms.conf-single and rename to transforms.conf.
https://github.com/fwijnholds/ta-ubiquiti-support/blob/master/transforms.conf-single.conf
This file holds the configuration which rewrites the sourcetype based on a patern match, and routes the traffic to the correct index.
Download props.conf-single and rename to props.conf. https://github.com/fwijnholds/ta-ubiquiti-support/blob/master/props.conf-single
This file holds the configuration which rewrites the sourcetype based on a patern match, and routes the traffic to the correct index. Place transforms.conf in the ta-ubiquiti/local directory. Place props.conf in the ta-ubiquiti/local directory.
Download and install the org_all_indexes.spl
https://github.com/fwijnholds/ta-ubiquiti-support/blob/master/org_all_indexes.spl
note: This contains a standard set of indexes, the Splunk best practice for CIM you will note that it separates OS logs from Network logs and Security logs from Application logs. The idea here is to separate them for performance reasons, but also for isolation purposes-you may want to expose the application or system logs to people who shouldn't view security logs. Putting them in separate indexes prevents that.
Restart splunk
In the UI navigate to Settings -> Data Inputs
Add a new input for UDP
Enter the port which you would like to receive the data on
Select any ubqt sourcetype ie ubqt:fw, change settings to your liking with the exception of indexes. Or manually create inputs.conf
[udp://8514]
connection_host = ip
sourcetype = ubqt
index=ubqt
Method 2:
For deployment with a syslog server the recomendation is to use a Universal forwarder on your rsyslog or syslog-ng server. Have the syslog server write a file per sourcetype and have the UF assign the sourcetype to the specific logs. More information will follow.
Check the latest updates: https://github.com/fwijnholds/ta-ubiquiti-support
Release Notes
Version 1.3.4
This release adds support for the Dream Machine. With special thanks to Michael Nobles!
The firewall and DHCP logs have a different format coming from the Dream machine. This release fixes that.
This release also has support for the new dnsmasq logs that have appeared after the 6.0 firmware release.
Version 1.2
Added support for field extractions for connecting and reconnecting clients with the help of Nathan T.
Added support for Edge switches with the help of John W.
Fixed some issues with extractions.
Version 1.1.23
Added sourcetype and extractions for linkspeed checks.
Version 1.1.22
Fixed FW rule extraction.
Sourcetype renamed from everything ubqt to ubnt.
Version 1.1.21
Bug fixes in source type matches..
Version 1.1.20
Version 1.1.18
Version 1.1.16
In the latest firmware releases of cloud controller and USG the MAC= field now contains src and dest mac. You might want to check your deployment before updating.
Update mac field extractions
Renamed fw_rule to rule as this is CIM compliant.
TA is now set to visible
Version 1.1.15
Enabled the transforms for IPS.
VERSION: 1.1.14
Found major issues with the transforms concerning source-types and index during a clean install, These should be fixed in this release.
VERSION: 1.1.13
Sourcetype fixing
Added support for the BETA IPS functionality
Normalized mac address reporting for hostapd
Improved hostapd extractions
Improved hostapd sourcetyping and added field extractions.
Special thanks to Corey Falo at Ubiquiti for his support, and Paul Jeffery at Splunk for his input!
For any questions or contributions please contact me @ goose@splunk.com
Version 1.1.15
Enabled the transforms for IPS.
VERSION: 10.1.14
Found major issues with the transforms concerning source-types and index during a clean install, These should be fixed in this release.
VERSION: 10.1.13
Sourcetype fixing
Added support for the BETA IPS functionality
Normalized mac address reporting for hostapd
Improved hostapd extractions
Improved hostapd sourcetyping and added field extractions.
VERSION: 1.1.12
Special thanks to Corey Falo at Ubiquiti for his support, and Paul Jeffery at Splunk for his input!
For any questions or contributions please contact me @ goose@splunk.com
Special thanks to Corey Falo at Ubiquiti for his support, and Paul Jeffery at Splunk for his input!
For any questions or contributions please contact me @ goose@splunk.com
Version 1.1.14
Found major issues with the transforms concerning source-types and index during a clean install, These should be fixed in this release.
VERSION: 10.1.13
Sourcetype fixing
Added support for the BETA IPS functionality
Normalized mac address reporting for hostapd
Improved hostapd extractions
Improved hostapd sourcetyping and added field extractions.
VERSION: 1.1.12
Special thanks to Corey Falo at Ubiquiti for his support, and Paul Jeffery at Splunk for his input!
For any questions or contributions please contact me @ goose@splunk.com
Special thanks to Corey Falo at Ubiquiti for his support, and Paul Jeffery at Splunk for his input!
For any questions or contributions please contact me @ goose@splunk.com
Version 1.0.9
This is the first release of the TA for Ubiquiti. It was developed for an environment with CloudKey, USG and Pro AP. This release supports field extractions for the Firewall and DHCP facilities. It requires 3 indexes; UBQT, netdhcp and netfw. The net* indexes are there for CIM compliance