<?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 Best Idea I can think of is in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-and-winscp-how-to-get-files-off-sfr-module/m-p/2860729#M1030568</link>
    <description>&lt;P&gt;Best Idea I can think of is using Firesight abilities to SCP.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 02 Jun 2016 01:18:05 GMT</pubDate>
    <dc:creator>evan.chadwick1</dc:creator>
    <dc:date>2016-06-02T01:18:05Z</dc:date>
    <item>
      <title>Firepower and WINscp - how to get files off SFR module</title>
      <link>https://community.cisco.com/t5/network-security/firepower-and-winscp-how-to-get-files-off-sfr-module/m-p/2860728#M1030566</link>
      <description>&lt;P&gt;Anyone able to use WINscp to get a file off a sourcefire module?&amp;nbsp;I'm thinking&amp;nbsp;WINscp has issues with the admin user not entering into expert mode by default.&lt;/P&gt;
&lt;P&gt;I have a windows environment and can not get the scp secure-copy command to work from SFR to a windows server with port 22 open.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 13:01:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-and-winscp-how-to-get-files-off-sfr-module/m-p/2860728#M1030566</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2019-03-12T13:01:57Z</dc:date>
    </item>
    <item>
      <title>Best Idea I can think of is</title>
      <link>https://community.cisco.com/t5/network-security/firepower-and-winscp-how-to-get-files-off-sfr-module/m-p/2860729#M1030568</link>
      <description>&lt;P&gt;Best Idea I can think of is using Firesight abilities to SCP.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2016 01:18:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-and-winscp-how-to-get-files-off-sfr-module/m-p/2860729#M1030568</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2016-06-02T01:18:05Z</dc:date>
    </item>
    <item>
      <title>You are right. sourcefire</title>
      <link>https://community.cisco.com/t5/network-security/firepower-and-winscp-how-to-get-files-off-sfr-module/m-p/2860730#M1030570</link>
      <description>&lt;P&gt;You are right. sourcefire module/sensor does not act as SCP server so you can't use winSC to connect to it. But it does act as SCP client so you can use either firesight or any other SCP server and copy the files to scp server first and then using winscp to get them out.&lt;/P&gt;
&lt;P&gt;Example.&lt;/P&gt;
&lt;P&gt;&amp;gt;expert&lt;/P&gt;
&lt;P&gt;&amp;gt;sudo scp /var/common/file-to-be-copied admin@Firesight-IP:/var/tmp&lt;/P&gt;
&lt;P&gt;This will copy the file to /var/tmp directory in firesight. You can use any other SCP server as well.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rate if helps.&lt;/P&gt;
&lt;P&gt;Yogesh&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2016 07:30:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-and-winscp-how-to-get-files-off-sfr-module/m-p/2860730#M1030570</guid>
      <dc:creator>yogdhanu</dc:creator>
      <dc:date>2016-06-02T07:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: You are right. sourcefire</title>
      <link>https://community.cisco.com/t5/network-security/firepower-and-winscp-how-to-get-files-off-sfr-module/m-p/3928711#M1030572</link>
      <description>&lt;P&gt;Thanks you for this&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2019 15:49:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-and-winscp-how-to-get-files-off-sfr-module/m-p/3928711#M1030572</guid>
      <dc:creator>mmccrack3n</dc:creator>
      <dc:date>2019-09-23T15:49:03Z</dc:date>
    </item>
  </channel>
</rss>

