mitre-attack / mitre-attack/attack-navigator

Default technique state

Open
#123 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Points: 5 seeking feedback timescale/imminent
Dominant language
TypeScript
Stars
2.5k
Forks
715
Avg merge
7h 33m
Merged PRs (30d)
4

Description

As a user of the ATT&CK navigator, I want to be able to configure the default technique state, both in the Navigator itself and in uploaded layers.

The default state would be overridden by defined values in the techniques of an uploaded layer. For example, the user could set the default state of enabled to false, thereby disabling all techniques, then upload a layer with a few explicitly enabled techniques to only enable those techniques.

This could be configured as part of the Navigator configuration, and also in the layer file itself.

  • If defined in the config file, it would set the default state of techniques for all layers (created or uploaded) to the configured defaults.
  • In the layer file, it would set the default state of techniques on just that that layer to the configured default. This would also override the defaults defined in the config file.

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 tracing the Navigator configuration and uploaded-layer loading entry points. Define how configured defaults apply to techniques, then verify that explicit technique states override layer defaults and that layer defaults override Navigator defaults. Done means both configuration locations support the described precedence consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.