Loading

Azure Network Watcher VNet

<div class="condensed-table">
| | |
| --- | --- |
| Version | 1.2.1 (View all) |
| Compatible Kibana version(s) | 8.13.0 or higher |
| Supported Serverless project types
What’s this? | Security
Observability |
| Subscription level
What’s this? | Basic |
| Level of support
What’s this? | Elastic |

</div>
VNet flow logs in Azure Network Watcher track IP traffic in virtual networks, sending data to Azure Storage for analysis. Unlike NSG flow logs, VNet flow logs offer enhanced monitoring capabilities. They are crucial for understanding network activity, identifying connections, and monitoring open ports. Flow logs serve as the primary source for optimizing resources, ensuring compliance, and detecting intrusions in cloud environments, catering to both startups and enterprises.

This integration supports ingestion of logs from Azure Network Watcher VNet, via Azure Blob Storage input.

  • Log is used to retrieve VNet Flow data. See more details in the documentation here.

Elastic Agent must be installed. For more details and installation instructions, please refer to the Elastic Agent Installation Guide.

There are several options for installing and managing Elastic Agent:

With this approach, you install Elastic Agent and use Fleet in Kibana to define, configure, and manage your agents in a central location. We recommend using Fleet management because it makes the management and upgrade of your agents considerably easier.

With this approach, you install Elastic Agent and manually configure the agent locally on the system where it’s installed. You are responsible for managing and upgrading the agents. This approach is reserved for advanced users only.

You can run Elastic Agent inside a container, either with Fleet Server or standalone. Docker images for all versions of Elastic Agent are available from the Elastic Docker registry, and we provide deployment manifests for running on Kubernetes.

Please note, there are minimum requirements for running Elastic Agent. For more information, refer to the Elastic Agent Minimum Requirements.

  1. In the Azure portal, go to your storage account.
  2. Under Security + networking, Click On Access keys. Your account access keys appear, as well as the complete connection string for each key.
  3. Click On Show keys to show your access keys and connection strings and to enable buttons to copy the values.
  4. Under key1, find the Key value. Click On the Copy button to copy the account key. Same way you can copy the storage account name shown above keys.
  5. Go to Containers under Data storage in your storage account to copy the container name.
Note

Enable virtual network flow logs using the steps provided in reference.

  1. In Kibana navigate to Management > Integrations.

  2. In "Search for integrations" top bar, search for Azure Network Watcher VNet.

  3. Select the "Azure Network Watcher VNet" integration from the search results.

  4. Select "Add Azure Network Watcher VNet" to add the integration.

  5. While adding the integration, to collect logs via Azure Blob Storage, keep Collect VNet logs via Azure Blob Storage toggle on and then configure following parameters:

    • account name
    • containers
    • service account key/service account uri
  6. Save the integration.

This is the Log dataset.