mitre-attack / mitre-attack/attack-workbench-rest-api
Improve Analytic editing Workflow
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 57
- Forks
- 18
- Avg merge
- 6m
- Merged PRs (30d)
- 2
Description
When saving an Analytic object in Workbench today, it just updates that one object. However, it should check the x_mitre_domains field in all Data Component objects that are connected to the Log Sources in the Analytic object to see if the domains match. If they don't it should prompt the user that saving the Analytic will update the Data Components as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing the Analytic save flow and how connected Log Sources and Data Components are loaded, then determine where domain mismatches and user confirmation belong. Done means saving detects mismatches, prompts before updating related Data Components, and leaves them unchanged if the update is declined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100