UAIF / L0 / L0-F01

Incident Uuid

Objective

Capture and validate the incident uuid element within the Incident Identity & Workflow layer.

UAIF requirement

The incident record should implement the canonical incident_uuid field using the defined UAIF data type, validation constraints, and conditional rules.

Business impact

Supports stable incident identity, deduplication, workflow tracking and an auditable reporting record.

Validation approach

Validate incident_uuid for required in the Core profile. Then review semantic consistency against the source incident evidence and the selected conformance profile.

Expected evidence

Retain the source record or analyst input for incident_uuid, schema-validation output, transformation history, selected profile, schema version and reviewer rationale where judgement is involved.

Mapping and source

UAIF Schema Specification; UAIF Technical Specification; JSON pointer /properties/incident_uuid.

Implementation guidance

Populate incident_uuid from an identified source or documented analyst decision. Enforce the schema constraints at record creation and update, preserve the original value and provenance, and surface validation failures without silently coercing data.

Assessment considerations

Sample records across normal, boundary and invalid conditions. Confirm that incident_uuid is populated only when applicable, conditional rules are enforced, provenance is retained and downstream systems do not change its meaning or precision.

Canonical schema definition

JSON propertyincident_uuid
Required in core profileYes
Type"string"
formatuuid

Source: UAIF Schema Specification and UAIF Core JSON Schema.