Independent VLANs: commonly used or occasionally used?

This article mainly introduces how to use an independent VLAN. In this article, the author introduces several standards to help you determine when to use an independent VLAN. I hope this article will help you.

You can set up a firewall in front of a vro or set up a firewall in front of the system. Either method requires an IPSec rule or an operating system firewall (such as a Windows Firewall ). Another way to protect the security zone is to directly establish a completely independent VLAN.

From the perspective of network switching, a completely independent VLAN basically belongs to Layer 2 (L2) connection and does not connect to other TCP/IP networks through the router. This completely independent network requires dedicated interfaces and switching devices, but in many cases, this means that the cost is improved and the number of required ports is hard to meet. When to use fully isolated L2 VLANs, I found some representative solutions in my actual work, which can indeed protect independent VLANs.

The most common use case is that an independent system with multiple ports can be used for security zones related to an independent VLAN. Of course, if a system is connected to multiple security zones, risks may occur and related problems may occur. Therefore, the most important thing is that there should be no bridging or routing between these systems, otherwise all efforts will be wasted.

Frankly speaking, if each role in the system only uses a specified port, the entire system will apply to most environments. Common applications in independent security zones protect data security during Virtual Machine migration. For installing VMware, this application shows how to protect unencrypted data during Virtual Machine migration. In addition, there are other common applications that are basically used to prevent man-in-the-middle attacks. Next we will face the problem of routing the L2 network to other large network environments.