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

[CSV Mappers] Add relationship representation for "sighted at/in" #4846

Closed
Lhorus6 opened this issue Nov 3, 2023 · 0 comments
Closed

[CSV Mappers] Add relationship representation for "sighted at/in" #4846

Lhorus6 opened this issue Nov 3, 2023 · 0 comments
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@Lhorus6
Copy link

Lhorus6 commented Nov 3, 2023

Needs

Be able to create Sightings/"sighted at/in" relationships with CSV mappers

Use case

I have a CSV file from the result of a Splunk search. This CSV is a table containing all the alerts raised by my search (one line = one alert). I would like these alerts to be imported into OpenCTI as sightings but I don't feel I can map a sighting ("sighted at/in" relationship). In a relationship representation, I don't find the "sighted at/in" type.

If the feature request is approved, would you be willing to submit a PR?

No

@Lhorus6 Lhorus6 added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Nov 3, 2023
@Jipegien Jipegien removed the needs triage use to identify issue needing triage from Filigran Product team label Nov 20, 2023
@Jipegien Jipegien added this to the Release 5.13.0 milestone Nov 20, 2023
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 2, 2024
@SamuelHassine SamuelHassine removed this from the Release 5.13.0 milestone Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop 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