Morphisec EPTP Syslog Add-on for Splunk
Description
The purpose of this add-on is to provide value to your Morphisec EPTP syslog logs. This is done by making the logs CIM compliant, adding tagging for Enterprise Security data models, and other knowledge objects to make searching and visualizing this data easy.
This add-on assumes you are onboarding the data either using a syslog collector that outputs to a file or using the built-in Splunk TCP/UDP listener (I would highly recommend the former)--the knowledge objects will work for any ingestion method if you use the correct sourcetype. Regardless of ingestion method, you may need to adjust some of the props.conf settings for proper line breaking and timestamp parsing.
- Built for Splunk Enterprise 6.x.x or higher
- CIM Compliant (CIM 4.0.0 or higher)
- Ready for Enterprise Security
Constraints
- This add-on requires that you use the sourcetype "morphisec:eptp:syslog" when ingesting the data.
- This add-on requires that you choose "CEF" as the Format when configuring Morphisec.
- This add-on requires that you check all logging fields in Morphisec EPTP.
Morphisec Instructions
- In the Morphisec interface, click Settings at the top right of the screen.
- The Settings dialog box appears, with the General tab active. Click the SIEM tab.
- Select Connect to SIEM
- Fill out the Connect, Host, and Port. You can not use "Event Receiver Folder" as a connection option.
- For Format, you must choose "CEF".
- Click Advanced, select "Attack", then select all details. Click save when finished.
INSTALLATION AND CONFIGURATION
- Search Head: Add-on Always Required (Knowledge Objects)
- Heavy Forwarder: Add-on Possibly Required (Data Collection and/or Event Parsing)
- Indexer: Possibly Add-on Required (Data Collection and/or Event Parsing)
- SH & Indexer Clustering: Supported
Add-on Installation Instructions
- This add-on needs to be installed on your Search Head(s) and on the FIRST Splunk Enterprise system(s) that handles the data, traditionally that would be a Heavy Forwarder or Indexer. This add-on should not be deployed to a Universal Forwarder as it won't do anything.
- Make sure you have read and understood the "Constraints" section to properly configure your inputs.conf.
- A Splunk Restart may be required, you may also attempt a debug refresh.
- Verify data is coming in and you are seeing the proper field extractions & sourcetype transforms by searching the data.
- Example Search: index=morphisec sourcetype=morphisec:eptp:syslog
- (Optional, recommended) On your Search Head(s) edit the "morphisec_eptp" Event Type to include the index you're storing this sourcetype in.
Example Inputs.conf
How you choose to bring the syslog data into Splunk is completely up to you. Here are a couple examples of how you might bring on this data:
Built-in Splunk Listener Example
[tcp://9514]
connection_host = dns
sourcetype = morphisec:eptp:syslog
index = morphisec
File Monitor For Syslog-ng Output Example
[monitor:///var/log/network/morphisec_eptp/*/syslog.log]
sourcetype = morphisec:eptp:syslog
index = morphisec
disabled = 0
host_segment = 5
New features
Fixed issues
Known issues
Third-party software attributions
DEV SUPPORT
Contact: splunk-app@hurricanelabs.com
