Record Type
Objective
Capture and validate the record type element within the Incident vs. Vulnerability layer.
UAIF requirement
The incident record should implement the canonical record_type field using the defined UAIF data type, validation constraints, and conditional rules.
Business impact
Preserves the different evidentiary and workflow treatment of incidents, vulnerabilities and observations.
Validation approach
Validate record_type for required in the Core profile, controlled vocabulary membership. Then review semantic consistency against the source incident evidence and the selected conformance profile.
Expected evidence
Retain the source record or analyst input for record_type, 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/record_type.
Implementation guidance
Populate record_type 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 record_type 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 property | record_type |
|---|---|
| Required in core profile | Yes |
| Type | "string" |
| Allowed values | Incident, Vulnerability, Observation |
Source: UAIF Schema Specification and UAIF Core JSON Schema.