Designing Defensible Networks

NetCraftsmen®

It’s not enough for a network just to get packets from here to there. Networks, in some sense, bear some responsibility for the epidemic of cybercrime: networks have enabled instant global connectivity, but they have also allowed instant global threats to come into your home or workplace. Networks need to be designed so that they enhance overall security, rather than contribute to the problem.

It is simply a fact of life that operating systems and applications will always have flaws that can be exploited by malicious actors. Software is getting more complex, straining the abilities of us humans to comprehend it. The rate of new software vulnerabilities discovered each month is not going down, it is increasing. If you’re hoping for the day when operating systems and applications are bug-free, forget it. We live in a world of vulnerable software and increasing connectivity, and your systems will always be exposed to potential attackers. The fact is, your networks will get attacked, and your users will be compromised.

So we, as network engineers, need to do more. I don’t mean add more firewalls or IDSs or other “security” devices, although they’re certainly helpful. We need to design networks that actively defend against network attacks. It’s been said many times before, but this design principle bears repeating: networks need to be designed with security in mind, and not as just an afterthought. Most networks are designed for performance, redundancy and administrative ease. Security is one of the last qualities to be considered, and it is almost always applied piecemeal – without a consistent plan.

You have all heard of and probably have even used the phrase “hard and crunchy on the outside, soft and chewy on the inside,” to describe the security posture of many networks. The candy metaphor may be a bit overused, but it is still accurate because it describes how network security is often applied: to the edges of the network only, leaving the internal network components subject to attack (soft and chewy). Remember, if an attacker is able to compromise one workstation on the internal network, he essentially becomes an “internal” hacker, and all your edge defenses are for naught. To build an effective secure network, security has to be included in all points of the network, by enforcing security policy throughout the network, not just at the edges.

How does a secure network defend against attacks? Richard Beijtlich has some useful blogs on this subject. Principally, in two ways:

  1. By limiting what can be attacked, improving the odds of detecting attacks, and it facilitating the containment and eradication of compromises.
  2. By providing information that can indicate that an attack took place (or is taking place). By providing evidence of network activities and events (or, just as importantly, their absence). In other words, by providing useful forensic information so that attacks can be detected.

I should emphasize that a secure network will not stop all attacks from succeeding. Given enough time and motivation, an attacker will eventually compromise your systems. However, a secure network design assumes that attacks will take place — even that some will (initially) succeed — and plans accordingly.

The first step in building a secure network is what I call “compartmentalization.” It refers to the idea of logically separating the network into sections, or “compartments,” where access policy can be enforced and attempted violations of that policy can be detected.

A good analogy for this is a fire door. You probably have fire doors spread throughout your place of work. Consider what a fire door does. A fire door does not prevent fires. But when a fire occurs, a fire door slows the fire’s spread. It gives you time to detect the fire, and it gives you time to respond. Similarly, a compartmentalized network does not prevent attacks, but it slows down attackers, making it harder to compromise more systems, and also makes it easier to detect the attacks taking place.

The first step in compartmentalizing a network is understanding the components and the subsystems, how they interact with other devices on the network and what kinds of traffic they use (and should not use). Here are some examples of components:

  1. General user workstations.
  2. General purpose servers (file/print, database, web, etc.).
  3. Servers with restricted access, such as financial systems, HR systems, etc.
  4. IP telephony servers.
  5. IP-based security systems (cameras, badge readers, recording equipment, motion sensors, etc.).
  6. Wireless guest networks.

This is not an exhaustive list – you may have additional categories. The point is to understand the different types of devices and their differing security needs – each of the categories above will have different access policies.

The next step is to separate the devices in each of these categories from devices in other categories. By “separate,” I mean create layer 3 boundaries between, say, printers and workstations. The easiest way to do this is to create VLANs for each category. Place your workstations in one VLAN, printers in another, IP phones in a third, and so on. In a large network you will have many VLANs for each category. As an example, each floor of a building may have a VLAN for user workstations, a VLAN for IP telephones, a VLAN for printers, etc.

This strategy greatly increases the number on VLANs and therefore, the number of IP subnets in your network. So, we should talk briefly about your IP addressing plan because it also plays an important part of your network security. A well thought out addressing plan can contribute to security by facilitating the creation of ACLs to enforce security policies. It does this by grouping categories of devices into summarizable address blocks. For example, if you allocate the following subnets to workstations:

172.24.0.0/24

172.24.1.0/24

172.24.2.0/24

172.24.3.0/24

:
:

172.24.15.0/24

You can summarize all these subnets as 172.24.0.0/20, and use that summary to make creating and applying ACLs much easier. Without summarization, it becomes difficult to create ACLs to control policy. They become long and difficult to manage. They may even affect network performance. Long ACLs may not be able to be processed in switching hardware and instead may require use of the CPU (often called process switching), which drastically reduces network performance.

So, for each of your device categories, allocate a block of addresses that you can summarize. In the example above, we’ve allocated 172.24.0.0/20 to workstations. You might allocate 172.24.16.0/20 to IP Phones, 172.24.32.0/20 to printers, etc. Each subnet within the /20 block can be used in a different closet or floor, yet you can refer to them all in an ACL by using the summary address.

In my next post, I will show how to develop an effective access policy for different groups of devices and how that contributes to a more secure network.

Leave a Reply

 

Nick Kelly

Cybersecurity Engineer, Cisco

Nick has over 20 years of experience in Security Operations and Security Sales. He is an avid student of cybersecurity and regularly engages with the Infosec community at events like BSides, RVASec, Derbycon and more. The son of an FBI forensics director, Nick holds a B.S. in Criminal Justice and is one of Cisco’s Fire Jumper Elite members. When he’s not working, he writes cyberpunk and punches aliens on his Playstation.

 

Virgilio “BONG” dela Cruz Jr.

CCDP, CCNA V, CCNP, Cisco IPS Express Security for AM/EE
Field Solutions Architect, Tech Data

Virgilio “Bong” has sixteen years of professional experience in IT industry from academe, technical and customer support, pre-sales, post sales, project management, training and enablement. He has worked in Cisco Technical Assistance Center (TAC) as a member of the WAN and LAN Switching team. Bong now works for Tech Data as the Field Solutions Architect with a focus on Cisco Security and holds a few Cisco certifications including Fire Jumper Elite.

 

John Cavanaugh

CCIE #1066, CCDE #20070002, CCAr
Chief Technology Officer, Practice Lead Security Services, NetCraftsmen

John is our CTO and the practice lead for a talented team of consultants focused on designing and delivering scalable and secure infrastructure solutions to customers across multiple industry verticals and technologies. Previously he has held several positions including Executive Director/Chief Architect for Global Network Services at JPMorgan Chase. In that capacity, he led a team managing network architecture and services.  Prior to his role at JPMorgan Chase, John was a Distinguished Engineer at Cisco working across a number of verticals including Higher Education, Finance, Retail, Government, and Health Care.

He is an expert in working with groups to identify business needs, and align technology strategies to enable business strategies, building in agility and scalability to allow for future changes. John is experienced in the architecture and design of highly available, secure, network infrastructure and data centers, and has worked on projects worldwide. He has worked in both the business and regulatory environments for the design and deployment of complex IT infrastructures.