PH_Rule_ES_IMPORT_AZURE_22
Enabled
Detects Azure infrastructure discovery
3
Security
Discovery
Discovery consists of techniques an adversary may use to gain knowledge about the system and internal network. These techniques help adversaries observe the environment and orient themselves before deciding how to act. They also allow adversaries to explore what they can control and what’s around their entry point in order to discover how it could benefit their current objective. Native operating system tools are often used toward this post-compromise information-gathering objective.
https://attack.mitre.org/tactics/TA0007T1580
Cloud Infrastructure Discovery
An adversary may attempt to discover resources that are available within an infrastructure-as-a-service (IaaS) environment. This includes compute service resources such as instances, virtual machines, and snapshots as well as resources of other services including the storage and database services. An adversary may enumerate resources using a compromised user's access keys to determine which are available to that user. The discovery of these available resources may help adversaries determine their next steps in the Cloud environment, such as establishing Persistence. This technique focuses on the discovery of components of the provided services rather than the services themselves.
https://attack.mitre.org/techniques/T1580Server
MS Azure via Azure Event Hub (AZURE_PYTHON_SDK)
Correlation
No remediation guidance specified
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
300 seconds
If the following defined pattern/s occur within a 300 second time window.
Filter
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType IN ("Microsoft-Azure-ClassicNetwork-reservedIps-read","Microsoft-Azure-Network-publicIPAddresses-read","Microsoft-Azure-Network-virtualNetworks-read","Microsoft-Azure-Resources-subscriptions-resourceGroups-read")
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
user
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.
The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern
user = Filter.user