[google-secops-siem-incidents] Creation of the connector (#5406)#6322
Open
[google-secops-siem-incidents] Creation of the connector (#5406)#6322
Conversation
|
260b366 to
cf72754
Compare
…nd retry strategy
…onsibility methods
…cize compute_pagination_pivot
d5533a0 to
5511a5c
Compare
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.
Proposed changes
Add new google-secops-siem-incidents external-import connector that fetches Chronicle SIEM rule alerts via the Legacy Search API, converts them to STIX2.1 (incidents, observables, relationships), and sends bundles to OpenCTI with backward-sliding-window pagination and checkpoint-based state persistence.
Catalog/Composer:




Log of the connector:

Tests:

Linter:

Manifest:

Related issues
#5406
Checklist
Further comments