Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AAD SignIns Insights #210

Open
piaudonn opened this issue Jan 22, 2022 · 4 comments
Open

AAD SignIns Insights #210

piaudonn opened this issue Jan 22, 2022 · 4 comments
Assignees
Labels
new module New automation module

Comments

@piaudonn
Copy link
Collaborator

I wonder if there would be an interest for such a module. It's essentially a similar concept of what we have for analysts in the entity page available for automation and a bit of what we have in UEBA.

Takes a user and return stats such as:

  • Last successful logon data (timestamp + other metadata)
  • Last failed logon data
  • Usual user-agent-string data
  • Usual contries/IPs

If there is a cloud-logon-session present in the entities (case of an AAD Protection alert), return all the info about this particular login.

That last one maybe could be added to the AAD Risk Module instead.

@piaudonn piaudonn added new module New automation module pending-triage Submitted issue needing triage labels Jan 22, 2022
@briandelmsft
Copy link
Owner

I like the idea, would this be a new module or perhaps an extension to the capabilities of the AAD Risks? It may make it too complex though if we add it... not sure off hand.

One issue, the cloud-logon-session is not passed from the incident trigger so you have to go back into SecurityAlerts to get it.... this is one of the reasons for #205 so you can use the KQL module to lookup the incident easily and work from there

@piaudonn
Copy link
Collaborator Author

piaudonn commented Feb 8, 2022

Maybe also return a table of last successfull access per app?

@briandelmsft briandelmsft removed the pending-triage Submitted issue needing triage label Feb 15, 2022
@briandelmsft
Copy link
Owner

possibilities to include:

  • Conditional access failures (and the policies that failed)
  • Named locations the user has been seen from
  • Device join status of the signins
  • password resets or other interesting admin actions on account

@piaudonn
Copy link
Collaborator Author

  • insights about signin hours

(although we would need to define what baseline could be used to determine out of character behaviors)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new module New automation module
Projects
None yet
Development

No branches or pull requests

2 participants