01-17-2024 01:27 PM - edited 01-17-2024 01:34 PM
Dears
i have a huge campus for 40 no's of building connected with fiber to distribution switches of each buidling and Distribution switches of each building connecting to the enterprise core switch by OSPF, i m introducing a campus firewall so all the vlans interface will move from Distribution switches to the firewall as an default gateway and from firewall there will be a OSPF peering with enterprise core , i have 3 question that i need expert advise, whether i m on a correct path ?
Thanks
01-17-2024 01:55 PM
@adamgibs7 I would probably put the CCTV cameras in a separate VRF and routed via a separate interface on the Firewall. I would leave the default gateway for the VLANs on the switches and just route all egress traffic to DC via the Firewall, therefore not have the Firewall performing intervlan routing. If you want to perform filtering between VLANs, then TrustSec SGTs would be the better solution to use and this can also restrict lateral movement in the same VLAN that the firewall cannot.
01-17-2024 10:57 PM - edited 01-18-2024 12:17 AM
Dear Rob
I would probably put the CCTV cameras in a separate VRF and routed via a separate interface on the Firewall.
But in this case still i need to have a bigger hardware of firewall , and what i understand is NVR server Default Gateway will be on campus firewall as an separate interface and all cameras will send the traffic to NVR, access switches will be the same as if currently ( user and camera traffic ) but there will be a separate trunk link from dist SW to campus fw for the camera's creating vlan sub interface on the camera vrf interfaces.
if u look from the security aspect the user traffic must be filtered becz one small piece of code on the user pc and overwhelm the Disti sw ( default gateway) , so that's the reason i want to keep the Default gateway on the firewall, trust sec with cisco ISE will be a tremendous job for IT to manage.
01-17-2024 02:22 PM
it hard task
CCTV use multicast and making FW inspect all these multicast is not optimal solution
but we can make control traffic inspect by FW and making data traffic bypass
anyway I will check other point and update you
MHM
01-18-2024 02:37 AM
I agree, TrustSec could have some implications if you have virtual environment that doesn't support SGTs or if you need to propagate the tags into ACI. Based on my experience, the CCTV devices should definitely be isolated from the network, and they should only be allowed to talk to the NVR, and potentially to the vendor public portal(s) to download updates. For the latter, we usually configure the specific IP addresses of the portals alongside the ports and protocols.
In some cases I'd seen the NVRs have multiple interfaces, one in the VLAN where the CCTV reside, and another in the normal data VLAN. In that case when the CCTV devices need to talk to the NVR they don't have to traverse any VLAN as the NVR interface that would be used by them will be in the same VLAN.
I personally would go with your design moving all the inter-VLAN routing to be managed by the firewall, where you can apply security restrictions on the traffic passing through, but even if you don't want to restrict the traffic between the VLANs you can still have visibility of what traffic is passing between the VLANs.
01-18-2024 06:21 AM
Putting all gateways on the firewall is almost always a bad idea that solves problems better left to other methods.That's my advice as a guy who had been doing firewalls for 30 years.
As others have mentioned, VRFs and possibly Trustsec SGTs solve this in a more scalable and elegant way.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide