mitre-attack / mitre-attack/mitreattack-python
[Request] Update changelog_helper to handle updated detection schema
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 743
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem?
This is not a problem yet. But the October 2025 ATT&CK release plans to update the schema around data sources, data components, etc. which is detailed here: https://github.com/mitre-attack/attack-data-model/issues/14. When that goes into effect, https://github.com/mitre-attack/mitreattack-python/blob/master/mitreattack/diffStix/changelog_helper.py will need to be updated to handle how changes are made between ATT&CK releases.
Describe the solution you'd like
The output of the changelog_helper.py script should appropriately show the current data source and data component objects as being deprecated. It should also know about and show the new detection strategy, log source, and analytic objects as being added. This issue here may become out of date if the schema changes further, so the latest information at https://github.com/mitre-attack/attack-data-model/issues/14 should always be referenced.
Describe alternatives you've considered
Since the ATT&CK team uses ATT&CK Workbench to create ATT&CK releases, one day this functionality should be baked into ATT&CK Workbench, per this GitHub issue: https://github.com/center-for-threat-informed-defense/attack-workbench-frontend/issues/573
Additional context
None at this time
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
Start with mitreattack/diffStix/changelog_helper.py and read the latest schema details in attack-data-model issue 14. Trace how the script identifies changed ATT&CK objects, then update its handling so current data sources and data components appear deprecated and detection strategies, log sources, and analytics appear added. Done means the changelog output reflects those schema changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100