This repository has been archived by the owner on Mar 17, 2022. It is now read-only.
ParseURLAnalyzer && FQDNAnalyzer && more configurable IPIAnalyzer #67
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I wanted to resolve the FQDN of URL observables for IPV4 inspection after I noticed we would have alerted on something we didn't because of network blacklisting.
I added the following very simple modules:
I debated turning on both of those by default but did not. They're disabled by default.
Also, this PR includes some code I needed for the ip_inspector module to be more configurable.