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

Add Kill Chain Phase selection when adding observable #105

Closed
cdiraimondi opened this issue Jul 2, 2019 · 1 comment
Closed

Add Kill Chain Phase selection when adding observable #105

cdiraimondi opened this issue Jul 2, 2019 · 1 comment
Assignees
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

Comments

@cdiraimondi
Copy link

Problem to Solve

There is currently no way to specify the Kill Chain phases, more specifically Lockheed Martin Kill Chain phases to specific observables when adding them to a report.

Current Workaround

None

Proposed Solution

When adding an Observable, provide a dropdown list that contains all the Kill Chain values added from the settings page.

Additional Information

I was able to add the custom Lockheed Martin Cyber Kill Chain phases to the Kill Chain settings page but was unable to add them to the observable.

@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Jul 8, 2019
@SamuelHassine SamuelHassine added this to the Release 1.1.0 milestone Jul 8, 2019
@SamuelHassine
Copy link
Member

Users must be able to add a kill chain phase not directly on the observable but on the relation between the observables and the associated threat. So kill chain phases will be implmented in the "relation form" form relations of type indicates.

@SamuelHassine SamuelHassine removed this from the Release 1.1.1 milestone Aug 3, 2019
@SamuelHassine SamuelHassine added this to the Release 2.0.0 milestone Oct 14, 2019
@SamuelHassine SamuelHassine self-assigned this Oct 14, 2019
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Oct 22, 2019
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

2 participants