Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate Recorded Future Fileset #28029

Open
jamiehynds opened this issue Sep 21, 2021 · 7 comments
Open

Deprecate Recorded Future Fileset #28029

jamiehynds opened this issue Sep 21, 2021 · 7 comments
Labels

Comments

@jamiehynds
Copy link

jamiehynds commented Sep 21, 2021

As we work through a longer term plan to fully support Recorded Future TI, we need to mark the RF fileset, within the TI module as experimental. Our current approach is not supported by Recorded Future and want to make it clear to our mutual customers that the current integration is not supported and mileage may vary.

Please add the experimental flag to the RF fileset in our docs: https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html#recordedfuture

// @shimonmodi @P1llus @adriansr

@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@jamiehynds
Copy link
Author

@shimonmodi can you provide the text you want to display for the RF deprecation notice?

FYI @adriansr

@shimonmodi
Copy link

Something along the lines of "This threat intelligence module is configured to use the search API for RecordedFuture, which does not provide the best analyst experience. We recommend using the RecordedFuture Integration Package (link here) for the most optimal experience."

@mbarretta
Copy link

@jamiehynds is there a plan to update our integration to the RF supported method?

@jamiehynds
Copy link
Author

@mbarretta this issue should have been closed. We shipped a new Recorded Future integration based on their recommended approach to ingest their TI data. Here's the PR: elastic/integrations#2757

Are you running into difficulties with the current integration? There's some known issues around our inability to handle IoC expiry, which we're currently working on across all TI integrations.

@norrietaylor norrietaylor added the Team:Security-Service Integrations Security Service Integrations Team label Jan 31, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@botelastic
Copy link

botelastic bot commented Feb 7, 2025

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants