DDS: SpyCloud: Threat Intel Integration Without Assets#23509
Open
jaypatel7-crest wants to merge 2 commits intoDataDog:masterfrom
Open
DDS: SpyCloud: Threat Intel Integration Without Assets#23509jaypatel7-crest wants to merge 2 commits intoDataDog:masterfrom
jaypatel7-crest wants to merge 2 commits intoDataDog:masterfrom
Conversation
domalessi
reviewed
Apr 29, 2026
Contributor
domalessi
left a comment
domalessi
left a comment
There was a problem hiding this comment.
Approving, since this is just a skeleton and is not displayed publicly.
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
2 participants
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.
What does this PR do?
PR includes skeleton of SpyCloud threat intel integration without any assets like dashboards, image, README content, etc.
Motivation
This is beta release of crawler integration and is intended for internal testing before going live. As per @nathanmadams's
suggestion, we will raise separate PR with assets and all necessary information later.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged