Microsoft Sentinel Analytic Rules
cloudbrothers.infoAzure Sentinel RepoToggle Dark/Light/Auto modeToggle Dark/Light/Auto modeToggle Dark/Light/Auto modeBack to homepage

Insider Risk_Sensitive Data Access Outside Organizational Geo-location

Back
Idb81ed294-28cf-48c3-bac8-ac60dcef293b
RulenameInsider Risk_Sensitive Data Access Outside Organizational Geo-location
DescriptionThis alert joins Azure Information Protection Logs (InformationProtectionLogs_CL) with Microsoft Entra ID Sign in Logs (SigninLogs) to provide a correlation of sensitive data access by geo-location. Results include User Principal Name, Label Name, Activity, City, State, Country/Region, and Time Generated. Recommended configuration is to include (or exclude) Sign in geo-locations (City, State, Country and/or Region) for trusted organizational locations. There is an option for configuration of correlations against Microsoft Sentinel watchlists. Accessing sensitive data from a new or unauthorized geo-location warrants further review. For more information see Sign-in logs in Microsoft Entra ID: Location Filtering
SeverityHigh
TacticsExfiltration
TechniquesT1567
Required data connectorsAzureActiveDirectory
AzureInformationProtection
KindScheduled
Query frequency6h
Query period6h
Trigger threshold0
Trigger operatorgt
Source Urihttps://github.com/Azure/Azure-Sentinel/blob/master/Solutions/MicrosoftPurviewInsiderRiskManagement/Analytic Rules/InsiderRiskSensitiveDataAccessOutsideOrgGeo.yaml
Version1.1.3
Arm templateb81ed294-28cf-48c3-bac8-ac60dcef293b.json
Deploy To Azure
InformationProtectionLogs_CL
| extend UserPrincipalName = UserId_s
| where LabelName_s <> ""
| join kind=inner (SigninLogs) on UserPrincipalName
| extend City = tostring(LocationDetails.city)
// | where City <> "New York" // Configure Location Details within Organizational Requirements
| extend State = tostring(LocationDetails.state)
// | where State <> "Texas" // Configure Location Details within Organizational Requirements
| extend Country_Region = tostring(LocationDetails.countryOrRegion)
// | where Country_Region <> "US" // Configure Location Details within Organizational Requirements
// | lookup kind=inner _GetWatchlist('<Your Watchlist Name>') on $left.UserPrincipalName == $right.SearchKey
| summarize count() by UserPrincipalName, LabelName_s, Activity_s, City, State, Country_Region, TimeGenerated
| sort by count_ desc
| extend AccountName = tostring(split(UserPrincipalName, "@")[0]), AccountUPNSuffix = tostring(split(UserPrincipalName, "@")[1])
triggerThreshold: 0
queryFrequency: 6h
id: b81ed294-28cf-48c3-bac8-ac60dcef293b
eventGroupingSettings:
  aggregationKind: SingleAlert
description: |
    'This alert joins Azure Information Protection Logs (InformationProtectionLogs_CL) with Microsoft Entra ID Sign in Logs (SigninLogs) to provide a correlation of sensitive data access by geo-location. Results include User Principal Name, Label Name, Activity, City, State, Country/Region, and Time Generated. Recommended configuration is to include (or exclude) Sign in geo-locations (City, State, Country and/or Region) for trusted organizational locations. There is an option for configuration of correlations against Microsoft Sentinel watchlists. Accessing sensitive data from a new or unauthorized geo-location warrants further review. For more information see [Sign-in logs in Microsoft Entra ID: Location Filtering](https://docs.microsoft.com/azure/active-directory/reports-monitoring/concept-sign-ins)'
entityMappings:
- entityType: Account
  fieldMappings:
  - identifier: FullName
    columnName: UserPrincipalName
  - identifier: Name
    columnName: AccountName
  - identifier: UPNSuffix
    columnName: AccountUPNSuffix
incidentConfiguration:
  createIncident: true
  groupingConfiguration:
    groupByEntities:
    - Account
    matchingMethod: Selected
    enabled: true
    lookbackDuration: 3d
    reopenClosedIncident: true
kind: Scheduled
queryPeriod: 6h
OriginalUri: https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/MicrosoftPurviewInsiderRiskManagement/Analytic Rules/InsiderRiskSensitiveDataAccessOutsideOrgGeo.yaml
query: |
  InformationProtectionLogs_CL
  | extend UserPrincipalName = UserId_s
  | where LabelName_s <> ""
  | join kind=inner (SigninLogs) on UserPrincipalName
  | extend City = tostring(LocationDetails.city)
  // | where City <> "New York" // Configure Location Details within Organizational Requirements
  | extend State = tostring(LocationDetails.state)
  // | where State <> "Texas" // Configure Location Details within Organizational Requirements
  | extend Country_Region = tostring(LocationDetails.countryOrRegion)
  // | where Country_Region <> "US" // Configure Location Details within Organizational Requirements
  // | lookup kind=inner _GetWatchlist('<Your Watchlist Name>') on $left.UserPrincipalName == $right.SearchKey
  | summarize count() by UserPrincipalName, LabelName_s, Activity_s, City, State, Country_Region, TimeGenerated
  | sort by count_ desc
  | extend AccountName = tostring(split(UserPrincipalName, "@")[0]), AccountUPNSuffix = tostring(split(UserPrincipalName, "@")[1])  
requiredDataConnectors:
- connectorId: AzureInformationProtection
  dataTypes:
  - InformationProtectionLogs_CL
- connectorId: AzureActiveDirectory
  dataTypes:
  - SigninLogs
severity: High
name: Insider Risk_Sensitive Data Access Outside Organizational Geo-location
tactics:
- Exfiltration
version: 1.1.3
triggerOperator: gt
relevantTechniques:
- T1567