Nessus parser for gowitness #123
Merged
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
|
Great thank you! 🙌 |
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.
As mentioned in #69 added the nessus parser into gowitness.
Used your parser at https://gist.github.com/leonjza/bb977e98eac9565fae2aa177e498d9b8
I've made a couple of default assumptions based on looking over some nessus XML files.
First, the "best" plugin for identifying web servers appears to be the "Service Detection" plugin.
Next, filtering the service name off of "www" and "https" appears to get most of the web servers in my analysis. However, several VPN clients have special service names and I had to add in another filter of plugin output contains "web server" to catch the rest of the items.
If there's a better plugin to use it should be easy enough to modify this code. Using plugin IDs might have been more clean, but the name seems fine.
I also required need for a plugin search in this code (matching on "Service Detection" ) because it seems like a waste of resources to search through the entire XML and end up with a map full of thousands of duplicates. That's the reasoning behind it.