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

Crowdstrike connector is ingesting duplicate reports #3295

Open
nhuber0724 opened this issue Jan 16, 2025 · 0 comments
Open

Crowdstrike connector is ingesting duplicate reports #3295

nhuber0724 opened this issue Jan 16, 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

@nhuber0724
Copy link

nhuber0724 commented Jan 16, 2025

Description

The Crowdstrike Connector is creating duplicate reports as it seems anytime a report is modified in Crowdstrike, even if there is no substantial modification or for an unknown reason, the connector will ingest that report into the platform; however, that report will be identical to a report already ingested from Crowdstrike.

Environment

OpenCTI v.6.4.7

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Run the Crowdstrike Connector
  2. Search for duplicate reports

Expected Output

We should not see identical reports from the same source (Crowdstrike)

Actual Output

Crowdstrike is making unknown modifications to reports within and the connector is pulling the report in based on the modification date causing duplicate reports. The reports are exactly the same. Sometimes one report will have labels and another identical report will contain no labels.

Additional information

Screenshots (optional)

@nhuber0724 nhuber0724 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 16, 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