A guardpoint manages access to a single Workspace with an encryption key. You set a guardpoint as part of the encryption process to create additional security layer. You should generate a guardpoint for each Workspace. 

Keys are used to encrypt data and keys should be updated (rotated) at a regular interval to comply with your company's security policy.

The purpose of key rotation is to retire an encryption key and replace it with a recently-generated, cryptographic key. 

These guardpoint events are tracked:

Event CodeEvent MessageAssociated Object ID
DSM-071
displays as: 
DSM-DAO0071I 		Create a key pair with a keyThe user ID associated with the action to create key pair with a key.
DSM-229
displays as: 
DSM-DAO0229I 		Add a guardpoint with a policyThe user ID associated with the action to add a guardpoint.
DSM-231
displays as: 
DSM-DAO0231I 		Add a group guardpointThe user ID associated with the action to add a group guardpoint.
DSM-235
displays as: 
DSM-DAO0235I 		Update a guardpointThe user ID associated with the action to update guardpoint
DSM-238
displays as: 
DSM-DAO0238I 		Delete a group guardpointThe user ID associated with the action to delete a group guardpoint.
DSM-240
displays as: 
DSM-DAO0240I 		Delete a symmetric key with a key The user ID associated with the action to delete a symmetric key with a key.
DSM-281
displays as: 
DSM-DAO0281I 		Delete an online policyThe user ID associated with the action to delete online policy
DSM-501
displays as:
DSM-DAO0501I		Marked guardpoint pending delete with a policyThe user ID associated with the action to mark the guardpoint pending delete with a policy
DSM-502
displays as:
DSM-DAO0502I		Delete a pending guardpoint with a policy The user ID associated with the action to delete pending guardpoint with policy.

Note: In addition to the guardpoint introduction above, a guardpoint specifies the list of folders of the paths to be protected. File folder access and encryption within the guardpoint is controlled by security policies.