{"id":2156,"date":"2018-09-25T12:55:57","date_gmt":"2018-09-25T16:55:57","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/?p=2156"},"modified":"2018-09-25T13:03:36","modified_gmt":"2018-09-25T17:03:36","slug":"new-feature-encryption-enrollment-account-reset","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2018\/09\/new-feature-encryption-enrollment-account-reset\/","title":{"rendered":"New Feature: Encryption Enrollment Account Reset"},"content":{"rendered":"

<\/h3>\n

\"\"<\/a><\/h3>\n

<\/h3>\n

 <\/p>\n

ExchangeDefender Encryption Enrollment Account Reset<\/h3>\n

Encryption<\/a> is hot \u2013 with daily news of hackers breaking in or compromising one system after another, taking that extra step to make sure your information is safe and secure has never been on the minds of business owners more. We may sound like a broken record when it comes to encryption but it is one of our more popular products and today we\u2019re happy to announce another quick feature that is coming.<\/p>\n

October 1st: You can now reset your recipients accounts (PIN+Password) in Corporate Encryption.<\/h3>\n

ExchangeDefender Corporate Encryption<\/a> has an alternate [ENCRYPT] flag that can allow the users to encrypt messages on demand and require the recipient to enroll in the ExchangeDefender Corporate Encryption<\/a> in order to access the message. Enrollment process is quick and simple and requires the recipient to provide their name and phone number along with a selection of a password and a 4 digit PIN. This additional security step is put in place to eliminate man in the middle attacks where a hacker may have compromised the firewall, disgruntled employee is trying to spy on inbound mail, or a variety of other threatening issues. It is the ultimate layer of protection because PIN is only known to the user.<\/p>\n

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

If you support ExchangeDefender Corporate Encryption<\/a>, you\u2019re going to like this feature a lot because you\u2019ve likely had to deal with the inevitable case of a recipient forgetting both their password and their PIN. Since we have no way to verify the users identity, we\u2019ve always processed reset requests manually. Now, this process is automated.<\/p>\n

Just go to admin.exchangedefender.com<\/span> and login as the domain administrator.<\/strong>\u00a0 If you subscribe to Corporate Encryption<\/a> you will see it under the Configuration menu. Simply type in the recipients email address and their account at ExchangeDefender will be reset allowing them to enroll again.<\/p>\n

As a security precaution, they will not be able to see emails sent to them prior to the enrollment period \u2013 only new messages after they have created their account. On the backend, there are additional checks in order to make sure that this is actually a user that receives email from your domain, etc, etc so we don\u2019t open the door to a malicious ExchangeDefender client attempting to reset accounts of unknown contacts. Obviously there is far more going on in the background that we cannot disclose in a blog post but if you\u2019re interested in the technology, we have patents pending on several of these and would be happy to discuss privately.<\/p>\n

There you have it, October 1st<\/strong>. Another cool feature that will save a lot of time for our users while keeping everyone just a little bit safer. We\u2019re adding more features all over the place so please stay tuned to our blog and our Facebook page.<\/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":[4,48],"tags":[52,39,40],"class_list":["post-2156","post","type-post","status-publish","format-standard","hentry","category-exchangedefender","category-security","tag-email-security","tag-encryption","tag-security"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2156","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=2156"}],"version-history":[{"count":16,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2156\/revisions"}],"predecessor-version":[{"id":2175,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2156\/revisions\/2175"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=2156"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=2156"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=2156"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}