APE Assurance Protocol Error
To report assurance protocol errors in a security structure
Sequence
Element
Name
Type
Requirement
Min
Max
Repeat
Code specifying the business purpose of the appended assurance to an existing
secured-entity (whether functional group or transaction set); the codes
represent the intention of the business or application that has control over
the assurance originator
Codes (24)
Code specifying the bounds of the text, whether contiguous or not, over which
the computation of the Assurance Token is computed using the defined
methodology of computation and any relevant Assurance Token parameters
The "body" is defined as a transaction set, beginning with the first byte of
the segment immediately following the ST segment terminator and including all
segments up to but not including the "S" in the first SVA segment; DO NOT
include any S4A segments
The "body" can also be defined as a functional group, beginning with the first
byte of the segment immediately following the GS segment terminator and
including all transaction sets up to but not including the "S" in the first SVA
segment at the functional group level; DO NOT include any S3A segments
"This Assurance" is defined as from the "S" in S3A or S4A up to and including
the segment terminator of that segment
"Previous Assurance(s)" is defined as including the entire S3A or S4A segment
and the entire corresponding SVA segment that is associated with the S3A or S4A
at the same level
Codes (7)
Code identifying a specific security protocol error
Codes (13)
Unique designation (identity) of the cryptographic process that performs the
stated assurance on data to be interchanged
Note: X9 has a required minimum length of 4 characters for a security
originator; no mechanism, or registration method, is provided by X9 or X12 to
guarantee uniqueness of the identifier
Unique designation (identity) of the cryptographic process that performs
validation of the stated assurance on received data. In the absence of an
Assurance Recipient all potential receivers will often be able to validate the
assurance because the cryptographic technique is based on a "public" (as
opposed to "secret") technology
Note: X9 has required minimum length of 4 characters for a security recipient;
no mechanism, or registration method, is provided by X9 or X12 to guarantee
uniqueness of the identifier