mitre-attack / mitre-attack/attack-navigator

Incomplete data while saving layer to JSON

Open
#662 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Dear All,

I am having an issue with the attack-navigator, exporting (saving) layer functionality. I create myself a new layer from scratch -> Enterprise ATTACK

image

I will enable the Show IDs in Layer controls (this probably has no significance to the problem).

And then I download a layer in JSON:

image

If I count the techniques displayed in the browser (navigator) I get - 235 techniques.

In the downloaded JSON file, I can only see 119 techniques. For example, I am not finding: T1046 Network Service Discovery.

I am attaching the download JSON file: layer1.json

I would expect that the techniques in the downloaded JSON match with the techniques visible on the screen. I would like to use the JSON to annotate the techniques, and then upload to attack navigator.

If I export the data to Excel, I see a complete list of techniques - including T1046

image

Thanks a lot,
Lukas

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

No source file, test, or entry point is named. Reproduce the issue by creating an Enterprise ATT&CK layer, exporting JSON and Excel, and comparing their technique lists; done means the JSON contains the same visible techniques as the Excel export and can be uploaded again.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.