When a tag is no longer relevant or no longer valid based on your business requirements, you can deactivate it by revoking it. You can also reactivate a revoked tag when necessary. In the case of BloxOne Threat Defense Cloud objects tags having been revoked, the revoked tags will continue to follow the original, defined tag rules configured in decurity a policy possessing a higher precedence than the security policy where the BloxOne Threat Defense Cloud objects are defined. For example, if the scope policy for tags has a precedence of 1 while the policy containing the objects has a precedence order of 2 or lower, then due the higher precedence of the tag policy, any objects contained within the policy will continue to function as if the tags are still applied. However, the Cloud Services Portal will show the tag as being revoked for the object. If tags are reactivated, then the tags will re-associate with their respective objects, and the policy rules will function for the network scopes based on how the tags were originally defined.
To deactivate a tag, complete the following:
...