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

[Sentinel] Observing 2 different IDs for each indicator coming from OpenCTI #3399

Open
EinatAR opened this issue Feb 7, 2025 · 0 comments
Open
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

@EinatAR
Copy link

EinatAR commented Feb 7, 2025

Description

For each indicator pushed from OpenCTI to Sentinel, we see 2 different ID's

Environment

  1. OpenCTI version: 6.5.0

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a Live Stream to push indicators from OpenCTI to Sentinel

Expected Output

One ID for each indicator pushed from OpenCTI to Sentinel

Actual Output

Two IDs for each indicator pushed from OpenCTI to Sentinel

Additional information

In Notion investigation page and you can reach out to me to see details.

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