<?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: Enabling Netflow on cloud-based Wireless Controllers in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/enabling-netflow-on-cloud-based-wireless-controllers/m-p/4950101#M1105420</link>
    <description>&lt;P&gt;When enabling Netflow on a cloud-based wireless controller, you typically send the Netflow data to a Netflow collector. Here's a simple explanation:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;You can use an on-premise Netflow collector, and in this case, the Netflow traffic is not encrypted by default. If your Netflow collector is in a private network, you may need to configure NAT to translate the Netflow collector's public IP to its private IP for the traffic to reach it.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Alternatively, you can use a cloud-based Netflow collector, such as one hosted in Azure. In this scenario, the Netflow data would be sent to the cloud-based collector directly, and you wouldn't need to worry about NAT or encrypting the traffic because it remains in the cloud environment.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The choice between on-premise and cloud-based Netflow collectors depends on your specific network architecture and security requirements.&lt;/P&gt;</description>
    <pubDate>Sat, 28 Oct 2023 22:23:25 GMT</pubDate>
    <dc:creator>yasodasanjel</dc:creator>
    <dc:date>2023-10-28T22:23:25Z</dc:date>
    <item>
      <title>Enabling Netflow on cloud-based Wireless Controllers</title>
      <link>https://community.cisco.com/t5/network-security/enabling-netflow-on-cloud-based-wireless-controllers/m-p/4950099#M1105419</link>
      <description>&lt;P&gt;Hey everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just wondering if anyone knows where to send the Netflow collector on a cloud-based wireless controller (such as Meraki for example). Would we send it to an on-premise Netflow collector? If it is on-premise, would the Netflow be encrypted and NAT is required to NAT the netflow collector IP from public to the private IP?&amp;nbsp; Or would the netflow collect be in the cloud too (i.e., in Azure)?&amp;nbsp; Just wondering how this would work.&lt;/P&gt;
&lt;P&gt;I'm working a project to evaluate different cloud-based wireless controllers and just curios how and where the netflow traffic would be configured.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you in advance!&lt;/P&gt;</description>
      <pubDate>Sat, 28 Oct 2023 22:21:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-netflow-on-cloud-based-wireless-controllers/m-p/4950099#M1105419</guid>
      <dc:creator>latenaite2011</dc:creator>
      <dc:date>2023-10-28T22:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling Netflow on cloud-based Wireless Controllers</title>
      <link>https://community.cisco.com/t5/network-security/enabling-netflow-on-cloud-based-wireless-controllers/m-p/4950101#M1105420</link>
      <description>&lt;P&gt;When enabling Netflow on a cloud-based wireless controller, you typically send the Netflow data to a Netflow collector. Here's a simple explanation:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;You can use an on-premise Netflow collector, and in this case, the Netflow traffic is not encrypted by default. If your Netflow collector is in a private network, you may need to configure NAT to translate the Netflow collector's public IP to its private IP for the traffic to reach it.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Alternatively, you can use a cloud-based Netflow collector, such as one hosted in Azure. In this scenario, the Netflow data would be sent to the cloud-based collector directly, and you wouldn't need to worry about NAT or encrypting the traffic because it remains in the cloud environment.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The choice between on-premise and cloud-based Netflow collectors depends on your specific network architecture and security requirements.&lt;/P&gt;</description>
      <pubDate>Sat, 28 Oct 2023 22:23:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-netflow-on-cloud-based-wireless-controllers/m-p/4950101#M1105420</guid>
      <dc:creator>yasodasanjel</dc:creator>
      <dc:date>2023-10-28T22:23:25Z</dc:date>
    </item>
    <item>
      <title>Re: Enabling Netflow on cloud-based Wireless Controllers</title>
      <link>https://community.cisco.com/t5/network-security/enabling-netflow-on-cloud-based-wireless-controllers/m-p/4950113#M1105421</link>
      <description>Thank you Yosadanjel for the explanation.&lt;BR /&gt;&lt;BR /&gt;Follow up questions.&lt;BR /&gt;&lt;BR /&gt;Say in the case of Meraki or Junipr Mist cloud controller for example, if&lt;BR /&gt;we send it on-premise, it probably wouldn't be good to send netflow data to&lt;BR /&gt;the Netflow collector on-premise as traffic would not be encrypted and&lt;BR /&gt;anything can sniff the Netflow data, even with NAT enable.&lt;BR /&gt;&lt;BR /&gt;In the case of sending the Netflow collector in the cloud, how can one send&lt;BR /&gt;the traffic to the Netflow collector in Azure for a sample. How does&lt;BR /&gt;Meraki's controller (via the Dashboard) or Juniper Mist controller via&lt;BR /&gt;their own dashboard be able to talk to the Netflow collect via the Azure's&lt;BR /&gt;IP address?&lt;BR /&gt;&lt;BR /&gt;Thank you!&lt;BR /&gt;</description>
      <pubDate>Sun, 29 Oct 2023 00:36:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/enabling-netflow-on-cloud-based-wireless-controllers/m-p/4950113#M1105421</guid>
      <dc:creator>latenaite2011</dc:creator>
      <dc:date>2023-10-29T00:36:17Z</dc:date>
    </item>
  </channel>
</rss>

