mitre-attack / mitre-attack/attack-navigator

Feature Request: add score visualisation in layer

Open
#605 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
2.5k
Forks
715
Avg merge
7h 33m
Merged PRs (30d)
4

Description

First of all I want to thank you for this magnificent tool, it is really helpful!

Some time ago I faced a usage case when I needed to combine several layers of one threat actor distributed in time and visualise similarities and differences. So I assigned a score to each of the layers, combined them and got the result. But the only option I had to distinguish different combinations of similarities in svg or excel was colours. And it seemed like "This combination is green, this one is little bit greenish, this one is more closely to yellow etc.". I think this is not a convenient way. When we work with json and machine readable data all is good, but in this case human readable data suffers. I propose an option to add assigned score of each technique to visual layer (svg, excel), maybe under a technique name, so it would be more easy to make out different combinations of similarities. Of course you can adjust colours to your needs but I think score solution is more user friendly.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the layer visualisation and SVG/Excel export entry points described in the issue. Clarify how assigned technique scores should appear in each output, then define completion as human-readable scores being visible alongside technique names without relying only on colours.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
data-visualization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.