Pseudo-microsegmentation with /29s and /30s in Legacy Environment?

I'm currently in a small environment with a single site, about 30 VMs, and 40 users, with a relatively flat network - just 4-5 subnets all open to each other, plus 2 DMZs which are more locked down.

​

Primarily a cisco shop with a pair of routers and a dozen switches. We also have Palo Altos which are only used for inline IDS but could be used for routing. Mass equipment upgrades are not an option for us, though we do incrementally upgrade a piece or two each year. I realize this is a big handcuff when discussing nearly-rebuilding a network from scratch, but it's what I've got.

​

I've been recently considering ways to lock down the network to provide better segmentation and security on a network-level, which is more difficult without a lot of the newer features on equipment.

​

I know something needs to change, but I'm not sure how to best implement without buying a ton of new tech. Without readdressing, all we'd be able to do would be firewall our server subnets from our client subnets. A start, but not great.

​

Security groups have allowed us to use this microsegmentation for our AWS applications, but the on-premises network is wide open once you breach the border. I'd like to implement a similar microsegmentation, or at least something close to it, on premises.

​

I've considered putting applications or servers in their own vlan with a /29 or /30 network - or larger where needed, and then routing everything (aside from the obvious like VM storage traffic). Similarly, adding users to department based subnets, allowing more granular access control. This would allow all ACLs to be enforced at a router level, with a default deny-all, only whitelisting specific ports between these small subnets, each subnet being an application, or at least a piece of one.

​

Is this a crazy idea? Has anyone ever implemented anything like this? What should I watch out for?

Posted May 21, 2019, 3:29 AM UTC · edited

49
copasjCCNP•

If you are trying to limit traffic between servers, you might be able to use PVLANS if your current gear supports it. That isn't really perfect if your apps are l2 adjacent to your SQL server. Cisco also has the ability to do L2 ACL's that might be helpful, but your config will be kinda of cluttered and unusual, that effects time to resolution.

Re-IP'ing and keeping Web Frontends, Apps, and Data on different subnets is probably the right answer.

3
[deleted]•

[deleted]

1
systemdadOP•

Awesome, I think I will do this. I'll also check into PVLAN.

​

I agree, L2 ACLs aren't what I'm wanting to get into.

1
Tronaldo46•

It works fine in a smaller environment to segment servers like you suggested. We are also doing that in an environment with a few hundred VMs. Just make sure you have the workflow to create a new server or at least a server VLAN automated so it doesn’t become too hard to maintain all the different VLANs.

For the client side you might be good by using Windows firewall on the Windows clients for isolation as usually there won’t be many requirements for peer to peer communication, so the Windows firewall config can be quite static.

Non Windows devices you can then keep on their own isolates VLANs per device type and maybe further segmented based on security zones.

2
packetthriller•

Yes, the old school dmz architecture is probably what you're thinking of. Your Palo could be put in routed mode or you can continue to use it in layer 2 mode if you move the downstream gateway for your vlans to the downstream router. I haven't seen many deployments like that in the wild though.

Another consideration is that if you do either way with your Palo, you will be increasing the amount of traffic traversing it by a factor of many. Not sure what your hardware looks like, but plan throughput accordingly.

1
systemdadOP•

good point on the capacity planning - I'll keep that in mind!

1
ZPrimedCerts? I don't need no stinking certs•

What model PAs do you have and how much traffic do you need to flow to the servers?

PAs can do per-user identification against a directory (primarily done with Windows/AD but they may have options for other things too)... you could very easily use the PAs + firewall rules to restrict traffic on a per-user basis regardless of what device they're using... and without screwing around with subnetting or changing IPs at all.

0
systemdadOP•

How would that help server-to-server or client-to-client segmentation? Stuff doesn't hit the gateway if it's in the same subnet.

1
ZPrimedCerts? I don't need no stinking certs•

I was assuming (you said 4-5 subnets) that servers and clients were separated in different VLANs / subnets.

If that isn't already the case, that's something you should consider doing... And will be less work than individual /29 or /30 all over the place.

It wouldn't help server-to-server or client-to-client though and I missed that originally 😛

Both of those are relatively easy with firewall rules on the machines though. With Windows it's all GPO... Pretty basic.

2
systemdadOP•

yes, the servers are in a different subnet than clients...but that doesn't help server to server traffic (the entire point of microsegementation).

1