Forum Discussion
1.7.575.57477 lots of "Reconnaissance using directory service enumeration"
Hi,
As you mentioned this is a known issue with ATA 1.7.
In some cases this suspicious activity can be caused by legitimate security solutions running on endpoints and servers. With ATA 1.7 Update 1 we've introduced the ability to disable this detection in order to stop generating these alerts. However it requires an additional manual step after deploying ATA 1.7 Update 1, which is decsribed at https://support.microsoft.com/en-us/help/3191777/description-of-update-1-for-microsoft-advanced-threat-analytics-v1.7We're further adding clustering and other elemets to the detection logic in the upcoming release of ATA to improve the detection itself and automatically address this scenario.
Hope this helps!
Michael.
Hi,
As you mentioned this is a known issue with ATA 1.7.
In some cases this suspicious activity can be caused by legitimate security solutions running on endpoints and servers. With ATA 1.7 Update 1 we've introduced the ability to disable this detection in order to stop generating these alerts. However it requires an additional manual step after deploying ATA 1.7 Update 1, which is decsribed at https://support.microsoft.com/en-us/help/3191777/description-of-update-1-for-microsoft-advanced-threat-analytics-v1.7
We're further adding clustering and other elemets to the detection logic in the upcoming release of ATA to improve the detection itself and automatically address this scenario.
Hope this helps!
Michael.
Hello,
We have been receiving alerts for directory service enumeration and I was wondering if those were triggered from legitimate security solutions. When you refer to legitimate security solutions are you talking about tools for administration? Is there a reason for any other program to do directory service enumeration to pull all domain users?
Andreas
Hi,
I'm familiar with a scenario where security scanners trigger these alerts but not admin tools.
However - there could be a 3rd party tool which (for some reason) decided to use this specific RPC call.
HTH.
BTW - In v.next we're adding a learning mechanism to avoid these exact scenarios.
I genuinely haven't had time to track down what is causing the query/call to be performed.
i'm hoping its probably something stupid like an address book plugin
