Open
Conversation
Contributor
Author
|
Marking as draft, until i get the fixes deployed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The old Suricata TA was nuked out from Splunkbase for "unknown reasons". We've identified a replacement TA that does the same parsing (overall). This PR aims to use that TA and update corresponding DS and
contentctl.ymlfiles. Below is the summary of the changesSummary
Because the new TA has a different parsing for the URL field (and a bunch of other fields) we had to make some changes. The CCX TA uses an eval to get the value of the URL CIM field, as follow
Which means the URL is usually a combination of
http.urlandhttp.hostname.In contrast, the old TA was simply doing an alias to URL form http.url (which is technically incorrect). Since
http.urlactually contains the URI.In practice, this means that we have to add a wildcard at the start of most of the analytic using the URL logic. Since it will be prefixed with the hostname. Most of the time this will not be an issue as long as the anchor string is long. I've only identified a couple of analytics suffering from small anchors and have proposed a fix. See details below.
Updated Analytics
As explained above most analytics have seen an addition of a wildcard character at the start of the string. I also took the time to update their metadata when needed and beautified the YAML/SPL. I will only detail meaningful fixes below.
Disable Schedule Task/Wscript Or Cscript Suspicious Child Processboth of these analytics we demoted toAnomalybut never saw their score reduced. Hence I've updated them here.Adobe ColdFusion Access Control Bypass- Update the logic to remove non double slash URLs. Since according to the reference they are not needed.HTTP Request to Reserved Name on IIS Server- This analytic suffered from a short anchor logic. Hence I've updated the search to reduce FP by adding an extra check after the tstats.Deprecated Analytics
Ivanti Sentry Authentication Bypass- After checking the reference, there is no strong IOC to catch this behavior and the actual analytic is weak. Hence it was deprecated.