mitre-attack / mitre-attack/attack-workbench-rest-api

Support for creating custom domains?

Open
#236 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
57
Forks
18
Avg merge
6m
Merged PRs (30d)
2

Description

Hi,
I wasn't able to find a way to add new domains (other than the pre-populated entries: enterprise-attack, mobile-attack, and ics-attack)?
It would be very useful to support defining custom domains for cases where one wants to threat model a specific scenario which is quite different from the supported ones and to avoid polluting the existing domain(s) with unrelated data.

Looks like the domains are currently hardcoded in app/config/config.js and app/config/allowed-values.json? Would adding the relevant entries to those files be enough to support additional domains?

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 reading app/config/config.js and app/config/allowed-values.json, where the existing enterprise-attack, mobile-attack, and ics-attack domains are reportedly hardcoded. Trace how those values are used when storing and querying ATT&CK objects, and determine whether configuration changes alone can support user-defined domains. Done means custom domains can be defined for separate threat-modeling scenarios without mixing their data with existing domains.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.