Skip to content
This repository was archived by the owner on Nov 16, 2023. It is now read-only.

5 queries for account compromise detection #27

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

adrwh
Copy link

@adrwh adrwh commented Jan 27, 2019

Please see 5 common queries for contribution.

  • Recent security alerts

Return triggered security alerts in the last 24 hours.

  • Signins by username

Return signin activity by username from the Azure SigninLogs table/log.

  • Signins by ip

Return signin activity by one or more ip address from the Azure SigninLogs table/log.

  • Office365 activity by username

Return activity from the Office365 unified audit log by username.

  • Office365 activity by ip

Return activity from the Office365 unified audit log by one or more ip addresses.

Use case

I usually start with Recent security alerts, look for obvious anomalous behaviour. Then i copy the unfamiliar IPs and run Signins by ip and look at the activity for that IP. I compare it with Signins by username. Then i run Office365 activity by ip to see what activity was done by this IP/user and usually this is enough to confirm compromise or not.

@msftclas
Copy link

msftclas commented Jan 27, 2019

CLA assistant check
All CLA requirements met.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants