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

Killchain view for Attack Patterns #245

Closed
SamuelHassine opened this issue Sep 26, 2019 · 0 comments
Closed

Killchain view for Attack Patterns #245

SamuelHassine opened this issue Sep 26, 2019 · 0 comments
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

@SamuelHassine
Copy link
Member

SamuelHassine commented Sep 26, 2019

Problem to Solve

The current view of Attack Patterns in the "threats" (Threat Actors, Intrusion Sets, etc.) is not useful.

Current Workaround

None.

Proposed Solution

Implement a grouping by kill chain phase.

Additional Information

None.

@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Sep 26, 2019
@SamuelHassine SamuelHassine self-assigned this Sep 26, 2019
@SamuelHassine SamuelHassine added this to the Release 2.1.0 milestone Oct 30, 2019
@SamuelHassine SamuelHassine changed the title Knowledge overview (killchain and diamond) Killchain view for Attack Patterns Dec 3, 2019
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Dec 3, 2019
SamuelHassine pushed a commit that referenced this issue Dec 3, 2019
…#245)

* [api/frontend] Prepare knowledge overview and vizualization

* [api/client] Implement a killChain view in the attackPatterns (#245)
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

1 participant