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

Auto-generate ATT&CK coverage matrices #95

Open
christophetd opened this issue Feb 7, 2022 · 8 comments · May be fixed by #613
Open

Auto-generate ATT&CK coverage matrices #95

christophetd opened this issue Feb 7, 2022 · 8 comments · May be fixed by #613
Assignees
Labels
good first issue Good for newcomers kind/documentation Improvements or additions to documentation

Comments

@christophetd
Copy link
Contributor

Idea: automatically generate images showing the ATT&CK Tactics (not techniques) coverage

Columns: ATT&CK Tactics
Rows: Stratus Red Team attack techniques

@christophetd christophetd added the kind/documentation Improvements or additions to documentation label Feb 7, 2022
@christophetd christophetd added the good first issue Good for newcomers label May 24, 2022
@tmendonca28
Copy link
Contributor

Hi @christophetd. I would like to contribute to this issue. Could you please provide a bit more context/detail on the above?

@christophetd
Copy link
Contributor Author

Thanks for reaching out! The idea is to provide a graphical representation of Stratus Red Team attack techniques.

Something along the lines of:

  • One graphical representation per platform (AWS, Azure, GCP, K8s)
  • One column per MITRE ATT&CK Tactic (Initial access, persistence...)
  • One cell for each Stratus Red Team attack technique

Available data sources:

The output might be a Markdown table or PNG image to include in the docs. Any thoughts?

@tmendonca28
Copy link
Contributor

Thank you very much for the explanation @christophetd. I've gone through the PR you sent over as well.

Here is my thought process:

  • I believe the following function returns a map of the data found in the index.yaml (where the techniques and metadata are found).
  • Interact with the index at this point and create a generate-coverage-matrices.go in the tools dir.
  • After doing so, I will output a markdown table (demarcating each of the platforms) in the docs folder. I am unsure at the moment how the process of generating a PNG from potentially a map will look like, but will see if it's possible.

Does this sound like a viable approach?

@christophetd
Copy link
Contributor Author

Makes a lot of sense! Definitely, starting with a Markdown output makes sense. At some point we can try to output a stylized HTML output if we need something fancier.

Looking forward to your contribution!

@christophetd
Copy link
Contributor Author

@tmendonca28 Do you still have interest in contributing?

@tmendonca28
Copy link
Contributor

Definitely! Sorry for dropping the ball on my end, was a bit of a busy period.

@christophetd
Copy link
Contributor Author

No worries! I'll leave the issue open, feel free to pick it up whenever you feel like it :)

@tmendonca28
Copy link
Contributor

Hey @christophetd , Happy New Year!
I worked on the pull request for this (finally) and decided to go for the stylised HTML output just so it has a similar look & feel to the SRT website.
LMKWYT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers kind/documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants