-
Notifications
You must be signed in to change notification settings - Fork 5
Maturity: Actions
Ivan Kirillov edited this page Oct 9, 2015
·
3 revisions
As with Events, Actions are a little undefined in terms of scope and context. For the most part they are intended to represent abstractions of system-level API calls (e.g., CreateFileEx in Windows), as used in MAEC. However, they could also be used to represent more abstract, non-API call actions, such as the receiving of an email message.
Depending on how the scope of Actions is defined, there is a potential for them to have additional fields and properties, as well as many more values for the default action names vocabulary.
Actions are used primarily through MAEC and its corresponding implementations.