Signal Sciences NG WAF/RASP - TA
Overview
Details
This is an open source project, no support provided, public repository available and installation documentation can be found a https://github.com/dacoburn/sigsci-splunk-app . The best way to report issues with the App is to create an Issue on the github page so that it can be tracked.
Installation and configuration information can be found at the github page
Release Notes
Version 1.0.19
- Added back in the props.conf as it was accidentally excluded from 1.0.18
Version 1.0.18
- Added support for Proxy configuration
- Updated splunklib to the latest version
- Used new method for App configuration instead of the old setup view
- Added Help messages for the configuration options
Version 1.0.17
1.0.17
- Fixed requirement for app.conf for Splunk Cloud Support, wasn't correctly fixed in 1.0.16.
1.0.15
- Updated props.conf for time issue https://github.com/dacoburn/sigsci-splunk-app/issues/2
1.0.14
- Fixed issue with timestamp not being found by adding TIME_PREFIX = timestamp . Previously the JSON could be to large for the default look ahead to find the timestamp element. This way the look ahead starts from the timestamp object.
- Linted and fixed formatting of python scripts
- Removed default Data Inputs for Requests and Events as this was keeping you from being able to delete them and caused isues.
IMPORTANT NOTE: If you had modified the default example Data Input you will need to go back and re-add the "5" for the Delta. Otherwise this will default to 0 and no data will be pulled.
New Features:
- Added support for the new API Tokens. You can either use the Username/API Token or the Username/Password combo. If both are filled in the API Token will take precedence.
Version 1.0.16
1.0.16
- Fixed requirement for app.conf for Splunk Cloud Support.
1.0.15
- Updated props.conf for time issue https://github.com/dacoburn/sigsci-splunk-app/issues/2
1.0.14
- Fixed issue with timestamp not being found by adding TIME_PREFIX = timestamp . Previously the JSON could be to large for the default look ahead to find the timestamp element. This way the look ahead starts from the timestamp object.
- Linted and fixed formatting of python scripts
- Removed default Data Inputs for Requests and Events as this was keeping you from being able to delete them and caused isues.
IMPORTANT NOTE: If you had modified the default example Data Input you will need to go back and re-add the "5" for the Delta. Otherwise this will default to 0 and no data will be pulled.
New Features:
- Added support for the new API Tokens. You can either use the Username/API Token or the Username/Password combo. If both are filled in the API Token will take precedence.
Version 1.0.15
1.0.15
- Updated props.conf for time issue https://github.com/dacoburn/sigsci-splunk-app/issues/2
1.0.14
- Fixed issue where the build script was not correctly updating some of the python files for the version
- Fixed issue with timestamp not being found by adding TIME_PREFIX = timestamp . Previously the JSON could be to large for the default look ahead to find the timestamp element. This way the look ahead starts from the timestamp object.
- Linted and fixed formatting of python scripts
- Removed default Data Inputs for Requests and Events as this was keeping you from being able to delete them and caused isues.
IMPORTANT NOTE: If you had modified the default example Data Input you will need to go back and re-add the "5" for the Delta. Otherwise this will default to 0 and no data will be pulled.
New Features:
- Added support for the new API Tokens. You can either use the Username/API Token or the Username/Password combo. If both are filled in the API Token will take precedence.
Version 1.0.14
Bugs Fixed:
- Fixed issue where the build script was not correctly updating some of the python files for the version
- Fixed issue with timestamp not being found by adding TIME_PREFIX = timestamp . Previously the JSON could be to large for the default look ahead to find the timestamp element. This way the look ahead starts from the timestamp object.
- Linted and fixed formatting of python scripts
- Removed default Data Inputs for Requests and Events as this was keeping you from being able to delete them and caused isues.
IMPORTANT NOTE: If you had modified the default example Data Input you will need to go back and re-add the "5" for the Delta. Otherwise this will default to 0 and no data will be pulled.
New Features:
- Added support for the new API Tokens. You can either use the Username/API Token or the Username/Password combo. If both are filled in the API Token will take precedence.
Version 1.0.13
This release includes improvements for:
- Changed default behavior of modular scripts from single_instance = True to single_instance = false. This means that there will be a unique execution of the script for each data input configured. This is important so that if one of the Data inputs causes an error it won't effect the other ones. Also for sites with high RPS it can potentially take to long to have the data be pulled sequentially instead of concurrently.
1.0.12 Improvements:
- Retry behavior if rate limiting for pulling details is hit
- More efficient methods for writing events. Previously as the events were detected they were being written out. Now to improve the Script performance the event write call is done after all items are pulled from SigSci
- Better error handling if the URL is not correctly built do to wrong entries being configured in the app settings
- User-Agent string update to be recognizable as the SigSci Splunk app
Version 1.0.11
- Fixed issue with regression for empty response headers
- Fixed issues where upgrade backups were left in the Splunk App Folder
Version 1.0.10
- Accidentally reverted the fix for requests with no Response headers from 1.08 when releasing 1.09. This fix has been added back in.
Version 1.0.9
- Refactored Module Input script to support when multiple sites are setup for Requests or Events. Before it would cause things to error out.
Version 1.0.8
- Removed logging out of Token when debug logging is enabled.
Version 1.0.7
- Fixed issue with time calculations not being correct and leading to potential errors from the API or getting unexpected time periods pulled back for the Requests API.
- Fixed issue where output format from SigSci is not optimal for header data. Header Data will now be properly sortable. The result from the API currently returns a JSON object of a list of lists for the headers so the header entries were showing in a format of [Header, Value] instead of {"header": "value"}