<?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 Re: Blocking macro-enabled Office files (docm, xlsm, etc) in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/102673#M44583</link>
    <description>&lt;P&gt;You can also block id 39154 which is Microsoft Office File with Macros. Please note that this isn't a perfect signature by far, but it does manage to take care of a good percentage of files before they hit our Barracudas&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 12 Aug 2016 17:15:39 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2016-08-12T17:15:39Z</dc:date>
    <item>
      <title>Blocking macro-enabled Office files (docm, xlsm, etc)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/102467#M44565</link>
      <description>&lt;P&gt;The available file types that can be filtered doesn't include Office documents with macros (docm, xlsm, etc).&amp;nbsp; These are being used now to sneak garbage into the network.&amp;nbsp; Is there a way to ID them or are they on the horizon for inclusion in the file blocking filters?&amp;nbsp; An innovative way that is being used is to create an xlsm file with a malicious macro in it and then replace the xlsm extension with csv.&amp;nbsp; User thinks it's just rows of text and clicks on it, Windows feeds it to Excel, and Excel opens it and runs the macro.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Gene&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2016 23:57:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/102467#M44565</guid>
      <dc:creator>gleduc</dc:creator>
      <dc:date>2016-08-11T23:57:48Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking macro-enabled Office files (docm, xlsm, etc)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/102589#M44578</link>
      <description>&lt;P&gt;Hi Gene&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In fileblocking the firewall is not able to differentiate doc files with or without macros as they are basically the same file type, it will be able to identify doc files 'disguised' as CSV as it looks deeper into the file than merely the extention . You could block doc files altogether, which may be a bit over the top.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Vulnerability protection has an ID for Office files containing Macros as BPry mentions&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2022-07-07 at 09.20.25.png" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/42167i82BB5966FB8F427D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screenshot 2022-07-07 at 09.20.25.png" alt="Screenshot 2022-07-07 at 09.20.25.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 07:23:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/102589#M44578</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2022-07-07T07:23:53Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking macro-enabled Office files (docm, xlsm, etc)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/102599#M44580</link>
      <description>&lt;P&gt;Block macros with GPO.&lt;/P&gt;&lt;P&gt;&lt;A href="https://blogs.technet.microsoft.com/mmpc/2016/03/22/new-feature-in-office-2016-can-block-macros-and-help-prevent-infection/" target="_blank"&gt;https://blogs.technet.microsoft.com/mmpc/2016/03/22/new-feature-in-office-2016-can-block-macros-and-help-prevent-infection/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Aug 2016 14:40:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/102599#M44580</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2016-08-12T14:40:03Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking macro-enabled Office files (docm, xlsm, etc)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/102673#M44583</link>
      <description>&lt;P&gt;You can also block id 39154 which is Microsoft Office File with Macros. Please note that this isn't a perfect signature by far, but it does manage to take care of a good percentage of files before they hit our Barracudas&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Aug 2016 17:15:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/102673#M44583</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2016-08-12T17:15:39Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking macro-enabled Office files (docm, xlsm, etc)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/103620#M44639</link>
      <description>&lt;P&gt;Or Subscribe to Wildfire, it does a pretty bang up job with handling them!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good luck!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-sO&lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2016 20:54:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-macro-enabled-office-files-docm-xlsm-etc/m-p/103620#M44639</guid>
      <dc:creator>steveo</dc:creator>
      <dc:date>2016-08-16T20:54:57Z</dc:date>
    </item>
  </channel>
</rss>

