Azure secure score block legacy authentication

Back


Id	C27BB559-28C5-4924-A7DA-3BF04CD02C8F
Rulename	Azure secure score block legacy authentication
Description	This query searches for most compromising sign-in attempts come from legacy authentication. Older office clients such as Office 2010 do not support modern authentication and use legacy protocols such as IMAP, SMTP, and POP3. Legacy authentication does not support multi-factor authentication (MFA). Even if an MFA policy is configured in your environment, bad actors can bypass these enforcements through legacy protocols.
Severity	High
Tactics	CredentialAccess
Techniques	T1212 T1556
Required data connectors	SenservaPro
Kind	Scheduled
Query frequency	6h
Query period	6h
Trigger threshold	0
Trigger operator	gt
Source Uri	https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/SenservaPro/Analytic Rules/BlockLegacyAuthentication.yaml
Version	1.0.1
Arm template	C27BB559-28C5-4924-A7DA-3BF04CD02C8F.json

KQL

SenservaPro_CL
| where ControlName_s == 'AzureSecureScoreBlockLegacyAuthentication'

YAML

severity: High
queryPeriod: 6h
name: Azure secure score block legacy authentication
OriginalUri: https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/SenservaPro/Analytic Rules/BlockLegacyAuthentication.yaml
entityMappings:
- fieldMappings:
  - columnName: ControlName_s
    identifier: Name
  - columnName: TenantId
    identifier: AadTenantId
  - columnName: TenantDisplayName_s
    identifier: DisplayName
  entityType: Account
- fieldMappings:
  - columnName: Group_s
    identifier: DistinguishedName
  entityType: SecurityGroup
- fieldMappings:
  - columnName: SourceSystem
    identifier: ResourceId
  entityType: AzureResource
version: 1.0.1
relevantTechniques:
- T1212
- T1556
status: Available
id: C27BB559-28C5-4924-A7DA-3BF04CD02C8F
queryFrequency: 6h
triggerThreshold: 0
triggerOperator: gt
query: |
  SenservaPro_CL
  | where ControlName_s == 'AzureSecureScoreBlockLegacyAuthentication'  
description: |
  'This query searches for most compromising sign-in attempts come from legacy authentication. 
   Older office clients such as Office 2010 do not support modern authentication and use legacy protocols such as IMAP, SMTP, and POP3. 
   Legacy authentication does not support multi-factor authentication (MFA).
   Even if an MFA policy is configured in your environment, bad actors can bypass these enforcements through legacy protocols.'  
requiredDataConnectors:
- connectorId: SenservaPro
  dataTypes:
  - SenservaPro_CL
tactics:
- CredentialAccess
kind: Scheduled

ARM