<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic In Incoming Mail Policy, we in Email Security</title>
    <link>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076855#M15744</link>
    <description>&lt;P style="padding-left: 30px;"&gt;In Incoming Mail Policy, we recommend enabling Antivirus, AMP and Outbreak Filtering. In Outbreak filtering policy make sure to have Message Modification feature enabled with URL Rewrite so suspicious emails are tagged to warn end users about these emails. As long as the threat level is about 3 (default) it should trigger the tagging to warn users.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Apr 2017 14:02:46 GMT</pubDate>
    <dc:creator>Sriram Subramanian</dc:creator>
    <dc:date>2017-04-21T14:02:46Z</dc:date>
    <item>
      <title>Scaning for Phishing in an Attachment</title>
      <link>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076851#M15740</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;We are seeing emails with attachments coming through our Ironport ESA&amp;nbsp;that are being used for Phishing. It was a PDF (or appears to be a PDF) attachment named Dropbox.PDF. When the user clicked on it, it&amp;nbsp;brought up a bogus&amp;nbsp;link to a dropbox that was asking to login with credentials.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;How can we configure the ESA to scan attachments for Phishing and if we do will it catch something like this? Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 05 Apr 2017 18:34:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076851#M15740</guid>
      <dc:creator>techtone</dc:creator>
      <dc:date>2017-04-05T18:34:22Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076852#M15741</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The Sophos scanning engine and AMP File reputation File Analysis features should scan for these phishing attachments.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;If there are attachments missed by these it is recommended to open a TAC case to get the rules updated for newer threats.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Apart from that if you would like to block attachments with specific filenames you can certainly use content/message filters for the same.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thank You!&lt;/P&gt;
&lt;P&gt;Libin Varghese&lt;/P&gt;</description>
      <pubDate>Wed, 05 Apr 2017 19:20:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076852#M15741</guid>
      <dc:creator>Libin Varghese</dc:creator>
      <dc:date>2017-04-05T19:20:48Z</dc:date>
    </item>
    <item>
      <title>Depending on the PDF --- if</title>
      <link>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076853#M15742</link>
      <description>&lt;P&gt;Depending on the PDF --- if the PDF only contains a URL that requires the end-user to interact and click on the URL to take them off-PDF and TO the malicious/phish site, the ESA currently is not capable of scanning that from AMP on ESA. &amp;nbsp;These PDF files are usually flagged from AV rules, or VOF rules. &amp;nbsp;AMP will take into account these rules, and readjust the scoring --- and will send out retrospective scoring adjustments based on the SHA reported from the ESA.&lt;/P&gt;
&lt;P&gt;Any missed phish emails, emails with attachments - they can be directly submitted to Cisco:&lt;/P&gt;
&lt;P&gt;phish@access.ironport.com&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A class="jive-link-email-small" href="mailto:spam@access.ironport.com" rel="nofollow noopener noreferrer"&gt;spam@access.ironport.com&lt;/A&gt;&amp;nbsp;-&amp;nbsp;Subject is prepended with [SUSPECTED SPAM] and is actual spam. &amp;nbsp;Forwarding this will assist the product efficacy team confirm the content and possibly score it lower.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="mailto:ham@access.ironport.com" target="_self" rel="nofollow noopener noreferrer"&gt;ham@access.ironport.com&lt;/A&gt; -&amp;nbsp;Subject is prepended with [SUSPECTED SPAM], but it is not spam, or&amp;nbsp;Subject is prepended with [SUSPICIOUS], and may also contain other tags.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="mailto:ads@access.ironport.com" target="_self" rel="nofollow noopener noreferrer"&gt;ads@access.ironport.com&lt;/A&gt; -&amp;nbsp;Untagged subject, but you consider it to be or contain marketing content.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="mailto:not_ads@access.ironport.com" target="_self" rel="nofollow noopener noreferrer"&gt;not_ads@access.ironport.com&lt;/A&gt; -&amp;nbsp;Subject is prepended with [MARKETING], but you do not consider it marketing.&lt;/LI&gt;
&lt;LI&gt;&lt;A class="jive-link-email-small" href="mailto:phish@access.ironport.com" rel="nofollow noopener noreferrer"&gt;phish@access.ironport.com&lt;/A&gt;&amp;nbsp;-&amp;nbsp;&lt;SPAN&gt;Untagged subject, but it appears to be a phishing (designed to acquire usernames, passwords, credit card info, or other personally identifiable information), or contains malware attachments&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;For full info:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/117822-qanda-esa-00.html" target="_blank"&gt;ESA FAQ: How to submit email messages to Cisco&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;-Robert&lt;/P&gt;</description>
      <pubDate>Fri, 07 Apr 2017 13:38:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076853#M15742</guid>
      <dc:creator>Robert Sherwin</dc:creator>
      <dc:date>2017-04-07T13:38:30Z</dc:date>
    </item>
    <item>
      <title>make sure you have enabled</title>
      <link>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076854#M15743</link>
      <description>&lt;P&gt;make sure you have enabled AMP file Analysis and selected all file types for file analysis&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Apr 2017 15:41:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076854#M15743</guid>
      <dc:creator>Venkatesh Attuluri</dc:creator>
      <dc:date>2017-04-12T15:41:08Z</dc:date>
    </item>
    <item>
      <title>In Incoming Mail Policy, we</title>
      <link>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076855#M15744</link>
      <description>&lt;P style="padding-left: 30px;"&gt;In Incoming Mail Policy, we recommend enabling Antivirus, AMP and Outbreak Filtering. In Outbreak filtering policy make sure to have Message Modification feature enabled with URL Rewrite so suspicious emails are tagged to warn end users about these emails. As long as the threat level is about 3 (default) it should trigger the tagging to warn users.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2017 14:02:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/email-security/scaning-for-phishing-in-an-attachment/m-p/3076855#M15744</guid>
      <dc:creator>Sriram Subramanian</dc:creator>
      <dc:date>2017-04-21T14:02:46Z</dc:date>
    </item>
  </channel>
</rss>

