Support Filtering/Display of Custom Context Menu Options by Technique

[ikiril01]

Right now custom context menu options via assets/config.json get applied to all techniques in a layer. It would be great if we could filter/select which techniques specific context menu options get applied to, as it would enable per-technique context menus to be built.

In the JSON, I think this could be implemented as a simple list in the context menu dictionary that acts as a filter:

{
    "label": "foo"
    "url": "https://test.com",
    "limit_techniques": ["T1099", "T1092"]
}

[rjsmitre]

In the case of multi-tactic techniques, we would need a way to specify whether that menu item applied to all instances of the technique or just some...

[workmcg]

Re: rjsmitre's point about multi-tactic techniques — the Navigator's own layer format already solves exactly this ambiguity: technique objects in a layer file take an optional tactic field, and per the layer format spec, "if the field is not present, the annotations... appear under every tactic the technique belongs to." Could apply the same pattern here — let each limit_techniques entry optionally be either a bare ID ("T1059", applies to all tactics the technique appears under) or a technique+tactic pair (e.g. {"id": "T1059", "tactic": "execution"}) when the filter needs to be tactic-specific. That would resolve the ambiguity without a breaking change to the existing bare-ID list format. Happy to take a stab at a PR for this if that approach sounds right.

[workmcg]

Opened #805 for this.

It implements the approach sketched above: each limit_techniques entry can be either a bare ATT&CK ID, which applies the option under every tactic the technique appears in, or an { "id": "T1059", "tactic": "execution" } pair scoping it to one tactic. The two forms can be mixed in a single list.

@rjsmitre — that should cover the multi-tactic case you raised. The pattern mirrors the optional tactic field on technique objects in the layer format, so it reuses a convention contributors already know rather than introducing new semantics.

Behavior is unchanged when the field is omitted or empty: the option applies to every technique, as today.