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

Include "potential indicator" in maecVocabs:CollectionEntityTypeEnum #113

Open
dzbeck opened this issue May 25, 2015 · 4 comments
Open

Include "potential indicator" in maecVocabs:CollectionEntityTypeEnum #113

dzbeck opened this issue May 25, 2015 · 4 comments

Comments

@dzbeck
Copy link
Contributor

dzbeck commented May 25, 2015

See proposal to deprecate MAEC Candidate Indicators in favor of STIX Indicators (which references the proposal to make MAEC Collections top-level Entities). The proposal involves using a MAEC Collection with the entity_type field set to "potential indicator."

@ikiril01
Copy link
Member

@dzbeck should this instead be captured in the Name field in the new CollectionType? It seems a little odd to have "potential indicator", which is more of a label or description, in the same enumeration that captures possible MAEC/CybOX entity types such as "actions", "objects", and the like.

@dzbeck
Copy link
Contributor Author

dzbeck commented Aug 4, 2015

@ikiril01 it doesn't seem a good idea to embed such info in a Name... although I see that it's odd to have an entity type (potential indicator) that is comprised of maec entities (actions, behaviors). How about defining both the "maec_entity_type" field (which includes "various") and an optional "collection_type" field to include "potential_indicator" (and any other higher level things that a collection of maec entities could be).

@ikiril01
Copy link
Member

ikiril01 commented Aug 6, 2015

@dzbeck I thought about this a bit more and I like your idea of having a separate field for having a standard way of specifying the contents of a Collection (including potential indicators), though I called it "type" for simplicity. I also thought it may be used for capture related "sets" of MAEC entities, such as file system entities, network entities, etc. Anyhow, what do you think of the corresponding changes in https://github.com/MAECProject/schemas/wiki/Proposal:-Make-Collections-Top-Level-Entities?

@dzbeck
Copy link
Contributor Author

dzbeck commented Aug 6, 2015

@ikiril01 I think the changes look great. I like the values in CollectionTypeEnum.

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