Set vulnerability ECS field based on Qualys data #11100
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
…ection.vulnerability.qds_factors`
…tion.vulnerability.qds_factor`
| The build is failing but it's passing on my laptop. Based on the logs, I'm not sure it's linked to my work. Do you have an idea on the root cause? |
andrewkroh added the Team:Security-Service Integrations 
| Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
🚀 Benchmarks reportPackage |
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
asset_host_detection | 1277.14 | 719.42 | -557.72 (-43.67%) | 💔 |
knowledge_base | 1886.79 | 1483.68 | -403.11 (-21.36%) | 💔 |
user_activity | 9090.91 | 7042.25 | -2048.66 (-22.54%) | 💔 |
To see the full report comment with /test benchmark fullreport
efd6 reviewed Sep 11, 2024
packages/qualys_vmdr/data_stream/asset_host_detection/elasticsearch/ingest_pipeline/default.yml Outdated Show resolved Hide resolved
packages/qualys_vmdr/data_stream/asset_host_detection/elasticsearch/ingest_pipeline/default.yml Outdated Show resolved Hide resolved
packages/qualys_vmdr/data_stream/asset_host_detection/elasticsearch/ingest_pipeline/default.yml Outdated Show resolved Hide resolved
packages/qualys_vmdr/data_stream/asset_host_detection/elasticsearch/ingest_pipeline/default.yml Outdated Show resolved Hide resolved
|
💚 Build Succeeded
History
|
| I've implemented @efd6's suggestion. I believe it's ready to be merged. |
efd6 approved these changes Sep 15, 2024
| Package qualys_vmdr - 5.1.0 containing this change is available at https://epr.elastic.co/search?package=qualys_vmdr |
harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 4, 2025
harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 5, 2025
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.
…ection.vulnerability.qds_factors`
Proposed commit message
In this version
5.1.0, the following changes have been made:vulnerability.score.basefield based on the item CVSS item under fieldqualys_vmdr.asset_host_detection.vulnerability.qds_factorsvulnerability.classificationfield to CVSSvulnerability.severityfield based onvulnerability.score.basevulnerability.scanner.vendorfield to Qualysvulnerability.score.versionfield based on the item CVSS_vector item under fieldqualys_vmdr.asset_host_detection.vulnerability.qds_factorsChecklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots