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

ImpossibleTravelQuery.yaml #11151

Closed
wants to merge 1 commit into from

Conversation

InspiraEnterprise
Copy link

Impossible-Travel-Custom-Query
ANALYZING ANOMALOUS SIGN-IN ACTIVITIES WITH KUSTO QUERY LANGUAGE (KQL)

Description
Impossible Travel Kusto Query Language (KQL) script is designed to analyze sign-in logs to detect potential anomalous activity by calculating the speed of travel between login locations. It filters out logs at excessively high speeds, which may indicate suspicious behavior.

Business Requirements
• Identify Potential Compromises: Detect anomalous user sign-ins that may indicate an account compromise, such as logins from geographically distant locations within an unfeasibly short time frame.

• Enhance Incident Response: Provide security teams with actionable insights to quickly investigate and respond to potential threats. Detecting impossible travel can help in initiating prompt investigations into compromised accounts.

• Mitigate Insider and External Threats: Protect against both internal (e.g., account misuse) and external threats (e.g., credential theft) by flagging suspicious activities that could indicate unauthorized access to corporate resources.

Prerequisites
• An active Azure subscription

• Sentinel Contributor RBAC role assigned to a resource group

• An active Sentinel workspace

• A Log Analytics workspace linked to Sentinel

• Azure Active Directory (Azure AD) Sign-In Logs.

• Adequate log retention policies must be in place to store sign-in data for a period sufficient to perform meaningful analysis.

• Determine appropriate threshold values for travel distance (in kilometers) and timeframe (in hours) based on the organization’s risk tolerance and normal user behavior.

MITRE ATT&CK
The following are the MITRE ATT&CK tactics and techniques associated with the analytical rule:

Initial Access

• T1078 - Valid Accounts

If an account is used from multiple geographically distant locations in a short period, it may indicate that an adversary has obtained valid credentials and is using them from a different location.

Command and Control

• T1071 - Application Layer Protocol

Adversaries might use remote access tools that leverage common application layer protocols to hide their activities, which could be indicated by logins from unusual locations.

Defense Evasion

• T1036 – Masquerading

An adversary might use techniques to make their activity appear normal, such as using VPNs or proxies to mimic legitimate user access patterns, which could involve impossible travel scenarios.

Query Scheduling
• Query Frequency: - Run query every 6 hours

• Query Lookup data: - Lookup data from the last 24 hours.

Change(s):
Created first version

Reason for Change(s):
Uploaded the first version

Testing Completed:
Yes, this workbook is tested successfully and requires the Syslog data connector to be connected.

Checked that the validations are passing and have addressed any issues that are present:
Yes

@v-prasadboke
Copy link
Contributor

Hello @InspiraEnterprise, Please package the solution using V3 tool and add the required missing files

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

Successfully merging this pull request may close these issues.

3 participants