Item types

Item types define what an evidence item or an asset is and which details are recorded about it. Configure them at Settings → Assets and evidence.

What an item type defines

An item type carries these things:

  • A name, shown wherever the item appears.
  • A default category, Evidence or Asset. A new item of this type starts in this category, and the person adding it can choose the other one. See Evidence and assets.
  • An icon, which identifies the type in item lists and on the item itself.
  • Its attribute fields, the type-specific details an investigator fills in when adding an item of this type. A field has a label, a database key, a data type, and a required flag. See Playbooks → Custom Fields for the available data types, which are the same here.
  • Its default runbooks, described below.

The list under Settings → Assets and evidence shows each type's default category and how many response actions apply to it.

Default item types

DFIRe ships with item types covering common physical devices, digital artifacts, and account identities. Each starts as an evidence type. The full list is in Evidence → Item types. Administrators can edit any of them, or add their own.

Three examples of how the shipped fields are shaped:

Hard Drive Internal

  • Serial Number (required)
  • Manufacturer
  • Capacity
  • Interface (SATA, SAS, USB)
  • Acquisition Hash (MD5)

Mobile Phone

  • IMEI Number (required)
  • Make, Model, Type
  • Unlock Passcode
  • SIM Card Present?
  • Secured in Faraday Bag?

Disk Image

  • Format (E01, RAW, VHD)
  • Segment Size
  • Acquisition Hash
  • Source Drive Serial
  • Verification Status

Creating an item type

  1. Go to Settings → Assets and evidence

    Choose New item type. The item type opens on its own page. To start from an existing type, use the clone button beside it in the list.

  2. Name it and choose its category

    Give it a name, choose the Default category, and pick an icon with Change icon. Choose Asset for things the organization owns and acts on, such as endpoints, servers or user accounts.

  3. Define its attribute fields

    Add the details investigators should record for this type, such as a serial number for hardware or a hostname for an endpoint. Mark a field required when an item of this type is not meaningful without it. A response action's webhook can send a field's value with {{item.attributes.key}}. See Connecting a webhook.

  4. Attach default runbooks (optional)

    Tick one or more runbooks. Whenever an investigator creates a new item of this type, DFIRe attaches copies of the selected runbooks to the item, so standard procedures are always present without anyone having to remember them.

    Runbooks already attached to items are independent copies. Editing the default runbooks of an item type only affects items created afterwards.

  5. Create the item type

    Choose Create item type, or Save item type when you edit one. JSON at the top of the page shows the whole definition as JSON to edit or copy. Visual returns to the form.

Set your item types up before going into production. Changing a type's fields does not rewrite the details already recorded on existing items, so a field renamed or removed later leaves earlier items holding values under the old name. Changing the default category changes only the items added afterwards.