Jan 26 2018 01:50 AM
Jan 26 2018 01:50 AM
Has anyone managed to get anything meaningful from Sensitive Groups ? I thought the intent was to "monitor" those groups for membership changes. I have pushed and pulled users in and out of groups (say, Domain Admins) and I never get notified of anything !
Jan 26 2018 09:25 PM
At least 8 weeks. What actually is the detector learning ? "Normal" modifications by expected admins or other sensitive users ?
Jan 28 2018 01:35 AM
wait for 2-3 more weeks, then to invoke the alert, try to modify a sensitive group using an account that does not normally do it...
Jan 28 2018 06:04 AM
There is a report that will show you all of the sensitive group modifications. Can you run this report and see if it has the modifications you did recently?
Jan 28 2018 09:02 AM
The group in question (as a test) was not one that normally gets modified at all....in fact it has probably not been modified for 12 months, by anyone previously.
Yes, was aware of the report.....and there is NOTHING at all in the report, which actually would be more useful to me than a console alert. Why would it not show in the report ? Yes, auditing for group membership is nabbed, and yes, it shows on the event log.
Jan 28 2018 12:27 PM
Which domain group was it?
Keep in mind that in 1.8.* we are using a closed list of groups defined as sensitive.
in future version you will be able to tag yourself which groups are sensitive for you.
Jan 28 2018 03:37 PM
Jan 28 2018 03:52 PM
Sorry, got confused with another thread.
in AATP, you can tag the entities, so it seems you gap is that you need to have at least 10 weeks of learning period.
Jan 28 2018 03:57 PM
10 weeks of learning, for what exactly ? To say that someone "unusual" has modified the group membership ? If this is 10 weeks to appear in the report, is pretty useless, don't you think ? What would be the point of that ?
Jan 28 2018 04:15 PM
Yes and No.
Unlike ATA which can alert for abnormal modifications, and report on all modifications,
AATP (for now) can alert for abnormal modifications too (with the same 10 weeks learning period), but it's report will only report on previously alerted modifications, and not all of them like in ATA.
So.. if you wait 2 more weeks, and use an account that did not modify the tagged group during the learning period, you should see an alert...
Feb 13 2018 10:43 AM
We've reviewed the sensitive groups report and I'm pleased to let you know that all changes to the sensitive groups will now be included in the report (not just the anomalies). We expect to release the code to enable this in our next update cycle on Sunday February 18th.
Feb 21 2018 01:05 AM
Did this make it in, as it does not seem to be working ?
Add group to entity list
Schedule a report for sensitive groups(daily)
wait a few hours
add some random user to group
await next daily report to show said user was added
Is my expectation correct ?
Feb 21 2018 10:08 AM
Can you make sure that the Group Events are logged?
To turn them on, please do the following:
After that, please do the group changes in the AD. You can make sure the events are created by opening the Event Viewer (Windows Logs -> Security)
Finally, try to download the report.
If it won't work, please PM me your workspace ID (and name) and the time range (UTC) of the group members change.
Feb 25 2018 09:49 PM
The report works fine and Stuart got a report with attached file few days ago.
Few things to clarify regarding the detector (i.e., when the Security Alert will be triggered and will be seen in the Timeline):
Jul 09 2020 01:51 PM
- if the group (i.e. Domain Admins) is modified always by the same account no alert is triggered, if another user modify the group membership I receive the alert. Is this correct?
- The learning period (4 weeks) starts from the first group membership change (add) event after the sensor installation. Is this correct?
- could you explain me better "The admin didn’t make any change to any group on any DC during the last 10 weeks."?
Thanks a lot