<?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: Bank's Security Team asks about Identify... in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/bank-s-security-team-asks-about-identify/m-p/34193#M1304</link>
    <description>Hi Ilia , as I remember , those ports are used by controller (some of them can be disabled) :&lt;BR /&gt;
- ssh (22) - for the ssh&lt;BR /&gt;
- https (5825) - for the GUI management&lt;BR /&gt;
- 13910/13907 - for AP registration . That can be changed to 4500 (typical GRE port) for the IPSec registration&lt;BR /&gt;
- 161 - snmp - for security you need to change it to snmpV3&lt;BR /&gt;
&lt;BR /&gt;
- all encryption types (WEP/WPA/WPA2 PSK and ENT) are all standard based , not a proprietary. For now we do not support PPSK (which can be considered proprietary).&lt;BR /&gt;
- CAPWAP tunnel - we do not use this standard , insted we are using our proprietary tunnel type (WASSP) . That can be used for both AP registration/management as well as user traffic (data plane) if traffic goes back to the controller. &lt;BR /&gt;
- RADIUS communication between controller and RADIUS server is used as everybody else using it - with MD5 (shared secret), which is not very secure . But that is the standard for now , and so far I never seen any other RADIUS server which would support something different.</description>
    <pubDate>Thu, 26 Oct 2017 02:19:00 GMT</pubDate>
    <dc:creator>Ostrovsky__Yury</dc:creator>
    <dc:date>2017-10-26T02:19:00Z</dc:date>
    <item>
      <title>Bank's Security Team asks about Identify...</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/bank-s-security-team-asks-about-identify/m-p/34191#M1302</link>
      <description>Hello, everybody,&lt;BR /&gt;
&lt;BR /&gt;
what could I aswer to security guys:&lt;BR /&gt;
&lt;BR /&gt;
They've asked:&lt;BR /&gt;
&lt;BR /&gt;
- list of opened port at V2110 by default;&lt;BR /&gt;
- does V2110 have standard (RFC) realisation of WEP, WPA and WPA2 or there is something vendor-specific?&lt;BR /&gt;
- how CAPWAP tunnel between V2110 and AP works and what kind of encryption does it provide? Does Identify use RFC CAPWA or something vendor-specific?&lt;BR /&gt;
- how safe RADIUS (Active Directory over NPS) authorization? Is there any encryption?&lt;BR /&gt;
&lt;BR /&gt;
Many thanks in advance for your comments,&lt;BR /&gt;
&lt;BR /&gt;
Ilya&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 26 Oct 2017 01:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/bank-s-security-team-asks-about-identify/m-p/34191#M1302</guid>
      <dc:creator>Ilya_Semenov</dc:creator>
      <dc:date>2017-10-26T01:56:00Z</dc:date>
    </item>
    <item>
      <title>RE: Bank's Security Team asks about Identify...</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/bank-s-security-team-asks-about-identify/m-p/34192#M1303</link>
      <description>1) Ports&lt;BR /&gt;
are listed in the release notes page#43&lt;BR /&gt;
&lt;A href="http://documentation.extremenetworks.com/release_notes/extremewireless/9035197_ExtremeWireless_v10.41.01.0080_RelNotes.pdf" target="_blank" rel="nofollow noreferrer noopener"&gt;http://documentation.extremenetworks.com/release_notes/extremewireless/9035197_ExtremeWireless_v10.4...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
2) 802.11&lt;BR /&gt;
yes that is per standard or clients wouldn't be able to connect&lt;BR /&gt;
&lt;BR /&gt;
3) CAPWAP&lt;BR /&gt;
As per the datasheet "Pre-standard (CAPWAP)"&lt;BR /&gt;
&lt;A href="http://bit.ly/2kP8vjG" target="_blank" rel="nofollow noreferrer noopener"&gt;http://bit.ly/2kP8vjG&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
4) RADIUS&lt;BR /&gt;
as per RFC&lt;BR /&gt;
&lt;A href="https://tools.ietf.org/html/rfc6614" target="_blank" rel="nofollow noreferrer noopener"&gt;https://tools.ietf.org/html/rfc6614&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 26 Oct 2017 02:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/bank-s-security-team-asks-about-identify/m-p/34192#M1303</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-10-26T02:13:00Z</dc:date>
    </item>
    <item>
      <title>RE: Bank's Security Team asks about Identify...</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/bank-s-security-team-asks-about-identify/m-p/34193#M1304</link>
      <description>Hi Ilia , as I remember , those ports are used by controller (some of them can be disabled) :&lt;BR /&gt;
- ssh (22) - for the ssh&lt;BR /&gt;
- https (5825) - for the GUI management&lt;BR /&gt;
- 13910/13907 - for AP registration . That can be changed to 4500 (typical GRE port) for the IPSec registration&lt;BR /&gt;
- 161 - snmp - for security you need to change it to snmpV3&lt;BR /&gt;
&lt;BR /&gt;
- all encryption types (WEP/WPA/WPA2 PSK and ENT) are all standard based , not a proprietary. For now we do not support PPSK (which can be considered proprietary).&lt;BR /&gt;
- CAPWAP tunnel - we do not use this standard , insted we are using our proprietary tunnel type (WASSP) . That can be used for both AP registration/management as well as user traffic (data plane) if traffic goes back to the controller. &lt;BR /&gt;
- RADIUS communication between controller and RADIUS server is used as everybody else using it - with MD5 (shared secret), which is not very secure . But that is the standard for now , and so far I never seen any other RADIUS server which would support something different.</description>
      <pubDate>Thu, 26 Oct 2017 02:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/bank-s-security-team-asks-about-identify/m-p/34193#M1304</guid>
      <dc:creator>Ostrovsky__Yury</dc:creator>
      <dc:date>2017-10-26T02:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Bank's Security Team asks about Identify...</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/bank-s-security-team-asks-about-identify/m-p/34194#M1305</link>
      <description>Thanks, gentlemen!</description>
      <pubDate>Thu, 26 Oct 2017 13:02:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/bank-s-security-team-asks-about-identify/m-p/34194#M1305</guid>
      <dc:creator>Ilya_Semenov</dc:creator>
      <dc:date>2017-10-26T13:02:00Z</dc:date>
    </item>
  </channel>
</rss>

