AI Security Extension
Objective
Implement Core + L5 (security subset) with 16 mandatory fields.
UAIF requirement
Optional: Attack vector fields. Prohibited: L3, L4.
Business impact
Defines a conformance profile and its expected record surface for a stated adoption use case.
Validation approach
Apply the specification-defined conformance profile deterministically and retain the input, expected result, actual result, version and reviewer disposition.
Expected evidence
Versioned input fixture or incident record, calculation or test trace, expected outcome, actual outcome, exception record and reviewer approval where required.
Mapping and source
UAIF Technical Specification and its applicable taxonomy, profile or conformance clause.
Implementation guidance
Implement this conformance profile as a versioned UAIF rule. Keep configuration, thresholds and exceptions visible; do not represent it as an independently certifiable GAISSF control.
Assessment considerations
Test representative, boundary, adverse and conflicting inputs. Confirm repeatability, version alignment, exception handling and retention of the complete decision or calculation trace.
Artifact classification
This page documents a UAIF taxonomy, calculation or conformance artifact. It must not be represented as an independently certifiable control unless a future approved assurance publication expressly establishes that status.