{"id":2550,"date":"2019-06-03T13:38:58","date_gmt":"2019-06-03T17:38:58","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/?p=2550"},"modified":"2019-06-03T13:38:58","modified_gmt":"2019-06-03T17:38:58","slug":"phishing-beware-of-strangers","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2019\/06\/phishing-beware-of-strangers\/","title":{"rendered":"Phishing: Beware of Strangers"},"content":{"rendered":"\n

This Thursday, June 6th,<\/a><\/strong> we will be announcing a major overhaul in the way we deal with spear phishing SPAM. No, it\u2019s not a mind-blowing patent-pending stroke-of-genius sort of stuff, it\u2019s much closer to what your parents told you growing up: Don\u2019t get into a car with strangers<\/s> don\u2019t click on links or open attachments from strangers. <\/p>\n\n\n\n

In a way, ExchangeDefender has had protection from this issue for years. If you had a decent IT Solution Provider implementing ExchangeDefender for you, they would have setup your SPF record and eliminated this issue \u2013 but many don\u2019t. Or they would have turned on ExchangeDefender protection where all messages spoofing\/forging your domain would automatically get junked \u2013 almost none of them do. Which is why ExchangeDefender as a service has become less of an IT tool and more of an end user suite of services to get stuff done. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

When features like this are left disabled \u201cbecause they might become support issues\u201d it becomes really difficult to secure users. But I get it, IT companies have a business to run too, which is why we\u2019ve really stepped up our support efforts and are going to be there to help folks get things done without becoming an additional problem for the IT department. Doing so has really made us rethink how we implement features and how the service behavior needs to speak the same language as the end user. Which brings me to phishing beyond forgeries. <\/p>\n\n\n\n

Can you spot a stranger?One of the new phishing protection features in ExchangeDefender will allow you to flag messages that are coming from outside of your organization. You will have two settings \u2013 to modify the subject and to modify the header of the message so when you look inside of your mailbox you\u2019ll know what came from a stranger right away. Try it: <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Even from the message listing you\u2019ll know which messages shouldn\u2019t even be opened. But suppose you ignored even that \u2013 you can set another warning, printed inside of the message, giving the user even more of an instruction of what to do. <\/p>\n\n\n\n

Warning:<\/strong><\/em> Message was sent from outside of the organization. Do not click on links or open attachments if you don\u2019t recognize the sender. <\/strong><\/p>\n\n\n\n

Far from subtle<\/strong>. And it has to be \u2013 because most people check email quickly, between tasks, or are simply interrupted by it. ExchangeDefender has your back, and we\u2019ll make sure we alert you to possible issues before they become problems. Which we hope everyone will be aboard with. <\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Please join us, June 6th at Noon<\/a>, for our NEW webinar featuring ExchangeDefender\u2019s Phishing and Spoofing protection, plus see what\u2019s new with Encryption, WFS, and Wrkoo! <\/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,1,47,46,48,17,13],"tags":[114,88,136,135,92],"class_list":["post-2550","post","type-post","status-publish","format-standard","hentry","category-exchangedefender","category-uncategorized","category-industrynews","category-product-features","category-security","category-support","category-webinars","tag-new-feature","tag-phishing","tag-phishing-protection","tag-phishing-webinar","tag-webinar"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2550","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=2550"}],"version-history":[{"count":5,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2550\/revisions"}],"predecessor-version":[{"id":2558,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/2550\/revisions\/2558"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=2550"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=2550"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=2550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}