<?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: ARP Poisoning Attack in Security e-Series</title>
    <link>https://community.hpe.com/t5/security-e-series/arp-poisoning-attack/m-p/6937781#M864</link>
    <description>&lt;P&gt;Really, if you are in a situation where devices on a broadcast segment are untrusted, you should segregate them using port isolation.&lt;/P&gt;</description>
    <pubDate>Tue, 07 Feb 2017 01:50:33 GMT</pubDate>
    <dc:creator>Vince-Whirlwind</dc:creator>
    <dc:date>2017-02-07T01:50:33Z</dc:date>
    <item>
      <title>ARP Poisoning Attack</title>
      <link>https://community.hpe.com/t5/security-e-series/arp-poisoning-attack/m-p/6937546#M859</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;As you know, ARP poisoning attack is the process of linking an attacker’s MAC address with the IP address of a legitimate user on a local area network using fake ARP messages. As a result, data sent to the host IP address is instead transmitted to the attacker.&lt;/P&gt;&lt;P&gt;I&amp;nbsp;need to protect&amp;nbsp;a network with ARP poisoning attacks. All the servers are using fixed IP adresses (so no DHCP).&lt;/P&gt;&lt;P&gt;Do you have some experience and how you proceed to protect your network ?&lt;/P&gt;&lt;P&gt;A easy solution is to implement static ARP entries but i"m looking for an another solution if you have.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2017 14:29:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/security-e-series/arp-poisoning-attack/m-p/6937546#M859</guid>
      <dc:creator>Thierry1</dc:creator>
      <dc:date>2017-02-06T14:29:03Z</dc:date>
    </item>
    <item>
      <title>Re: ARP Poisoning Attack</title>
      <link>https://community.hpe.com/t5/security-e-series/arp-poisoning-attack/m-p/6937781#M864</link>
      <description>&lt;P&gt;Really, if you are in a situation where devices on a broadcast segment are untrusted, you should segregate them using port isolation.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2017 01:50:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/security-e-series/arp-poisoning-attack/m-p/6937781#M864</guid>
      <dc:creator>Vince-Whirlwind</dc:creator>
      <dc:date>2017-02-07T01:50:33Z</dc:date>
    </item>
    <item>
      <title>Re: ARP Poisoning Attack</title>
      <link>https://community.hpe.com/t5/security-e-series/arp-poisoning-attack/m-p/6937847#M867</link>
      <description>&lt;P&gt;It''s not really untursted devices, but we are in a PCI context and we need to run vulnerability scans. ARP poisoning is part of the scan and we need to protect our environnement&amp;nbsp;against this attack.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2017 07:13:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/security-e-series/arp-poisoning-attack/m-p/6937847#M867</guid>
      <dc:creator>Thierry1</dc:creator>
      <dc:date>2017-02-07T07:13:18Z</dc:date>
    </item>
    <item>
      <title>Re: ARP Poisoning Attack</title>
      <link>https://community.hpe.com/t5/security-e-series/arp-poisoning-attack/m-p/6937999#M869</link>
      <description>&lt;P&gt;Not sure if informations about &lt;STRONG&gt;Dynamic ARP Protection&lt;/STRONG&gt; feature apply entirely - I mean: now, years after the linked article - also to actual Aruba 2920 but &lt;A href="http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c02609533" target="_blank"&gt;this&lt;/A&gt; article would be interesting enough to start with (and so...looking for a similar feature on Aruba 2920 could be the very first thing to do): on &lt;A href="http://h20566.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=5354494&amp;amp;docLocale=en_US&amp;amp;docId=emr_na-c05365159" target="_blank"&gt;HPE ArubaOS-Switch Access Security Guide for WB.16.03&lt;/A&gt; there is a clear reference [*] about Dynamic ARP Protection (page 384), part of "Configuring Advanced Threat Protection" Chapter 17 (among others, also DHCP Snooping, Dynamic IP Lockdown and Instrumentation Monitor, are discussed topics).&lt;/P&gt;&lt;P&gt;[*] I'm quite sure I saw the same feature described in earlier WB.15.18 documentation too.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2017 15:21:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/security-e-series/arp-poisoning-attack/m-p/6937999#M869</guid>
      <dc:creator>parnassus</dc:creator>
      <dc:date>2017-02-07T15:21:51Z</dc:date>
    </item>
  </channel>
</rss>

