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.

Sign up for GitHub

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

Jump to bottom

Add new observable types #370

Closed
VVX7 opened this issue Dec 8, 2019 · 0 comments
Closed

Add new observable types #370

VVX7 opened this issue Dec 8, 2019 · 0 comments
Assignees
@SamuelHassine
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)
Milestone
Release 3.3.0

Comments

@VVX7
Copy link

VVX7 commented Dec 8, 2019

Problem to Solve

Only STIX2 Cyber Observable types are currently permitted. This limits reporting of observables when discussing disinformation and influence operations.

Current Workaround

None

Proposed Solution

Allow users to upload custom object types, or use a richer observable schema such as MISP's standard attribute types.

Specifically add:
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Dec 9, 2019
@SamuelHassine SamuelHassine added this to the Release 3.0.0 milestone Feb 5, 2020
@SamuelHassine SamuelHassine self-assigned this Feb 5, 2020
@SamuelHassine SamuelHassine changed the title Add custom observable types Add new observable types Apr 18, 2020
@SamuelHassine SamuelHassine mentioned this issue May 7, 2020
Closed
SamuelHassine pushed a commit that referenced this issue May 26, 2020
[api/frontend] Add new custom observable types (#370, #687)
0b1ceac
SamuelHassine pushed a commit that referenced this issue May 26, 2020
[api/frontend] Add new custom observable types (#370, #687)
bd701b7
SamuelHassine pushed a commit that referenced this issue May 26, 2020
[api/frontend] Add new observable types (#370, #687)
6a87f67
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

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
Milestone
Release 3.3.0
Development

No branches or pull requests
2 participants
@SamuelHassine @VVX7