ti_misp: update the use of fingerprint processors #11824
Merged
Conversation
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
chemamartinez
added
Integration:ti_misp
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
|
kcreddy
approved these changes
Nov 22, 2024
|
Package ti_misp - 1.35.8 containing this change is available at https://epr.elastic.co/package/ti_misp/1.35.8/ |
qcorporation
pushed a commit
that referenced
this pull request
Feb 3, 2025
Adding a fingerprint processor for the threat_attributes data stream to avoid ingesting the same indicators every time a request to the API is made. Updated the fingerprint for the threat data stream, by including created/updated timestamps, so subsequent updates of the indicators are also ingested.
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
Adding a fingerprint processor for the threat_attributes data stream to avoid ingesting the same indicators every time a request to the API is made. Updated the fingerprint for the threat data stream, by including created/updated timestamps, so subsequent updates of the indicators are also ingested.
qcorporation
pushed a commit
that referenced
this pull request
Feb 4, 2025
Adding a fingerprint processor for the threat_attributes data stream to avoid ingesting the same indicators every time a request to the API is made. Updated the fingerprint for the threat data stream, by including created/updated timestamps, so subsequent updates of the indicators are also ingested.
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
Adding a fingerprint processor for the threat_attributes data stream to avoid ingesting the same indicators every time a request to the API is made. Updated the fingerprint for the threat data stream, by including created/updated timestamps, so subsequent updates of the indicators are also ingested.
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 commit message
Adding a fingerprint processor for the
threat_attributesdata stream to avoid ingesting the same indicators every time a request to the API is made.Updated the fingerprint for the
threatdata stream, by including created/updated timestamps, so subsequent updates of the indicators are also ingested.Checklist
changelog.ymlfile.