[tenable_io] Include last_fixed date in the fingerprint to avoid duplicated entries - #10356
Merged
chemamartinez merged 2 commits intoJul 4, 2024
Merged
Conversation
chemamartinez
added
Integration:tenable_io
chemamartinez
marked this pull request as ready for review
July 3, 2024 16:54
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
|
efd6
approved these changes
Jul 3, 2024
|
Package tenable_io - 3.1.1 containing this change is available at https://epr.elastic.co/search?package=tenable_io |
orestisfl
pushed a commit
to orestisfl/integrations
that referenced
this pull request
May 15, 2026
…icated entries (elastic#10356) Add the last_fixed field to the fingerprint calculation
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
3 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.
Proposed commit message
From some customer's feedback, current fields for generating the fingerprint could not be enough in some cases to identify unique entries. When a vulnerability gets fixed, a new record can be triggered with the same
last_foundbut including alast_fixeddate.These kind of events may be dropped since there exists any other entry with the same fingerprint as
_id.This pull request adds the
last_fixedfield to the fingerprint calculation.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots