{"id":5120,"date":"2021-10-15T13:32:44","date_gmt":"2021-10-15T17:32:44","guid":{"rendered":"https:\/\/www.exchangedefender.com\/blog\/?p=5120"},"modified":"2021-10-15T13:32:47","modified_gmt":"2021-10-15T17:32:47","slug":"phishing-protection-gets-new-terminology","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2021\/10\/phishing-protection-gets-new-terminology\/","title":{"rendered":"Phishing protection gets new terminology"},"content":{"rendered":"\n<div style=\"height:43px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter is-resized\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.exchangedefender.com\/blog\/wp-content\/uploads\/2021\/10\/phishing-protection.png\" alt=\"\" class=\"wp-image-5124\" width=\"803\" height=\"525\" srcset=\"https:\/\/www.exchangedefender.com\/blog\/wp-content\/uploads\/2021\/10\/phishing-protection.png 650w, https:\/\/www.exchangedefender.com\/blog\/wp-content\/uploads\/2021\/10\/phishing-protection-300x196.png 300w\" sizes=\"auto, (max-width: 803px) 100vw, 803px\" \/><\/figure><\/div>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>At ExchangeDefender, we are unique just like our clients. Our team members are all from different nationalities, backgrounds, and expertise.<\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>We do not aim to offend or demoralize any individual or groups, unless the<em>y are spammers or hackers<\/em>. \ud83d\ude42<\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>Some of the industry standard terms used in the backend, that have been part of IT for decades, may sound offensive to clients in the modern workplace. Non-technical clients who are not accustomated to traditional IT terms are rightfully shocked when they see terms like &#8220;master-slave replication&#8221;, &#8220;whitelist&#8221;, and other similar racially sensitive wording. <\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>SPAM filtering and email security should not be offending our clients so <strong>we&#8217;ve gone through an audit<\/strong> of our web site, our portals, our mobile apps, and our backend <strong>in an effort to rephrase<\/strong> some of the industry terms that may be offensive.\u00a0 <\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>Our client base has changed over the past 24 years, (our services are predominantly used by non-technical staff) and this was a part of our larger effort to make ExchangeDefender more user-friendly.\u00a0 <\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>We want to make our services more accessible for users that have never used ExchangeDefender, or an enterprise security software; you will see fewer IT acronyms. Instead, we&#8217;re rephrasing our services to sound like spoken English, for example: To block senders from sending you SPAM you will now add their address to a <strong>&#8220;Block list&#8221;<\/strong>. <\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p> [&hellip;]<\/p>\n","protected":false},"author":50,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[88],"class_list":["post-5120","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-phishing"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5120","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\/50"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=5120"}],"version-history":[{"count":9,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5120\/revisions"}],"predecessor-version":[{"id":5130,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5120\/revisions\/5130"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=5120"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=5120"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=5120"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}