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

[MISP & ImportFileMISP] Obervable missing from import #3255

Open
Lhorus6 opened this issue Jan 10, 2025 · 0 comments
Open

[MISP & ImportFileMISP] Obervable missing from import #3255

Lhorus6 opened this issue Jan 10, 2025 · 0 comments
Labels
bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. needs triage use to identify issue needing triage from Filigran Product team
Milestone

Comments

@Lhorus6
Copy link
Contributor

Lhorus6 commented Jan 10, 2025

Description

When importing the MISP attributes “filename|sha256”, OpenCTI imports the filename as a File Observable and an Indicator, but the sha256 is missing.

Looking at the code, the connector seems to support it, so we have a bug there

Image

Environment

OCTI 6.4.6

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Enable a MISP connector
  2. Create a "filename|sha256" attribute in MISP
  3. Wait for OpenCTI ingesting it
    -> No sha256

Other Option

  1. Enbale ImportFileMISP
  2. Ingest the following file (it's an export of a MISP event containing a "filename|sha256" attribute)

misp.event.350.json

@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 10, 2025
@nino-filigran nino-filigran added the filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. label Jan 23, 2025
@nino-filigran nino-filigran added this to the Bugs backlog milestone Jan 23, 2025
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 filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. needs triage use to identify issue needing triage from Filigran Product team
Projects
None yet
Development

No branches or pull requests

2 participants