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 Connector Does Not Implement Import_Indicators #1263

Closed
AliceGrey opened this issue Jun 26, 2023 · 1 comment
Closed

Flashpoint Connector Does Not Implement Import_Indicators #1263

AliceGrey opened this issue Jun 26, 2023 · 1 comment
Labels
duplicate use to identify issue already existing feature use for describing a new feature to develop

Comments

@AliceGrey
Copy link

Description

The Flashpoint connector does not currently pull any indicator data but the config makes it seems like it does. You can find the full Flashpoint IOC API docs here: https://help.fp.tools/en/articles/5803017-technical-indicators-api-documentation

Environment

  1. OS (where OpenCTI server runs): Ubuntu 20.04
  2. OpenCTI version: 5.8.4
  3. OpenCTI client: frontend
  4. Other environment details: N/A

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Read through flashpoint.py connector
  2. It doesn't implement pulling indicators from the API

Expected Output

Flashpoint connector should pull all available IOC's and properly tag them.

Actual Output

Flashpoint connector only pulls APT & Malware data.

Additional information

The current workaround is to load Flashpoints api data into MISP and then pull MISP data into OpenCTI.

@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Aug 26, 2023
@SamuelHassine SamuelHassine added this to the Release 5.11.0 milestone Aug 26, 2023
@Jipegien Jipegien modified the milestones: Release 5.13.0, Short-term candidates Nov 7, 2023
@SamuelHassine SamuelHassine added filigran team use to identify PR from the Filigran team and removed filigran team use to identify PR from the Filigran team labels Apr 20, 2024
@Jipegien Jipegien removed this from the Short-term candidates milestone Apr 23, 2024
@richard-julien
Copy link
Member

Will be handled by #1988

@SamuelHassine SamuelHassine added the duplicate use to identify issue already existing label Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate use to identify issue already existing feature use for describing a new feature to develop
Projects
None yet
Development

No branches or pull requests

4 participants