<?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 Microsoft Active Directory DCSync Attempt Detection Vulnerabilitiy in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/microsoft-active-directory-dcsync-attempt-detection/m-p/211642#M61737</link>
    <description>&lt;P&gt;Today I got many critical alerts from Palo Alto Firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Threat Type: vulnerability&lt;BR /&gt;Threat Name: Microsoft Active Directory DCSync Attempt Detection&lt;BR /&gt;ID: 54406&lt;BR /&gt;Category: info-leak&lt;BR /&gt;Content Version: AppThreat-8010-4662&lt;BR /&gt;Severity: critical&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone has the same issue? Can somebody share the details of this attack?&lt;/P&gt;</description>
    <pubDate>Wed, 25 Apr 2018 08:28:19 GMT</pubDate>
    <dc:creator>qafcopa</dc:creator>
    <dc:date>2018-04-25T08:28:19Z</dc:date>
    <item>
      <title>Microsoft Active Directory DCSync Attempt Detection Vulnerabilitiy</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/microsoft-active-directory-dcsync-attempt-detection/m-p/211642#M61737</link>
      <description>&lt;P&gt;Today I got many critical alerts from Palo Alto Firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Threat Type: vulnerability&lt;BR /&gt;Threat Name: Microsoft Active Directory DCSync Attempt Detection&lt;BR /&gt;ID: 54406&lt;BR /&gt;Category: info-leak&lt;BR /&gt;Content Version: AppThreat-8010-4662&lt;BR /&gt;Severity: critical&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone has the same issue? Can somebody share the details of this attack?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 08:28:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/microsoft-active-directory-dcsync-attempt-detection/m-p/211642#M61737</guid>
      <dc:creator>qafcopa</dc:creator>
      <dc:date>2018-04-25T08:28:19Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft Active Directory DCSync Attempt Detection Vulnerabilitiy</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/microsoft-active-directory-dcsync-attempt-detection/m-p/211712#M61754</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/29441"&gt;@qafcopa&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;If you log into &lt;A href="https://threatvault.paloaltonetworks.com" target="_blank"&gt;https://threatvault.paloaltonetworks.com&lt;/A&gt; you can search for the the ID number that you were given you can find additional information on this threat. However with this one you don't really need to, as it tells you that it identified a DCSync attempt.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So we know that DCSync uses the standard Domain Controller replication API to pull password data on the DC accounts as long as the attacker can guess the proper credentials to run DCSync.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So here's the two possibilities.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) It was someone internal to your organization that was using the replication API for legitimate work and it isn't something to worry about. You would be able to verify this by identifying the source and destination and simply talking to the owner of the machine in question.&lt;/P&gt;&lt;P&gt;2) This wasn't internal to your organizaiton and came from the outside. You shouldn't have policies that even allow this to take place.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 15:00:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/microsoft-active-directory-dcsync-attempt-detection/m-p/211712#M61754</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-04-25T15:00:22Z</dc:date>
    </item>
  </channel>
</rss>

