{"id":5738,"date":"2023-03-03T20:24:49","date_gmt":"2023-03-04T01:24:49","guid":{"rendered":"https:\/\/www.exchangedefender.com\/blog\/?p=5738"},"modified":"2023-03-03T20:27:03","modified_gmt":"2023-03-04T01:27:03","slug":"exchangedefender-phishing-firewall-is-live","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2023\/03\/exchangedefender-phishing-firewall-is-live\/","title":{"rendered":"ExchangeDefender Phishing Firewall is Live!"},"content":{"rendered":"\n
<\/div>\n\n\n
\n
\"\"<\/a><\/figure><\/div>\n\n\n
<\/div>\n\n\n\n

As mentioned previously<\/a><\/strong> our new ExchangeDefender Phishing Firewall went live in production at noon EST today (March 3rd, 2023) and is already rewriting URLs unique to service provider that manages the domain.<\/p>\n\n\n\n

<\/div>\n\n\n\n

A little bit about the technology<\/h3>\n\n\n\n


URL \/ link rewriting is an industry standard used by biggest email providers to rewrite potentially dangerous URLs. When the user clicks on the link they are redirected to a Phishing Firewall site instead of the direct web site address that was in the email. The phishing firewall looks at all the domain policies, allow\/block lists, exceptions, and determines if the user should be allowed to proceed to the web site.<\/p>\n\n\n\n

<\/div>\n\n\n\n

When the messages arrive into your organization, instead of https:\/\/www.yahoo.com<\/strong> the URL is rewritten to something like https:\/\/exchangedefender<\/mark><\/strong>.xdref.com\/url=hash<\/strong>. These masked URLs are only visible to our clients, when they reply to an email the outbound network reverses the process. Outbound network replaces https:\/\/<\/mark>exchangedefender<\/mark>.xdref.com\/url=hash<\/mark><\/strong>with the original URL.<\/p>\n\n\n\n

<\/div>\n\n\n\n

This technology eliminates the possibility that a random hacker can deliver a payload that is one click away from the user. Additionally, it gives the user the ability to check the site reputation, check for viruses, and clearly see the URL they are going (instead of a squashed little tooltip with a 200+ character URL). Essentially, we study how people get hacked with phishing and try to eliminate those issues.<\/p>\n\n\n\n

<\/div>\n\n\n\n

All the sites and services are fully encrypted and partners\/clients do not need to worry about certificate renewals, site mappings, etc – everything is automatic and done for you. Set it and forget it<\/s> just keep an eye on the logs.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Going Forward<\/h2>\n\n\n\n
<\/div>\n\n\n\n

As of March 3rd, 2023 all the URLs will be rewritten using service providers id. Main benefit of this upgrade is that it reduces the scope and likelihood that the URL gets inadvertently reported or picked up by another security service that may deem xdref.com<\/a> to be a masking site for dangerous content.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Additionally, you can configure your firewall to only accept unapproved URLs after a hop through <yourspid<\/strong>>.xdref.com<\/a>. It also gives you full visibility into everything that happens with the URL, who clicks on it, where they go, etc which is something we do for our clients to address cybersecurity compromise and trace back how it happened (very lucrative service for partners that may be interested in deploying that level of protection.<\/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":[153,88],"class_list":["post-5738","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-exchangedefender-phishing-firewall","tag-phishing"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5738","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=5738"}],"version-history":[{"count":8,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5738\/revisions"}],"predecessor-version":[{"id":5747,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5738\/revisions\/5747"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=5738"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=5738"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=5738"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}