Query: Sigma rule for Detects usage of the "Import-Module" cmdlet to load the "Microsoft.ActiveDirectory.Management.dl" DLL. Which is often us
Matching passage: Sigma rule: Detects usage of the "Import-Module" cmdlet to load the "Microsoft.ActiveDirectory.Management.dl" DLL. Which is often us. Logsource: windows / ps_script. Rule: title: Potential Active Directory Enumeration Using AD Module - PsScript id: 9e620995-f2d8-4630-8430-4afd89f77604 related: - id: 70bc5215-526f-4477-963c-a47a5c9ebd12 type: similar - id: 74176142-4684-4d8a-8b0a-713257e7df8e type: similar status: test description: Detects usage of the "Import-Module" cmdlet to load the "Microsoft.ActiveDirectory.Management.dl" DLL. Which is often used by attackers to perform AD enumeration. references: - https://github.com/samratashok/ADModule - https://twitter.com/cyb3rops/status/1617108657166061568?s=20 - https://www.ired.team/offensive-security-experiments/active-directory-kerberos-abuse/active-directory-enumeration-with-ad-module-without-rsat-or-admin-privileges author: frack113, Nasreddine Bencherchali date: 2023-01-22 tags: - attack.reconnaissance - attack.discovery - attack.impact logsource: product: windows category: ps_script definition: 'Requirements: Script Block Logging must be enable' detection: selection_generic: ScriptBlockText|contains|all: - 'Import-Module ' - Microsoft.ActiveDirectory.Management.dll selection_specific: ScriptBlockText|contains: ipmo Microsoft.ActiveDirectory.Management.dll condition: 1 of selection_* falsepositives: - Legitimate use of the library for administrative activity level: medium
Near-miss passage: Sigma rule: This detection uses Windows security events to detect suspicious access attempts to the registry key values and sub-keys. Logsource: windows / security. Rule: title: Azure AD Health Service Agents Registry Keys Access id: 1d2ab8ac-1a01-423b-9c39-001510eae8e8 status: test description: 'This detection uses Windows security events to detect suspicious access attempts to the registry key values and sub-keys of Azure AD Health service agents (e.g AD FS). Information from AD Health service agents can be used to potentially abuse some of the features provided by those services in the cloud (e.g. Federation). This detection requires an access control entry (ACE) on the system access control list (SACL) of the following securable object: HKLM:\SOFTWARE\Microsoft\ADHealthAgent. Make sure you set the SACL to propagate to its sub-keys. ' references: - https://o365blog.com/post/hybridhealthagent/ - https://github.com/OTRF/Set-AuditRule/blob/c3dec5443414231714d850565d364ca73475ade5/rules/registry/aad_connect_health_service_agent.yml author: Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research), MSTIC date: 2021-08-26 modified: 2022-10-09 tags: - attack.discovery - attack.t1012 logsource: product: windows service: security detection: selection: EventID: - 4656 - 4663 ObjectType: Key ObjectName: \REGISTRY\MACHINE\SOFTWARE\Microsoft\ADHealthAgent filter: ProcessName|contains: - Microsoft.Identity.Health.Adfs.DiagnosticsAgent.exe - Microsoft.Identity.Health.Adfs.InsightsService.exe - Microsoft.Identity.Health.Adfs.MonitoringAgent.Startup.exe - Microsoft.Identity.Health.Adfs.PshSurrogate.exe - Microsoft.Identity.Health.Common.Clients.ResourceMonitor.exe condition: selection and not filter falsepositives: - Unknown level: medium