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

Visualize TTPs in ATT&CK Navigator #76

Closed
YamatoSecurity opened this issue Dec 15, 2023 · 2 comments · Fixed by #77
Closed

Visualize TTPs in ATT&CK Navigator #76

YamatoSecurity opened this issue Dec 15, 2023 · 2 comments · Fixed by #77
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@YamatoSecurity
Copy link
Collaborator

When Hayabusa saves results with JSONL and a profile with %MitreTags%, I want to extract those technique IDs create a JSON file to import into ATT&CK Navigator.
Something similar to this: https://github.com/olafhartong/sysmon-modular/blob/master/attack_matrix/Sysmon-modular.json
and this: https://github.com/olafhartong/sysmon-modular/tree/master/attack_matrix
Navigator: https://mitre-attack.github.io/attack-navigator/

However, right now Hayabusa outputs MITRE techniques in a single string separated by the broken pipe but would be better to output as an array of strings. Issue here: Yamato-Security/hayabusa#1230
So we may want to update hayabusa first before implementing this.

The legacy sigmatools has a command named sigma2attack that creates a navigator coverage map from sigma rules that can be used as a reference: https://pypi.org/project/sigmatools/

@fukusuket Are you interested in this?

@YamatoSecurity YamatoSecurity added the enhancement New feature or request label Dec 15, 2023
@fukusuket
Copy link
Collaborator

@YamatoSecurity Yes, I would love to implement it💪 :) Thank you for mentioning!

@hitenkoku
Copy link
Collaborator

duplicated #1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants