tenable_io: Document breaking-changes introduced in 4.0.0.#14130
Merged
kcreddy merged 3 commits intoelastic:mainfrom Jun 4, 2025
Merged
tenable_io: Document breaking-changes introduced in 4.0.0.#14130kcreddy merged 3 commits intoelastic:mainfrom
kcreddy merged 3 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Merged
5 tasks
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
scan |
17857.14 | 12195.12 | -5662.02 (-31.71%) | 💔 |
To see the full report comment with /test benchmark fullreport
efd6
reviewed
Jun 4, 2025
| #### Support for Elastic Vulnerability Findings page. | ||
|
|
||
| Version `4.0.0` of the Tenable Vulnerability Management integration adds support for [Elastic Cloud Security workflow](https://www.elastic.co/docs/solutions/security/cloud/ingest-third-party-cloud-security-data#_ingest_third_party_security_posture_and_vulnerability_data). The enhancement enables the users of Tenable Vulnerability Management integration to ingest their enriched asset vulnerabilities from Tenable platform into Elastic and get insights directly from Elastic [Vulnerability Findings page](https://www.elastic.co/docs/solutions/security/cloud/findings-page-3). | ||
| This update adds [Elastic Latest Transform](https://www.elastic.co/docs/explore-analyze/transforms/transform-overview#latest-transform-overview) which copies the latest vulnerability findings from source indices macthing the pattern `logs-tenable_io.vulnerability-*` into new destination indices matching the pattern `security_solution-tenable_io.vulnerability_latest-*`. The Elastic Vulnerability Findings page will display vulnerablities based on the destination indices. |
Contributor
There was a problem hiding this comment.
Suggested change
| This update adds [Elastic Latest Transform](https://www.elastic.co/docs/explore-analyze/transforms/transform-overview#latest-transform-overview) which copies the latest vulnerability findings from source indices macthing the pattern `logs-tenable_io.vulnerability-*` into new destination indices matching the pattern `security_solution-tenable_io.vulnerability_latest-*`. The Elastic Vulnerability Findings page will display vulnerablities based on the destination indices. | |
| This update adds [Elastic Latest Transform](https://www.elastic.co/docs/explore-analyze/transforms/transform-overview#latest-transform-overview) which copies the latest vulnerability findings from source indices matching the pattern `logs-tenable_io.vulnerability-*` into new destination indices matching the pattern `security_solution-tenable_io.vulnerability_latest-*`. The Elastic Vulnerability Findings page will display vulnerabilities based on the destination indices. |
| - grant use of transforms, and | ||
| - grant access to source and destination indices | ||
| For more details on Transform Setup, refer to the link [here](https://www.elastic.co/docs/explore-analyze/transforms/transform-setup) | ||
| 3. Because the latest copy of vulnerabilities is now indexed in 2 places, i.e., in both source and destination indices, users must anticipate storage requirements accordingly. |
Contributor
There was a problem hiding this comment.
Suggested change
| 3. Because the latest copy of vulnerabilities is now indexed in 2 places, i.e., in both source and destination indices, users must anticipate storage requirements accordingly. | |
| 3. Because the latest copy of vulnerabilities is now indexed in two places, i.e., in both source and destination indices, users must anticipate storage requirements accordingly. |
|
💚 Build Succeeded
History
cc @kcreddy |
efd6
approved these changes
Jun 4, 2025
|
Package tenable_io - 4.0.1 containing this change is available at https://epr.elastic.co/package/tenable_io/4.0.1/ |
1 task
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
Checklist
changelog.ymlfile.Related issues
Screenshots