mitre-attack / mitre-attack/attack-workbench-frontend

[REQUEST] Change how Contributors are tracked

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

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
438
Forks
79
Avg merge
1d 21h
Merged PRs (30d)
3

Description

Is your feature request related to a problem? Please describe.

Contributors are tracked today using the x_mitre_contributors field (list of strings) on specific object types. It might be nice to have them tracked by a dedicated STIX object, like the Identity

Describe the solution you'd like
If the STIX Identity object were used to track contributors, then the current practice of each ATT&CK STIX object using the x_mitre_contributors field as a list of strings could still be used, but the strings would be the STIX ids of Identity objects of contributors. This would ultimately make it easier to interact with Contributor objects in the Mongo DB.

Describe alternatives you've considered

I have only really considered the approach mentioned above so far, but open to other suggestions.

Additional context

The ATT&CK website has the poor practice of manually adding some contributors after the fact since they are not directly connected to specific objects, while still contributing to ATT&CK. This feature request would help make this scenario be able to be handled in STIX directly instead of a random python script generating a webpage.

https://github.com/mitre-attack/attack-website/blob/master/modules/util/stixhelpers.py#L428-L429

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 with the x_mitre_contributors fields described in the issue and the linked modules/util/stixhelpers.py lines 428-429. Review how contributor data is represented in STIX and stored in MongoDB, then identify all affected ATT&CK object types and website handling. Done requires an agreed design and a complete, consistent contributor representation.

Written by the indexing model from the issue text.

Assessment

Tech stack
mongodb, python
Domain
backend-api-design, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.