Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to enhance the JSON "name" formatting #44

Closed
borgendorf opened this issue Apr 10, 2019 · 1 comment
Closed

Request to enhance the JSON "name" formatting #44

borgendorf opened this issue Apr 10, 2019 · 1 comment

Comments

@borgendorf
Copy link

Hi there, our tool is ingesting and storing ATT&CK enterprise-attack.json along with the Unit42 Adversary Playbook campaign STIX reports. You have previously synchronized the "id" field of Attack Patterns (so helpful!) but what is happening now is that Unit42 names their Attack Patterns like "name": "T1060: Registry Run Keys / Startup Folder" where in ATT&CK that would be "name": "Registry Run Keys / Startup Folder". Since we are use a linked-node graph to link everything together, I end up with two "name" fields which makes it difficult in the UI to display the name.

In my user testing, people almost always prefer the version that has both the number and the name in it, as we quickly get used to the numbers and it helps when sorting lists, too. I'm requesting that the name field be modified to use the "technique-number colon space technique name" format that Unit42 uses in ATT&CK.

Thank you!

@jburns12
Copy link
Contributor

Hi @borgendorf - thanks for the suggestions and your thoughts!

Currently our infrastructure (website, back-end content web app, etc.) is dependent on the current format of the name attribute, and the STIX is being widely used, so a change like the one presented would affect how others are currently using the STIX as well. Since there are so many dependencies on the current format, we aren't able to change the name attribute at this point.

However, the ATT&CK ID is available in the STIX as the source_name within the first external_reference of each object that has an ATT&CK ID. Hopefully that can help in some way as you continue to develop your linked-node graph.

Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants