Network Security Architecture Implementation
As soon as the security policy has been defined, the next step is implementing the policy in the form of a network security design. We will discuss various security principles and design issues throughout this book. The first step to take after a security policy has been created is to translate it into procedures. These procedures are typically laid out as a set of tasks that must be completed to successfully implement the policy. These procedures upon execution result in a n..
Static NAT works just like the example in Figure 4-6, but with the IP addresses statically mapped to each other via configuration commands. With static NAT: ■ A particular Inside Local address always maps to the same Inside Global (public) IP address. ■ If used, each Outside Local address always maps to the same Outside Global (public) IP address. ■ Static NAT does not conserve public IP addresses. Although static NAT does not help with IP address conservation, sta..
Cisco IOS provides a wide variety of queuing tools. The upcoming sections of this chapter describe several different IOS queuing tools, with a brief summary ending the section on queuing. Table 15-2 summarizes the main characteristics of different queuing tools that you will want to keep in mind while comparing each successive queuing tool. Table 15-2 Key Comparison Points for Queuing Tools
Secure Shell and Cisco IOS SSH
Secure Shell (SSH) is a protocol that provides a secure connection to a router. Cisco IOS supports version 1 and 2 of SSH, which enables clients to make a secure and encrypted connection to a Cisco router. Cisco refers to this SSH support as Cisco IOS SSH. Before SSH was implemented, the only form of security available when accessing devices such as routers was Telnet username/password authentication, which is clearly visible with a network sniffer. Telnet is insecure because..
Frame Relay Forum Implementation Agreement Document Number FRF.5
The functional specifications of network interworking between Frame Relay and ATM are defined in the Frame Relay Forum Implementation Agreement Document Number FRF.5. FRF.5 describes the implementation agreement on PVC network interworking between Frame Relay and ATM protocols, jointly agreed upon by the Frame Relay Forum and the ATM Forum. The complete FRF.5 documentation can be downloaded from the Frame Relay Forum's web site address at http://www.mplsforum.org/frame/Approv..
