Hyper-V vSensor

This guide is intended to help customers or partners deploy vSensors in Hyper-V environments and pair them to your Vectra Brain. This includes both Respond UX and Quadrant UX deployments.

Introduction

This guide is intended to help customers or partners deploy vSensors in Hyper-V environments and pair them to your Vectra Brain. It will cover basic background information, connectivity requirements (firewall rules that may be needed in your environment), deployment of the vSensor in Hyper-V, and pairing.

vSensors behave much in the same way that physical Sensors do. One advantage is that there is no cost to deploy a vSensor other than your own costs to provide and maintain the infrastructure they run in. vSensors also allow you to capture and analyze traffic that only exists in the virtual environment. You can even use vSensors in place of physical Sensors to capture physical network traffic.

Hyper-V vSensors 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 guidesarrow-up-right. Physical appliance pairing is covered in the Vectra Physical Appliance Pairing Guide. Please see the Vectra Product Documentation Indexarrow-up-right on the Vectra support site for additional documentation including deployment guides for CDR for M365 / Azure ADarrow-up-right and CDR for AWSarrow-up-right.

Contains

  • About Hyper-V vSensor Images

  • Hyper-V vSensor Requirements and Throughput

  • Connectivity Requirements

  • vSensor Deployment in Hyper-V

    • Requirements

    • Downloading the latest vSensor Hyper-V VHD image

    • Deploying the VHD

  • Capture Configuration Guidance and Virtual Switch Options

    • Capturing physical network traffic coming into the Hyper-V server

    • Capturing virtual network traffic from other guests

    • Capturing traffic that flows over multiple VLANs

    • Additional guidance for virtual switch options in Hyper-V

  • Initial vSensor Configuration at CLI

  • Pairing vSensors

  • Additional Pairing Guidance

  • Traffic Validation

  • Worldwide Support Contact Information

Attachments

Last updated

Was this helpful?