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

OpenCTI couldn't get a MISP data #47

Closed
xinfolab opened this issue Feb 26, 2020 · 2 comments
Closed

OpenCTI couldn't get a MISP data #47

xinfolab opened this issue Feb 26, 2020 · 2 comments
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@xinfolab
Copy link

Description

When running the MISP connector, OpenCTI couldn't get a MISP data.

Environment

  1. OS (where OpenCTI server runs): ubuntu 19.10 VirtualBox
  2. OpenCTI version : 3.0.2
  3. OpenCTI client : python 3.7.5
  4. Other environment details: pymisp==2.4.119.1

Reproducible Steps

Clone the repository

$ mkdir /path/to/your/app && cd /path/to/your/app
$ git clone https://github.com/OpenCTI-Platform/docker.git
$ cd docker

misp connector download

Docker Set configure

  • APP__ADMIN__PASSWORD
  • APP__ADMIN__TOKEN
  • OPENCTI_TOKEN
  • vm.max_map_count

MISP configure

  • opencti-url
  • opencti-token
  • misp-url
  • misp-key
  • misp-ssl_verify

Run

$ docker-compose --compatibility up
$ python3 misp.py

Expected Output

I wanted to importing MISP data inside openCTI.

Actual Output

MISP returned 0 events

$ python3 misp.py
INFO:root:Connector last run: 2020-02-26 07:02:25
INFO:root:Fetching MISP events with args: {"tags": {"OR": ["opencti:import", "type:osint"]}, "timestamp": "2020-02-26 07:02:25", "limit": 100, "page": 1}
INFO:root:MISP returned 0 events.

Additional information

image

@mbower
Copy link

mbower commented Mar 6, 2020

Im sort of seeing this same thing. Although, I get some of the MISP data to come in initially, then it just stops importing anything and I see the above.

@SamuelHassine
Copy link
Member

@mbower @xinfolab: just fixed this issue. It will be in the next release!

@SamuelHassine SamuelHassine added solved use to identify issue that has been solved (must be linked to the solving PR) bug use for describing something not working as expected labels Mar 7, 2020
@SamuelHassine SamuelHassine self-assigned this Mar 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected 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

3 participants