Skip to content

MISP Object Proposal: container-instance #494

@damasch

Description

@damasch

There is no structured way to represent running or stopped containers in forensic investigations.

Introduce container-instance to describe runtime container details.

Proposed Attributes:

  • container-id (text)
  • image (link to container-image)
  • command (text)
  • created (datetime)
  • started (datetime)
  • finished (datetime)
  • state (text: running, exited, paused)
  • hostname (text)
  • user (text)
  • privileged (boolean)
  • capabilities (text)
  • security-opt (text)
  • mounts (text)
  • network-mode (text)
  • ip-address (ip-dst)
  • ports (text)
  • environment-variables (text)

Using host-based forensic artifacts, but this loses container-specific isolation context.

Useful for DFIR scenarios, especially when analyzing compromised hosts running containers.

related to: #493 #495

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions