Generating alerts

Occasional Contributor

Hi all,


We've starting rolling out EMS5 to our users, and have deployed the ATP Sensor on our dc's. The daily reports are working as expected but we have yet to see an alert. I've tried the FAQ trick of running nslookup againest the DC but no joy. Anyone got an ways to trigger an alert within AATP?


Oh AATP has been running for about 5 days.

12 Replies



The easiest way to generate an alert is to do DNS recon against the Domain Controller - which is protected by the AATP Sensor.


let me know if you require more information.




Are there any health alerts on the portal? if yes, what are they?

Hey Itay,


We have no errors in the workspace. I can see the senors are checking i believe there is no communication issue. I can also see the reports are getting updated with current information.


I've tried a very basic nslooking recon process...with no joy. If you are able to provide a method that will trigger something happy to have a look at it.

I got a high priority alert after setting up AATP when I used this command: mstsc /v computername /remoteguard


My intention was to connect to another computer (where I have admin privileges) by remote desktop, but without exposing my credentials to that computer. AATP really got worried about me skating on my Kerberos ticket like that. 

What happened? did it alert on Pass The Ticket claiming the ticket was stolen from your source computer to the remote host?

Yes, that's exactly what happened. I decided to stop using mstsc with /remoteguard rather than generate false positives, or disable meaningful alerts.

Thanks for letting me know, we will check if we can spot that as false positive...

(although technically you might say it's a benign true) 

Hi Joe, John,


It is a FP/B-TP that is caused by remote credential guard.


Using remote credential guard the RDP client copies its original TGT to the RDP server so the user can use this TGT for requesting other TGS’s. The new TGS’s seems like PTT because their TGT parent created from the RDP client.


It is n our backlog to exclude this case and not trigger PTT.


Regarding the DNS recon - are you trying it against a DNS server which is on a DC that is covered by a Sensor?




Hey All, finally got an alert. Turns out if you send 12+ authenication requests from a single server within 10 get an ldap bind alert.


Tried simulating the sensitive group alert but did not get any alert when adding users to domain admins etc... The actions are shown if searched the user from top right corner search bar but it does not alert in the timeline.
Why is that?

Hi @Mtee- ,


Suspicious modifications of sensitive groups requires learning period of 4 weeks per DC.

The detection relies on events audited on domain controllers. Make sure your domain controllers are auditing the events needed.


Do you see any data in the Modification to sensitive groups report?





Thank you for the reply. Apparently my issue is that 4 week learning period.
Created AATP instance a week ago so that is the reason.