Virtual LECS brings the same internal visibility capability and advanced traffic detection to virtualized environments, without physical appliances.
Virtual LECS is the ideal choice when you want to bring LECS security to virtualized environments by leveraging the infrastructure you already have.
It reduces installation time and complexity, standardizes deployment across multiple sites, and makes logs and telemetry already usable for SOC, SIEM, and incident response processes.
Designed for VMware, Hyper-V and Proxmox environments.
Leverage the resources already available in your data center and match CPU, RAM and storage to the actual load.
Virtual LECS grows with your environment, maintaining a scalable and replicable approach.
It collects and organizes traffic data in a way that is useful for monitoring, analysis, and incident response.
The result is concrete internal visibility, ready to be integrated into existing security processes.
You can choose centralized management in the Cloud or an On-Premise mode with local dashboard via HTTPS, also suitable for contexts with restrictive policies, critical segmentations.
No host configuration changes, no interruption of active services.
It imports the Virtual LECS package into the chosen hypervisor and prepares the instance in the environment to be monitored.
Configures a network for management and two dedicated interfaces for mirrored traffic, according to the planned architecture.
Set up connectivity via DHCP or static IP and perform the necessary reachability tests.
Frequently asked questions about LECS technology in virtualized version
Virtual LECS is designed for VMware, Hyper-V, and Proxmox environments so that it can be deployed consistently across different virtualized infrastructures.
Not necessarily. On-Premise management with local dashboard via HTTPS is also available. However, for some essential services such as updates and licensing, an outbound connection to LECS servers is required, consistent with corporate network policies.
Sizing depends on the volume of traffic and the number of hosts. The correct principle is not to stop at the minimum necessary, but to provide an adequate margin to ensure continuity, performance and scalability.
The solution uses two dedicated interfaces for mirroring traffic analysis, keeping the management network separate from the flow observation component.