ti_rapid7_threat_command: Add IOC expiration - #9925
Merged
Merged
Conversation
🚀 Benchmarks reportTo see the full report comment with |
This ensures that something is broken to the users. A required value must be set to proceed further
The transform filters out any doc with error message, so error shouldn't be written. It would be nice to capture this in some comments field though
kcreddy
marked this pull request as ready for review
June 20, 2024 13:17
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
efd6
reviewed
Jun 21, 2024
kcreddy
commented
Jun 21, 2024
Comment on lines
+26
to
+33
| - name: ioc_expiration_duration | ||
| type: text | ||
| title: IOC Expiration Duration | ||
| multi: false | ||
| required: true | ||
| show_user: true | ||
| description: >- | ||
| Enforces all active IOCs to expire after this duration since their last seen time indicated in the feed. Use [Elasticsearch time units](https://www.elastic.co/guide/en/elasticsearch/reference/current/api-conventions.html#time-units) in days, hours, or minutes (e.g `10d`). If invalid units are provided, default value `90d` i.e., 90 days is used. Check `README` for more details how IOC expiration works and removal of custom transforms and views used in older versions. |
Contributor
Author
There was a problem hiding this comment.
Intentionally didn't add any default, so that user checks on IOC expiration and removes existing transforms, and rules. If we use default, the users may not notice the major changes during the upgrade.
efd6
approved these changes
Jun 21, 2024
Contributor
Author
|
To be merged after elastic/detection-rules#3800 is out next week |
💚 Build Succeeded
History
cc @kcreddy |
|
|
Package ti_rapid7_threat_command - 2.0.0 containing this change is available at https://epr.elastic.co/search?package=ti_rapid7_threat_command |
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
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
See title
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
elastic-package stack down && elastic-package build && elastic-package stack up -d -v && eval "$(elastic-package stack shellinit)" && elastic-package test pipeline --generate -velastic-package stack down && elastic-package build && elastic-package stack up -d -v && eval "$(elastic-package stack shellinit)" && elastic-package test system --generate -vRelated issues
Screenshots
Updated dashboards (querying only on the newly created destination indices):
1. Alerts Overview

2. Vulnerability Overview

3. IOC Overview
