Get access to immediate incident response assistance.
Eliminate active threats with 24/7 threat detection, investigation, and response.
Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.
Advance your cybersecurity program and get expert guidance where you need it most.
Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.
Prevent unauthorized access and exceed compliance requirements.
Stop email threats others miss and secure your organization against the #1 ransomware attack vector.
Prepare for the inevitable with 24/7 global breach response in-region and available on-site.
Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.
MailMarshal uses the following criteria to identify and block all spoofed email, legitimate and otherwise:
In some cases you may want to allow email messages generated elsewhere to pass through. For instance, email distribution list groups often send email as the user.
To allow legitimate email to pass, you can add exclusions to the Block Spoofed Messages rule.
Sample TextCensor script:
The following script, specified in the Edit TextCesor Script dialog box, above, does not block spoofed email with fedex, cnn.com, msnbc, or webex in the message subject: "NOT (fedex OR cnn.com OR msnbc OR webex)"
"NOT (fedex OR cnn.com OR msnbc OR webex)"
Notes: This script assumes that the text you are matching is in the message subject. It does NOT check the sender email address. Many distribution lists provide unique identifying text in the subject. Matching on sender email addresses is very likely to allow unwanted spoofed items. Add any additional keywords to the existing entry - NOT as a new TextCensor item. For instance the line could read: "NOT (fedex OR cnn.com OR msnbc OR webex OR yahoo)"
Notes:
When a message arrives Where message is incoming Where message triggers text censor script(s) 'Spoofing Exclusions' And where message spoofing analysis is based on 'anti-relay' Send a 'Spoofed Message In' notification message And write log message(s) with 'Spoofed Message Inbound' And move the message to 'Spoofed Messages'
'Spoofing Exclusions'
'anti-relay'
'Spoofed Message In'
'Spoofed Message Inbound'
'Spoofed Messages'
This article was previously published as: NETIQKB34945
To contact Trustwave about this article or to request support: