--- title: "Virtual Sensors and VM-Aware ports" slug: "virtual-sensors-and-vm-aware-ports" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-10-05T15:39:58Z published: 2026-10-05T15:39:58Z canonical: "docs.trellix.com/virtual-sensors-and-vm-aware-ports" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Virtual Sensors and VM-Aware ports The VM-Aware feature is available with Virtual Sensors as well. Regardless of whether you use an M-series Sensor or a Virtual Sensor, the configurations and functionality are similar for this feature except for the following difference. > [!NOTE] > Note > > NS-series Sensors do not support this feature. - In case of M-series Sensors, the port that you want to configure as VM-Aware must be a SPAN port and its interface type can only be dedicated. - In case of M-series Sensors, the Manager can integrate with one of the following to quarantine attacking VMs: In case of Virtual Sensors, the Manager can collaborate only with VMware vCenter and VMware vShield. - VMware vCenter and VMware vShield - Reflex Virtualization Management Center (VMC) and Reflex vTrust - In case of Virtual Sensors, you can configure a SPAN port or an inline port-pair as VM-Aware. You can even configure a sub-interface (VLAN or CIDR) of a SPAN or inline port as a VM-Aware port. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-F025C101-C24F-455B-A938-51530B41FD1D-low.png?sv=2026-02-06&spr=https&st=2026-11-22T16%3A09%3A20Z&se=2026-11-22T17%3A09%3A20Z&sr=c&sp=r&sig=DCWdKYJscjR6YiyGqIRnvu0K7pND%2FnQxX5RkVl1ihWk%3D) Though it is possible for you configure a monitoring port of a Virtual Sensor as a VM-Aware port, these two are distinct entities. | Virtual Sensors | VM-Aware ports | | --- | --- | | These are virtual instance of the Sensor software, which you install on a virtual host such as VMware ESX server. | You can configure the following as VM-Aware ports: - Physical monitoring ports of physical M-series Sensors. - Monitoring ports of Virtual Sensors. | | You can deploy the monitoring ports in inline or SPAN mode. | In case of M-series Sensors, these monitoring ports must be in SPAN mode. Therefore, only intrusion detection is possible. In case of Virtual Sensors, you can deploy a SPAN port or an inline port-pair as VM-Aware. | | You can use Virtual Sensors to monitor traffic from VMs as well as from physical machines. | These ports are exclusively for traffic from VMs. | | These are virtualized next-generation IPS. Therefore, almost all of the features supported by a physical Sensor are provided. This includes DoS attack prevention, Firewall policies (including application identification and visualization), Advanced Malware policies, Connection Limiting policies, and so on. | These ports implement only the applied exploit and recon policies. | | All response actions supported by a physical Sensor are supported. | The Sensor response actions applicable to a SPAN port are supported in case of M-series. The main one being manual quarantine of an attacking VM from Attack Log. | | No integration with any third-party product is required for normal functioning. | To quarantine attacking VMs, the Manager must be integrated with one of the following third-party products: - VMware vCenter and VMware vShield - Reflex Virtualization Management Center (VMC) and Reflex vTrust | | Virtual Sensors respond just like their physical counterparts. | The Sensor is not involved in quarantining the host. The Manager collaborates with one of the third-party products to quarantine the host. So, it involves re-configuring the third-party product accordingly. | | You can create sub-interfaces based on VLAN and CIDRs. The process of creating, configuring, and managing sub-interfaces are the same as in the case of physical ports. | In case of M-series Sensors, no virtualization of a VM-Aware SPAN port is possible. That is, you cannot define sub-interfaces for this port. This is possible in case of Virtual Sensors. |