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

CAPEC STIX Documents are all Separate Documents #47

Closed
HamptonJ opened this issue May 3, 2019 · 6 comments
Closed

CAPEC STIX Documents are all Separate Documents #47

HamptonJ opened this issue May 3, 2019 · 6 comments

Comments

@HamptonJ
Copy link

HamptonJ commented May 3, 2019

Are there plans on merging the CAPEC STIX documents in a way similar to the ATT&CK STIX?

@rpiazza
Copy link
Collaborator

rpiazza commented May 4, 2019

Hi @HamptonJ,

I'm not 100% sure what your question is. Was it - can ATT&CK and CAPEC STIX use the same custom properties?

@HamptonJ
Copy link
Author

HamptonJ commented May 6, 2019

What I meant was, you have merged all of the ATT&CK STIX objects into one document: "enterprise.json". I was wondering if there were plans to merge all of CAPEC STIX into one document as well, so there would be one ATT&CK STIX and one CAPEC STIX document.

@rpiazza
Copy link
Collaborator

rpiazza commented May 6, 2019

I see no reason why we can't do that sometime in the near future.

@HamptonJ
Copy link
Author

HamptonJ commented May 6, 2019

Awesome! That will be very helpful for me. Thanks! And thanks for your quick responses!

@jburns12
Copy link
Contributor

@HamptonJ - @rpiazza put this together in the latest CAPEC STIX release here. Let us know if you have any questions or concerns!

@HamptonJ
Copy link
Author

Thanks @rpiazza @jburns12 !! This is exactly what I was looking for!

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