Skip to main content

MISB ST 0102 General Info

Overview​

MISB ST 0102 defines the Security Metadata Local Set used to carry security markings alongside motion-imagery metadata.

In ST Inspector, this metadata is typically encountered as a nested local set inside MISB ST 0601 Tag 48. The application decodes that nested payload and applies rule checks that focus on structure, revision handling, required tags, field decoding, and semantic consistency.

What ST Inspector Checks​

The MISB ST 0102 rules currently cover:

  • nested local-set decode validity
  • revision detection
  • required-tag presence by revision
  • unknown-tag detection by resolved revision
  • field-level decode correctness
  • duplicate-tag detection inside one security local set
  • dependency checks between coding-method fields and related country-code fields

Typical Failure Themes​

Common MISB ST 0102 findings include:

  • malformed or truncated nested local sets
  • unsupported or undecodable revision values
  • required security tags missing from the set
  • tags that do not belong to the resolved revision
  • invalid encoded values for known fields
  • repeated tags inside a single security metadata set
  • country-code fields present without the required supporting coding-method fields

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

  • Start with Security Local Set Decode when the nested payload does not parse at all.
  • Check Security Metadata Revision Detect, Required Tags, and Unknown Tag for Revision when the issue is schema or revision related.
  • Use Field Decode, Duplicate Tags, and Field Dependencies for content-level interpretation after the set has already decoded.