Scribbles about events

Joachim Metz edited this page Jan 21, 2017 · 10 revisions

This page contains some scribbles about events. It contains information about:

  • What is an event?
  • How can an event be defined?
  • How are events defined in plaso?

What is an event?

From Wikipedia - Event (computing)

In computing, an event is an action or occurrence detected by the program that may be handled by the program. Typically events are handled synchronously with the program flow, that is, the program has one or more dedicated places where events are handled, frequently an event loop. Typical sources of events include the user (who presses a key on the keyboard, in other words, through a keystroke). Another source is a hardware device such as a timer. Any program can trigger its own custom set of events as well, e.g. to communicate the completion of a task.

How can an event be defined?

An event consists of the following types of information:

  • date and time or duration of the event (event time), which can be unknown if we know the event happened but not when;
  • an indication of what the event time represents e.g. Creation Time, Program Execution Duration, etc.
  • the source of the event e.g. the Windows Application Event Log C:\Windows\System32\config\AppEvent.evt or specific lines in the /var/log/messages
  • data specific to the event e.g. in case of process execution this could be the path of the executable file and arguments
  • contextual information about the event e.g. the hostname of the system on which the event occurred, the identifier of the user account under which the event occurred, etc.

A more analysts view on how an event can be defined is:

  • When or for how long this event happened (event time)
  • Who/what did an action for the event to happen (actor or subject)
  • What was the action that happened (action or predicate)
  • Who/what affected the action (object)
  • Where did we learn from that the event happened (event source)

Time-less events

Based on our definition an event technically should have a date or time (or duration). However there are cases where we know an action happened but have no indication of when.

TODO: add description

Different levels of events

TODO: add description

  • source-level event; e.g. a line in syslog representing an event
  • system-level event; e.g.
  • user-level event

How are events defined in plaso?

TODO: add description

Event object

TODO: add description

Event object type

TODO: add description

Event time

A plaso timestamp is a 64-bit signed integer that contains the number of micro seconds since January 1, 1970 00:00:00 UTC. A negative time means that the event happened before its reference date (or epoch).

  • An event spanning a duration is currently not supported
  • Time-less events currently overload timestamp 0

However plaso is moving to dfdatetime to represent event time with preservation of accuracy and precision.

Event formatting

TODO: add description

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.