-
Notifications
You must be signed in to change notification settings - Fork 799
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
Observables export #362
Comments
Linked to #391 |
Observables export will be implemented in the Release 2.1.4, but basic indicators exports has been implemented in the Release 2.1.3. |
Merci, Samuel |
@Fred-certeu, it will be implemented in 2.1.3 for Indicators (with the filters) and in 2.1.4 for Observables. |
@SamuelHassine Is the export of observables foreseen in 3.1.0? At first we could export them like the other menus without necessarily having a filter. |
Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.
Problem to Solve
It is currently unclear how a user can export observables
Current Workaround
{ Please describe how you currently solve or work around this problem, given OpenCTI's limitation. }
Proposed Solution
It should be possible to export sets of observables:
Export format : to be discussed (STIX JSON, CSV, etc)
It should be possible to select fields to be included in the export files:
It should be possible to combine (and/or) different filters to generate the export sets:
-## Additional Information
{ Any additional information, including logs or screenshots if you have any. }
The text was updated successfully, but these errors were encountered: