Loading

Azure Firewall Logs

Version 1.23.0 (View all)
Compatible Kibana version(s) 8.15.1 or higher
9.0.0 or higher
Supported Serverless project types
What's this?
Security
Observability
Subscription level
What's this?
Basic

Azure Firewall Logs are records of events such as network and application rules that occur within your Azure Firewalls. They provide visibility and can be used to troubleshoot issues related to access, conectivity or performance.

Supported log categories:

Log Category Description Destination Table
AzureFirewallApplicationRule These logs capture information about the traffic that is allowed or denied by application rules configured in Azure Firewall. Azure diagnostics
AzureFirewallNetworkRule These logs capture information about the traffic that is allowed or denied by network rules configured in Azure Firewall. Azure diagnostics
AzureFirewallDnsProxy These logs capture information about DNS requests and responses that are processed by Azure Firewall's DNS proxy. Azure diagnostics
AZFWApplicationRule These logs capture resource specific information about the traffic that is allowed or denied by application rules configured in Azure Firewall. Resource specific
AZFWNetworkRule These logs capture resource specific information about the traffic that is allowed or denied by network rules configured in Azure Firewall. Resource specific
AZFWNatRule These logs capture resource specific information about all DNAT (Destination Network Address Translation) events log data. Resource specific
AZFWDnsQuery These logs capture resource specific information about DNS requests and responses that are processed by Azure Firewall's DNS proxy. Resource specific

For detailed information and instructions on how to migrate to Resource-specific mode, please refer to the following Microsoft documentation: Azure Monitor Resource Logs.

All Azure services will eventually use the resource-specific mode. As part of this transition, some resources allow you to select a mode in the diagnostic setting. Specify resource-specific mode for any new diagnostic settings because this mode makes the data easier to manage.

Refer to the Azure Logs page for more information about setting up and using this integration.

eventhub : string An Event Hub is a fully managed, real-time data ingestion service. Elastic recommends using only letters, numbers, and the hyphen (-) character for Event Hub names to maximize compatibility. You can use existing Event Hubs having underscores (_) in the Event Hub name; in this case, the integration will replace underscores with hyphens (-) when it uses the Event Hub name to create dependent Azure resources behind the scenes (e.g., the storage account container to store Event Hub consumer offsets). Elastic also recommends using a separate event hub for each log type as the field mappings of each log type differ. Default value insights-operational-logs.

consumer_group : string The publish/subscribe mechanism of Event Hubs is enabled through consumer groups. A consumer group is a view (state, position, or offset) of an entire event hub. Consumer groups enable multiple consuming applications to each have a separate view of the event stream, and to read the stream independently at their own pace and with their own offsets. Default value: $Default

connection_string : string The connection string is required to communicate with Event Hubs, see steps here.

A Blob Storage account is required in order to store/retrieve/update the offset or state of the eventhub messages. This means that after stopping the Azure logs package it can start back up at the spot that it stopped processing messages.

storage_account : string The name of the storage account where the state/offsets will be stored and updated.

storage_account_key : string The storage account key, this key will be used to authorize access to data in your storage account.

storage_account_container : string The storage account container where the integration stores the checkpoint data for the consumer group. It is an advanced option to use with extreme care. You MUST use a dedicated storage account container for each Azure log type (activity, sign-in, audit logs, and others). DO NOT REUSE the same container name for more than one Azure log type. See Container Names for details on naming rules from Microsoft. The integration generates a default container name if not specified.

resource_manager_endpoint : string Optional, by default we are using the azure public environment, to override, users can provide a specific resource manager endpoint in order to use a different azure environment.

Resource manager endpoints:

# Azure ChinaCloud
https://management.chinacloudapi.cn/

# Azure GermanCloud
https://management.microsoftazure.de/

# Azure PublicCloud 
https://management.azure.com/

# Azure USGovernmentCloud
https://management.usgovcloudapi.net/

The firewall_logs data stream of the Azure Logs package will collect any firewall log events that have been streamed through an Azure event hub.

ECS Field Reference

Please refer to the following document for detailed information on ECS fields.