This read-only DisplayString, up to 80 characters, is described as the name of the hash algorithm actually negotiated for this SA. An admin checks this to verify the negotiated integrity-protection hash matches the intended security policy, since a mismatch could mean the crypto map fell back to a weaker allowed option. For example, an admin who intended all tunnels to use SHA-based hashing would check this field and flag any SA that instead shows an MD5-based hash.