<?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: NTP Master problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ntp-master-problem/m-p/3212016#M905426</link>
    <description>exactly dear, &lt;BR /&gt;&lt;BR /&gt;please note that it's coreSW  Catalyst 6807 &lt;BR /&gt;&lt;BR /&gt;how can i solve this issue?</description>
    <pubDate>Tue, 07 Nov 2017 07:11:37 GMT</pubDate>
    <dc:creator>mohamed.ali</dc:creator>
    <dc:date>2017-11-07T07:11:37Z</dc:date>
    <item>
      <title>NTP Master problem</title>
      <link>https://community.cisco.com/t5/network-security/ntp-master-problem/m-p/3211809#M905420</link>
      <description>&lt;P&gt;Dears plz i want your support to this issue&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;=: An NTP control (mode 6) message with the UNSETTRAP (31) opcode with an unknown association identifier will cause NTP to respond with two packets -- one error response packet indicating that the association identifier was invalid followed by another nonerror, largely empty response. Because the number of packets sent as the response is greater than the single packet request, this can be used to conduct a DRDoS attack using vulnerable NTP servers as the unwitting third parties.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Apply a restrict option to all hosts that are not authorized to perform NTP queries. For example, to deny query requests from all clients, put the following in the NTP configuration file, typically /etc/ntp.conf, and restart the NTP service:&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:39:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-master-problem/m-p/3211809#M905420</guid>
      <dc:creator>mohamed.ali</dc:creator>
      <dc:date>2020-02-21T14:39:31Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Master problem</title>
      <link>https://community.cisco.com/t5/network-security/ntp-master-problem/m-p/3211922#M905422</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/413705"&gt;@mohamed.ali&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;Which device we are talking about? Switch, router, firewall, etc?&lt;/P&gt;
&lt;P&gt;Looks like someone ran an audit tool and asked you to fix this right?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-If I helped you somehow, please, rate it as useful.-&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2017 01:19:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-master-problem/m-p/3211922#M905422</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2017-11-07T01:19:50Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Master problem</title>
      <link>https://community.cisco.com/t5/network-security/ntp-master-problem/m-p/3212016#M905426</link>
      <description>exactly dear, &lt;BR /&gt;&lt;BR /&gt;please note that it's coreSW  Catalyst 6807 &lt;BR /&gt;&lt;BR /&gt;how can i solve this issue?</description>
      <pubDate>Tue, 07 Nov 2017 07:11:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-master-problem/m-p/3212016#M905426</guid>
      <dc:creator>mohamed.ali</dc:creator>
      <dc:date>2017-11-07T07:11:37Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Master problem</title>
      <link>https://community.cisco.com/t5/network-security/ntp-master-problem/m-p/3213558#M905430</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Are you using the switch as ntp master? if so, then you will need to restrict who can query that switch.Create an access-list with addresses that are allowed to query time and apply to ntp access-group serve-only e.g.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;access-list 10 permit 192.168.10.0 0.0.0.255&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ntp access-group serve-only 10&lt;/P&gt;
&lt;P&gt;&amp;nbsp;you can then create an access-list with deny any and apply it using the ntp access-group serve and&amp;nbsp;&lt;SPAN&gt;ntp access-group query-only.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;configure you ntp servers and you can use ntp access-group peer to restrict the address your switch will get time from.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;thanks&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;John&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2017 00:38:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-master-problem/m-p/3213558#M905430</guid>
      <dc:creator>johnd2310</dc:creator>
      <dc:date>2017-11-09T00:38:09Z</dc:date>
    </item>
  </channel>
</rss>

