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

[Flashpoint]: Enhance Flashpoint connector #3279

Closed
romain-filigran opened this issue Jan 15, 2025 · 0 comments
Closed

[Flashpoint]: Enhance Flashpoint connector #3279

romain-filigran opened this issue Jan 15, 2025 · 0 comments
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@romain-filigran
Copy link
Member

romain-filigran commented Jan 15, 2025

Global

  • Implement the standard scheduling and back-pressure mechanism. Previous "interval" configuration option stay maintained to not introduce breaking change.
  • Generate a work_id per collection to ingest

Flashpoint Alerts

  • Better Modeling of Alerts: Refine the structure used to model Flashpoint alerts in OpenCTI
  • Use a more efficient API to retrieve alerts
  • Consideration of Data Exposure Alerts

Flashpoint Indicators (MISP Feed)

  • No longer import MITRE attack pattern identifiers as labels
  • Align indicator ingestion scheduling
@romain-filigran romain-filigran added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Jan 15, 2025
@romain-filigran romain-filigran changed the title [Flashpoint]: Enhance Flashpoint Alerts Ingestion [Flashpoint]: Enhance Flashpoint connector Jan 15, 2025
@romain-filigran romain-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 16, 2025
@romain-filigran romain-filigran added this to the Bugs backlog milestone Jan 16, 2025
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 17, 2025
@SamuelHassine SamuelHassine pinned this issue Jan 17, 2025
@romain-filigran romain-filigran unpinned this issue Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants