3.3 Given a scenario, implement secure network designs. Flashcards
Active/active load balancing
In an active/active high-availability cluster, the load-balanced services perform the same functions at the same time, but with different transactions. As an example, two load-balanced Web servers would respond to different users’ browser requests. The load balancer manages the traffic and requests going to each of the members of the service or device cluster for which it is responsible. This helps provide for efficiency, eliminates delays or latency, and provides for system and data availability if a member of the cluster is unable to fulfill requests or requires maintenance.
Active/passive load balancing
A load balancer contributes to security by providing for high availability. If a server goes down, the load balancer can transparently and immediately provide for availability by transferring network and resource requests to an identically configured backup server.
An active/passive high-availability cluster like this has one server active and the second passive, acting as a failover or backup.
scheduling load balancing
Load balancers may use several different criteria to determine scheduling—that is, which device gets a particular request. A load balancer may base its decisions on network traffic conditions, for example; it may use a turn-based system (otherwise known as a round-robin type of system); or it can send traffic based on available resources on the target systems in more advanced products.
Load Balancing Virtual IP
A load balancer receives traffic for other devices or services via a virtual IP address. All the traffic is sent to a virtual IP address that is hosted on the load balancer, which forwards the relevant traffic to each resource behind it. This address is labeled “virtual” because it only exists for the purpose of routing traffic, and it is assigned to a device that already has a hardware-relevant IP address.
Load Balancing Persistence
A load balancer contributes to security by providing for high availability. If a server goes down, the load balancer can transparently and immediately provide for availability by transferring network and resource requests to an identically configured backup server. This is considered persistence in networking, meaning the network resources are always available.
Network Segmentation
Network segmentation generally means partitioning a single enterprise network into two or more subnetworks using either switches (at Layer 2) or routers (at Layer 3). Layer 2 switches use VLAN capabilities to turn single broadcast domains into multiple broadcast domains.
Virtual local area network (VLAN)
A VLAN doesn’t depend upon the physical layout of the network; it doesn’t matter if the hosts are physically sitting next to each other or are located several buildings apart. A VLAN creates a logical network in which to assign hosts.
Screened Subnet(DMZ)
screened subnet—also known as a demilitarized zone (DMZ)—a LAN, separate from the internal LANs that contain workstations and private servers. The DMZ connects to the Internet via a lightly firewalled router, and an internal network connects to the DMZ via a much more aggressively firewalled router.
East-West Traffic
The network documentation folks have long called the internal server-to-server connection east-west traffic, not because of any geographic necessities, but because the network diagrams tend to show them as horizontal connections.
Extranet
A private TCP/IP network that provides external entities (customers, vendors, etc.) access to their intranet is called an extranet.
Intranet
A network using VLANs or routers that’s essentially a single enterprise network is called an intranet.
Zero Trust
The CompTIA Security+ objectives list Zero Trust under network segmentation. Zero Trust operates on the principle of “never trust, always verify,” which means exclude any traffic from anyone until you can prove that traffic is legitimate. Zero Trust uses network segmentation as some of the methods for excluding traffic.
Virtual Private Network(VPN)
A virtual private network (VPN) uses the public Internet as a direct connection between a single computer and a faraway LAN or between two faraway LANs. This is not a remote desktop connection or a terminal or a Web page connection. A VPN puts a single system or a separate LAN on the same broadcast domain, the same Layer 2 connection, just as if the faraway system plugged directly into the LAN’s switch.
Always-on VPN
Site-to-site VPN concentrators generally never disconnect. We call these always-on VPNs.
Split-tunnel VPN
Current VPN technologies enable you to configure a VPN connection to send only LAN traffic through the tunnel. All other traffic ignores the tunnel. This is a split tunnel and is the most common type of tunnel.
Full-tunnel VPN
One early problem with VPNs was that once you connected to a LAN, that was your only connection. Your IP address and default gateway were on that LAN; you used that LAN’s DHCP and DNS servers. That meant if your computer was connected to a VPN and opened a Web browser, your computer went through the VPN connection and then went back out and used the Internet connection on your LAN. This is called a full tunnel and is a terrible way to get to the Internet.
Remote access vs. site-to-site VPN
VPNs work in one of two different ways. You can connect a single system to an existing LAN in what is called remote access, or you can connect two complete LANs in site-to-site.
VPN IPSec
Internet Protocol Security (IPsec) is a security protocol that works at the Network layer of the OSI model. IPsec was developed to provide security services (authentication and encryption) for IP traffic, since IP does not have any built-in native security protections. Three major protocols make up IPsec: AH, ESP, and ISAKMP.
SSL/TLS VPN
The only serious competitor to IPsec VPNs is VPNs using the SSL/TLS protocol. This is the same SSL/TLS protocol used in secure Web pages. SSL/TLS VPN connections don’t require special client software installed on the system that wants to connect to the remote network. That system uses only a Web browser and SSL/TLS security to make the VPN connection.
HTML5(VPN)
Sophos has a Unified Threat Management (UTM) system on Amazon Web Services (AWS) that enables you to log into AWS and get a list of predefined network services. The system requires an HTML5-compliant browser—so the latest Chrome, Firefox, or Safari work fine—but the catch is interesting: you can only access content remotely; you can’t download content to your local machine. Sophos calls its service a VPN portal—and CompTIA includes HTML5 VPN as a VPN option. Be aware that this exists for the exam.
Layer 2 tunneling protocol(L2TP)
Layer 2 Tunneling Protocol (L2TP) was developed jointly by Microsoft and Cisco, but it has become an Internet standard. L2TP is only an encapsulation protocol, simply providing transport services and protecting data through untrusted networks (such as the Internet) to get it to a destination network. L2TP still sees some adoption but is also fading to IPsec and SSL/TLS VPNs.
DNS
The Domain Name System (DNS) resolves Internet names to IP addresses.
Network access control(NAC)
Network access control (NAC) provides network protection and security by prohibiting hosts from connecting to the organization’s infrastructure unless they meet certain criteria. A NAC device provides an entry point or gateway into the network, typically for remote or mobile clients. This device checks the health and security settings of the client—a host health check—against a specified set of criteria before allowing it to access the network.
Agent and agentless
Agent-based NAC tracks many features of potentially inbound devices, such as software versions and so on. The agent-based approach enables very fine control over allowing a device to connect to the network. The criteria used for an agent-based approach can be permanent or dissolvable. The former means the device that wants access to the network must have some software loaded—that software stays loaded. A dissolvable agent system runs something once on the device and admits or denies access; the software is then deleted.
Agentless NAC (such as one based on Windows Active Directory) would apply group policy rules to enforce the controls that an agent-based NAC device would do directly.