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

[Recorded Future] Connector is creating relationships in the wrong direction #3263

Closed
SamuelHassine opened this issue Jan 13, 2025 · 1 comment · Fixed by #3428
Closed

[Recorded Future] Connector is creating relationships in the wrong direction #3263

SamuelHassine opened this issue Jan 13, 2025 · 1 comment · Fixed by #3428
Assignees
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. solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@SamuelHassine
Copy link
Member

Description

Image

=> The relationship between observables and "threats" or "incidents" (threat actor, intrusion set, campaign, incident, etc.) should always be "Observable" => related-to => "Threat".

@helene-nguyen We should check if this is not in other connectors please.

@SamuelHassine SamuelHassine added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 13, 2025
@SamuelHassine SamuelHassine changed the title Recorded Future is creating relationships in the wrong direction [Recorded Future] Connector is creating relationships in the wrong direction Jan 13, 2025
@helene-nguyen
Copy link
Member

@SamuelHassine I will check it :)

@helene-nguyen helene-nguyen self-assigned this Jan 15, 2025
@helene-nguyen helene-nguyen added this to the Bugs backlog milestone Jan 15, 2025
@romain-filigran romain-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 15, 2025
@helene-nguyen helene-nguyen added the filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. label Feb 14, 2025
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 17, 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. solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
3 participants