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

DragonFly like a intrustion set #4

Closed
sebdraven opened this issue Oct 30, 2017 · 2 comments
Closed

DragonFly like a intrustion set #4

sebdraven opened this issue Oct 30, 2017 · 2 comments

Comments

@sebdraven
Copy link

I think there is a mistake here https://github.com/mitre/cti/blob/272ce2cd52a7ca4820775e7278a7af1395b44d94/ATTACK/intrusion-set/intrusion-set--1c63d4ec-0a75-4daa-b1df-0d11af3d3cc1.json about DragonFly is a threat actor and no intrusion set if i read the documentation here https://stixproject.github.io/stix2.0/stixdocs/stix-v2.0-wd02.pdf.

@Bojak4616
Copy link

Hey @sebdraven, I just removed those documents since they shouldn't have been hosted there. You can get the latest documents on our new site here: https://oasis-open.github.io/cti-documentation/resources.html

@johnwunder
Copy link
Contributor

Good question, @sebdraven. You can see the definition of groups in ATT&CK here: https://attack.mitre.org/wiki/Groups. Based on the definition "related intrusion activity that are tracked by a common name in the security community" we felt that intrusion set was a better mapping than threat actor. That applies to Dragonfly but also the other groups referenced in ATT&CK.

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

3 participants