[tenable_sc] Add drop to pipeline if event is empty - #5380
Conversation
Add ignore_missing to json.seeAlso field
|
@P1llus Test :) |
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
|
/test |
|
@LaZyDK any idea why we would want to ignore this? If its missing then there is no data. |
|
@P1llus I see that you are right! So we should actually drop the events instead. |
|
Hey @LaZyDK @P1llus - These are the extra external references for the Vulnerability. I don't see a point in dropping the entire event as the field is expected to be empty for many vulnerabilities. With that being said, this is a new behavior for the API though previously the response would have an empty string in cases where there were no external references for the vulnerability. By the way, thanks for the PR @LaZyDK, Really appreciate it. :) |
|
After testing with the ignore_missing set we get a new error, which should also be fixed if not everything should be dropped. |
|
I don't find any data in the events that are not having the Data is all neat after implementing a Drop action as a failure event handler for that particular split. |
And remove Drop Failure Processor
|
I removed the failure processor and included a conditional drop processor instead, to be inline with other integrations like the one for MISP. Also included the empty original event in the test document. |
|
/test |
|
It needs to generate pipeline tests, adding it now |
|
/test |
🌐 Coverage report
|
|
Package tenable_sc - 1.7.1 containing this change is available at https://epr.elastic.co/search?package=tenable_sc |
* Add ignore_missing Add ignore_missing to json.seeAlso field * Update changelog.yml * Update manifest.yml * Drop event if no results * Update changelog.yml * Add Drop processor with conditions And remove Drop Failure Processor * Update changelog.yml * Add test for empty event * adding pipeline test generation --------- Co-authored-by: Marius Iversen <marius.iversen@elastic.co>
* Add ignore_missing Add ignore_missing to json.seeAlso field * Update changelog.yml * Update manifest.yml * Drop event if no results * Update changelog.yml * Add Drop processor with conditions And remove Drop Failure Processor * Update changelog.yml * Add test for empty event * adding pipeline test generation --------- Co-authored-by: Marius Iversen <marius.iversen@elastic.co>
* Add ignore_missing Add ignore_missing to json.seeAlso field * Update changelog.yml * Update manifest.yml * Drop event if no results * Update changelog.yml * Add Drop processor with conditions And remove Drop Failure Processor * Update changelog.yml * Add test for empty event * adding pipeline test generation --------- Co-authored-by: Marius Iversen <marius.iversen@elastic.co>
Drop event in Vulnerability pipeline if there is no returned results.
What does this PR do?
Drops empty events.
Checklist
changelog.ymlfile.