{"id":399,"date":"2012-05-04T10:26:41","date_gmt":"2012-05-04T15:26:41","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/2012\/05\/exchangedefenderlexicon-pattern-matching-encryption\/"},"modified":"2012-05-04T10:26:41","modified_gmt":"2012-05-04T15:26:41","slug":"exchangedefenderlexicon-pattern-matching-encryption","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2012\/05\/exchangedefenderlexicon-pattern-matching-encryption\/","title":{"rendered":"ExchangeDefender–Lexicon & Pattern Matching Encryption"},"content":{"rendered":"

This week our main focus has been implementing more advanced encryption methods. These new additions will be available sometime next week and will require an additional fee to enable these features. This new system implements two new types of encryption \u201ctriggers\u201d that will flag the messages and send them through the encryption process. <\/p>\n

Lexicon Encryption<\/b> <\/p>\n

The first method is called Lexicon Encryption<\/b>. This feature works by examining a pre-defined set of keywords that act as encryption triggers anytime they are encountered inside a message. Once a keyword is located inside of a message, that message is sent through our encryption process. <\/p>\n

The [Default Action] <\/b>determines the action that occurs once the message hits the encryption system. You can choose one of the following: <\/p>\n

\n

Encrypt<\/b> <\/p>\n

*This is the normal encryption process, which will deliver a secure link to the user\u2019s mailbox and require a password to view the message. <\/p>\n

Clear Encrypt<\/b> <\/p>\n

*This method is similar to the normal encryption method, except a password is not required to view the message.  <\/p>\n

Alert Administrator<\/b> <\/p>\n

*This method, delivers an encryption summary to the domain administrator and will require them to (view, deliver, delete) the message before it reaches the user. <\/p>\n<\/blockquote>\n

We understand that some users may already have a predefined list from another 3rd<\/sup> party or software provider. So we have implemented a very simple \u201cimport\u201d process which will allow you import these keyword definitions. <\/p>\n

The format is .CSV and is implemented in the following sequence: (keyword, category<\/b>)<\/i> <\/p>\n

\"Configuration\"<\/a> <\/p>\n

  <\/p>\n

Pattern Matching<\/b> <\/p>\n

The next method is called Pattern Matching<\/b>. This approach examines the message for a series of common patterns found when referencing things like (credit card numbers, social security numbers and birthdays.<\/i>) Later in the year we also plan on implementing custom pattern matching, which will allow you to enter your own custom defined patterns. <\/p>\n

Once any of these patterns is located inside of a message, the same encryption process will occur. Unlike Lexicon matching, each individual pattern is allowed to have a different action. This will help route crucial and confidential information more accurately. <\/p>\n

\"Configuration-2\"<\/a> <\/p>\n

Hank Newman
VP Development, ExchangeDefender
hank@ownwebnow.com<\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-399","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/399","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=399"}],"version-history":[{"count":0,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/399\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=399"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=399"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=399"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}