Encryption Content Filter vs. DLP Encrypt Action

[johnsmith1000]

As I go through the IronPort Email Config Guide, I see two places that email encryption is mentioed:

1) Under DLP configuration (chapter 11): as an action for DLP policy violation 

2) Under Email Encryption configuration (chapter 12): as a content filter which determines which messages should be encrypted

Are both of these methods using the same encryption engine? Does DLP "encrypt" policy action ends up invoking CRES and send an encrypted message to a recipient which has the same format as the encrypted message generated by encryption content filter (assuming no DLP filter configured)?

Thanks.

[kjohnson1024]

I ran into this recently and both of them use the same encryption engine. DLP policies will trigger messages to be encrypted; however, policies are processed top to bottom and left to right, so DLP policies will be enforced after Content Filter policies. Additionally, each policy can be set with specific features. In my opionon, Content Filters provide more options to catch interesting traffic via regular expressions, dictionarys, text resources, etc.