Ingest entities and relationships #1
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
ndowmon
reviewed
Dec 17, 2020
There was a problem hiding this comment.
Hi @eXtremeX! I spent some time reviewing your PR today since @aiwilliams is out of the office this week. Yet again, another great integration by you. Please let me know what you think about my comments and if you want to discuss anything on a call together.
Cheers!
ndowmon
approved these changes
Dec 23, 2020
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.
This PR includes MalwareBytes' Nebula integration - the entities and relationships that seemed high value/of interest for JupiterOne.
Some links that could be useful to anyone trying to familiarize with MalwareBytes Nebula a bit more:
A lot of back and forth discussion already took place in this Google document.
There is also this document that shows example resources as MB's API returns them and a list of fields we choose to assign to entities - could be useful in figuring out what other fields should be assigned, if something can be changed, and so on.
We don't have any particular questions at this point (mostly thanks to that Google document where we already asked a lot of questions and got the answers), so please just take a look when you can and let us know of your findings! @aiwilliams @ndowmon
The current state of graph:
P.S @aiwilliams we've asked MB sales rep about users API access - he told us that unless it's listed on the API documentation page it simply means it's not supported and that we could ask the API team if something can be arranged.