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

New function to remove deprecated STIX objects #15

Merged
merged 1 commit into from
Jul 12, 2020
Merged

New function to remove deprecated STIX objects #15

merged 1 commit into from
Jul 12, 2020

Conversation

marcusbakker
Copy link
Contributor

Hi Roberto,

While we were busy with adding support for sub-techniques in DeTT&CT we noticed that we needed to get rid of STIX objects that are deprecated. In our particular case, these were old techniques which are no longer used in the latest release of ATT&CK. I have therefore added a new function based on the already existing function remove_revoked. The new function remove_deprecated removes any objects which have the STIX property 'x_mitre_deprecated' set to true

I think it would be of value to add this to attackcti.

Regards,
Marcus

@marcusbakker marcusbakker changed the title Added a new function to remove deprecated STIX objects. New function to remove deprecated STIX objects. Jul 10, 2020
@marcusbakker marcusbakker changed the title New function to remove deprecated STIX objects. New function to remove deprecated STIX objects Jul 10, 2020
@Cyb3rWard0g
Copy link
Collaborator

Thank you very much @marcusbakker !! I appreciate it. I would like to hear more about how you guys are handling the sub-techniques update. I will merge this and push a quick fix to the version.

@marcusbakker
Copy link
Contributor Author

Regarding the handling of the sub-techniques. Not sure if you have any questions in particular? But, we were pleased that no real changes were required in the functionality of attackcti. If that was the case, also no big deal of course as we can provide back the changes that we did via PRs. Basically, sub-techniques are just techniques with a different number within the CTI data of ATT&CK :-). So, that helped a lot.

To help users with the migration of YAML files in DeTT&CT we made heavy use of the crosswalk.json file provided by MITRE. We created some new logic and guidance to help the user to migrate their files/mappings the most efficient. Still, it can be an annoying exercise, but it has to be done.

We dropped support for any old techniques. They can still be used in some areas, but not everywhere. We also did not re-mapped any published ATT&CK mappings (like the one for CrowdStrike, Red Canary, etc.). That's almost impossible to do because we do not have access to the raw data that tells us how it should be mapped into sub-techniques.

No idea if this answers your question :-).

@Cyb3rWard0g
Copy link
Collaborator

That's awesome @marcusbakker ! Thank you very much for taking the time to write those details. Yes that helped. I am happy to hear that there were no real changes required in the functionality of attackcti. I was working on another project and I was setting up some time to take a look at it a little bit deeper. Thank you again! I hope you enjoy the rest of your week :)

@marcusbakker
Copy link
Contributor Author

I'm happy tot help. Also enjoy the rest of your week over there too!

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

Successfully merging this pull request may close these issues.

None yet

2 participants