-
Notifications
You must be signed in to change notification settings - Fork 5
Maturity: API Object
Ivan Kirillov edited this page Oct 20, 2015
·
5 revisions
There are two main issues relating to the semantics of the API Object:
- An API is more commonly thought of as a set of functions, protocols, etc. However, the API Object as it currently stands is really characterizing a single function and also its particular location in a binary. Therefore, we need to clarify if the intent is to really characterize an entire API or just a single function.
- Compared to many of the other Objects in CybOX, an API/API call is much more abstract, and is really more of a "meta" object. This is because it is unclear whether an API/API Object will ever be used by itself; instead, the primary use seems to be in conjunction with another object, such as the Windows Executable File Object, for stating that a particular API call was found at some location inside the code that makes up the executable file.
Depending on the intended scope of the API Object, there is the potential for it having additional fields.
There is no documented use of the API Object.