Exploit Path Description
Objective
Capture and validate the exploit path description element within the Causal Separation Chain layer.
UAIF requirement
The incident record should implement the canonical exploit_path_description field using the defined UAIF data type, validation constraints, and conditional rules.
Business impact
Supports defensible separation of initiating cause from observed manifestation and records uncertainty in causal attribution.
Validation approach
Validate exploit_path_description for length constraints. Then review semantic consistency against the source incident evidence and the selected conformance profile.
Expected evidence
Retain the source record or analyst input for exploit_path_description, 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/exploit_path_description.
Implementation guidance
Populate exploit_path_description 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 exploit_path_description 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 | exploit_path_description |
|---|---|
| Required in core profile | No |
| Type | "string" |
| minLength | 20 |
| maxLength | 4000 |
Source: UAIF Schema Specification and UAIF Core JSON Schema.