Azure vSensor
Deploy and pair Vectra vSensors in Microsoft Azure environments.
Please see attachment on the right for the full document!
Introduction
This document describes the pre-requisites, specifications, and steps required to deploy a Vectra NDR (formerly Detect for Network) Virtual Sensor (vSensor) in an Azure subscription to monitor cloud Infrastructure-as-a-Service workloads. These Sensors can be paired with Brains of any type.
Azure Sensors can be deployed in configurations that support up to 1 Gbps or 2 Gbps of network throughput per Sensor. The input to the Sensor can be from any VxLAN-based 3rd party packet broker or the Microsoft virtual network tap (VTAP) when it becomes available.
Azure Sensors can be used in both Respond UX and Quadrant UX deployments. For more detail on Respond UX vs Quadrant UX please see Vectra Analyst User Experiences (Respond vs Quadrant). One of the below guides should be the starting point for your overall Vectra deployment:
Either of the above guides cover basic firewall rules needed for the overall deployment and initial platform settings. Virtual Sensor (VMware, Hyper-V, KVM, AWS, Amazon, and GCP) configuration and pairing and covered in their respective guides. Physical appliance pairing is covered in the Vectra Physical Appliance Pairing Guide. Please see the Vectra Product Documentation Index on the Vectra support site for additional documentation including deployment guides for CDR for M365 / Azure AD and CDR for AWS.
Contains
Deployment from Azure Marketplace
Cloud Sensor Registration Token
Forwarding Traffic to Azure vSensors
Pairing Azure Virtual Sensors (vSensors)
Additional Guidance for Normal Pairing
Pairing Guidance for Special Situations
Host ID Extraction (Azure External Connector Integration)
Configuration Example
Viewing and Modifying Virtual Networks Considered by the Connector
Traffic Validation
Worldwide Support Contact Information
Attachments
Last updated
Was this helpful?