mitre-attack / mitre-attack/attack-workbench-rest-api
There should be a record of objects that have been included in a published STIX Bundle or Collection Bundle
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 57
- Forks
- 18
- Avg merge
- 6m
- Merged PRs (30d)
- 2
Description
Objects that have been published should not be deleted from the Workbench data store. This requires a record of which objects have been published.
- "Published" is generally intended to mean sharing an object outside the organization.
- Exporting a STIX Bundle or Collection Bundle may occur in contexts other than publishing the bundle, therefore there must be some way to distinguish between an export intended for publishing and an export intended for other purposes.
- TBD: When an object is published, does this apply to all versions of the object or just the published version
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
No files or tests are identified. Start by tracing the publish and export flows for STIX Bundle and Collection Bundle operations, then clarify whether publishing applies to every object version or only the published version. Done means the service distinguishes publishing exports from other exports and preserves published objects from deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100