One Article Review
| Source |  ProofPoint |
|---|---|
| Identifiant | 8611074 |
| Date de publication | 2024-11-14 09:41:20 (vue: 2024-11-14 14:07:48) |
| Titre | What\\'s the Best Way to Send Transactional Email? |
| Texte | One of the things I like about being in cybersecurity is knowing my company helps protect others from criminals looking to exploit them. At every customer-facing event that I go to, customers tell me how many times our solutions have made them look good with their executives. But many of these same people may be doing something that has the potential to make them look very bad. You may be in a similar situation and not even know it. So that is what I\'ll cover today-steps you can take to reduce the chances that your transactional emails impact your user-generated messages. In this blog post, we are going to assume that you are already familiar with what we mean by transactional email. However, if you would like to better understand this topic-including where transactional emails are generated and why they are so important-read our blog “Transactional Emails: Best Practices and Background.” 3 Methods for relaying transactional email Let\'s start by exploring the three different methods for relaying transactional email. 1: On-premises mail transfer agent (MTA) Microsoft Exchange is an example of an on-premises solution that can be used to relay transactional email. There are several challenges with using this type of solution. For starters, it can be costly to maintain physical servers and pay for licensing. Also, when the solution hits end-of-life, support becomes an issue. Moreover, this method typically doesn\'t align with a company\'s desire to move these types of functions to the cloud. And since authentication is not required to submit messages via the host name, it can be abused by bad actors. 2: Email service provider (ESP) ESPs are third parties that can relay transactional email on a company\'s behalf. This method is often popular because it\'s inexpensive. Unfortunately, these are the same reasons why it\'s frequently targeted. Bad actors can easily register accounts to launch attacks or compromise existing accounts. If bad actors compromise your authorized ESP infrastructure (or app-owner accounts) “upstream,” then they can send malicious email on your behalf. What\'s worse is that it will likely be delivered because it will pass email authentication. 3: Sending transactional email through your user-generated sending IPs This is the riskiest method. Frequently, the risks far outweigh the convenience and potential cost savings. Email is one of the most critical forms of business communications that we use today. Any issues that are caused by an application or third-party sending email on your behalf could jeopardize these sending IPs. In fact, this method is so risky that many email providers are now precluding companies from using this method in their terms of use. Key issues with this method: Transactional emails are typically sent in much higher volumes. This can impact performance, resulting in delays of business-critical emails (“did you get it yet?”). Messages sent via an “open relay” can result in blocklisting. When you allow third parties to send on your behalf, you could be creating an “open relay.” If exploited, this can result in your main sending IP addresses being blocklisted. Blocklisted addresses can grind business to a halt. Whether high volumes of traffic is the result of compromise or just a rogue app, any blocklisting of your addresses can bring down your company\'s entire business operations. That last bullet is the scariest one to face. You don\'t want to put yourself in a position where all your email is blocked due to something that occurs with your transactional email. Believe me, it can happen. And when it does, any thoughts about your cost savings will be overshadowed by the urgency to get your email flowing again quickly. What is the best method? By far, sending transactional email from a dedicated email environment is the best method. With this method, you use a dedicated gateway environment that is specifically designed f |
| Notes | ★★ |
| Envoyé | Oui |
| Condensat | about abused accounts actors add addition addresses again against agent align all allow allows already also another anti antivirus any app apple application applications are assume attacks authenticated authentication authorized available background bad based because becomes been before behalf being believe benefits best better between blocked blocklisted blocklisting blog bonus brand bring bullet business but can cause caused centralized challenges chances clean click cloud comes communications companies company compromise compromised content control convenience cost costly could cover create created creating criminals critical customer customers cybersecurity damage dedicated delays deliverability delivered designed desire different dkim dlp does doesn doing domain don down due easily effective email email emails emails: encryption end ensure entire environment esp especially esps even event every example exchange executives existing expect exploit exploited exploring face facing fact familiar far flowing forms frequently from functions gateway generated get gets going good google/yahoo grind halt happen has have header help helps high higher historically hits host how however identity immediately impact impersonation important including increase industry inexpensive infrastructure inject internally ips ips issue issues jeopardize just key know knowing last launch layer leaders let level licensing life like likely link lists look looking made mail main maintain make malicious manage many may mean meet messages method method: methods microsoft might more moreover most move mta much name need new not now occurs off offer often one ons operations organization others out outside outweigh over overshadowed overview owner parties partners party pass pay people performance physical point popular position post potential practice practices precluding premises process proofpoint protect protective provider providers put quick quicker quickly read reasons recipients reduce register relay relaying relays relay” required requirements resources restrict result resulting retire riskiest risks risky rogue saas sacrificing safeguards same savings scanned scanning scariest secure security send sending sensitive sent separate separating separation ser ser servers service several shut signature significant similar since situation skills solution solutions something sources spam specifically start starters steps submit support support dmarc initiatives take targeted technology tell terms than that them then these they things third thoughts three through times today topic traffic transactional transfer type types typically understand unfortunately unsubscribe unsubscribe” urgency use used user users using very video: viruses volumes waiting want watch way what when where whether why will without works worse would yet you your yourself “did “one “open “transactional “upstream “what ” |
| Tags | Threat Cloud |
| Stories | Yahoo |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.