Skip to main content

MISB ST 0903 General Info

Overview​

MISB ST 0903 defines VMTI metadata used to report detections, targets, and related scene information for video exploitation workflows.

VMTI

In ST Inspector, ST 0903 data is typically encountered as a nested VMTI local set inside MISB ST 0601 Tag 74. The application decodes that nested payload and validates both the local-set structure and the internal consistency of the reported VMTI content.

What ST Inspector Checks​

The MISB ST 0903 rules currently cover:

  • nested VMTI local-set decode validity
  • revision detection
  • unknown-tag detection by resolved revision
  • root-field decode correctness
  • duplicate root-tag detection inside one VMTI local set
  • internal dependency checks across counts, dimensions, references, and tracker timestamps
  • required parent metadata on the surrounding MISB ST 0601 packet for embedded VMTI use

Typical Failure Themes​

Common MISB ST 0903 findings include:

  • malformed or truncated embedded VMTI local sets
  • unsupported or invalid revision declarations
  • root tags that are not valid for the resolved revision
  • known fields whose encoded value cannot be decoded correctly
  • repeated root tags in the same VMTI set
  • inconsistent target, frame, or tracker relationships
  • missing parent-packet tags required when VMTI is carried inside ST 0601

Use the pages under this section when you need rule-by-rule detail for a specific ST 0903 finding.

  • Start with VMTI Local Set Decode when the VMTI payload itself does not parse.
  • Check VMTI Revision Detect and VMTI Unknown Tag for Revision for schema and revision issues.
  • Use VMTI Field Decode, VMTI Duplicate Tags, and VMTI Field Dependencies for content-level failures.
  • Use Embedded VMTI Parent Metadata when the VMTI payload is valid but the surrounding ST 0601 packet is missing required context.