This chapter covers the following subjects:
• Management plane attack types: Reviews the different types of attacks that are focused on the management plane.
• Management plane security technologies: Goes over the specific technologies that can be used to mitigate the various management place attack types and describes how to configure them.
The management plane is a hard thing to protect in the production environments because it must remain open enough for legitimate management but stay closed enough to not be exploited. This chapter reviews the threats to the management plane and describes the available security technology options that are available to help in securing it.
The “Do I Know This Already?” quiz helps you decide whether you really need to read the entire chapter. If you already intend to read the entire chapter, you do not necessarily need to answer these questions now.
The ten-question quiz, derived from the major sections in the “Foundation Topics” section of this chapter, helps you determine how to spend your limited study time.
Table 10-1 outlines the major topics discussed in this chapter and the “Do I Know This Already?” quiz questions that correspond to those topics.
Table 10-1. “Do I Know This Already?” Foundation Topics Section-to-Question Mapping

The goal of self-assessment is to gauge your mastery of the topics in this chapter. If you do not know the answer to a question or are only partially sure of the answer, you should mark this question wrong for purposes of the self-assessment. Giving yourself credit for an answer that you correctly guess skews your self-assessment results and might provide you with a false sense of security.
1. Which type of management plane attack type works by creating or taking over a management session?
a. Slow-path denial of service
b. Management session spoofing
c. Man-in-the-middle attacks
d. DoS session spoofing
2. Which of the following type of password is used to secure SSH connections?
a. Terminal line
b. Console
c. Async
d. Enable
4. What is the minimum modulus (key size) that must be used to enable SSH version 2?
a. 2048
b. 512
c. 1024
d. 768
5. Which of the following SNMP components is run directly on the device?
a. Manager
b. Agent
c. MIB
d. Supervisor
6. Which of the following SNMP operations notify the manager of an event without requiring an acknowledgment?
a. Get
b. Trap
c. Put
d. Inform
7. Which of the following authentication mechanisms can be used with SNMP version 3?
a. MD5
b. 3DES
c. AES
d. SHA
9. Which of the following global services are disabled by the AutoSecure feature?
a. HTTP server
b. SSH
c. NTP
d. AAA
10. Which of the following are valid types of keys when using digitally signed Cisco software?
a. Rollover
b. Development
c. Global
d. Special
The answers to the “Do I Know This Already?” quiz are found in Appendix A. The suggested choices for your next step are as follows:
• 8 or less overall score: Read the entire chapter. This includes the “Foundation Topics” and the “Exam Preparation” sections.
• 9 or 10 overall score: If you want more review on these topics, skip to the “Exam Preparation” section.
As with the other planes that were discussed in the previous chapters, it is important to understand the common types of attacks that are attempted toward the management plane. The following sections review these common attack types.
When setting up the management of network devices, it is important that those who are able to gain access to them have been authenticated and given the appropriate privileges to do their jobs. Depending on the size of the company and the network, these privileges can be set up to only permit those commands required to be used at each stage of the support structure. It is also important that whatever authentication is used is capable of securing the device not only from unauthorized internal users but also from outside attacks. A strong management structure is vital in maintaining these requirements. This chapter covers a number of different features that can be used to create a system that meets these requirements.
As much as a strong management system is important in maintaining the security of a device, it is also important to secure the device from potential spoofing attacks. These attacks are made possible by using management protocols that are inherently insecure and should not be used. These attacks work by creating or taking over a management session. The attacker can then perform the commands that were able to be performed by the exploited user.
You can use a number of different security technologies to mitigate the attacks alluded to in the previous section. A description of these technologies and how to implement them will be covered in the following sections.
Some of the best ways to secure a networking device are the simplest things to configure. These include basic password management, the configuration of privileges, and the creation of access control lists (ACL) that are used to limit management access. This section reviews the available options and displays how to configure each of them.
Each device has a number of IOS modes that are used to display and configure it for a variety of operations; the main two are

• User EXEC mode: While in user EXEC mode, the user is limited to doing a number of limited display commands that can only be used to parse the simplest of device information.
• Privileged EXEC mode: By default, while in privileged EXEC mode, the user is allowed to do any of the commands available on the device, including all that display and configure the device.
On top of privileged EXEC mode are a number of configuration modes that can be used to configure the various features available on the device. The highest available configuration mode is global configuration mode, which is used to configure feature options for the entire device. From within global configuration mode, there are a number of different others modes that can be accessed to configure all the other available features on the device.
On each device, there are a number of passwords that can be set to control access to the various parts of the device, which include the following:

• Enable: The enable password is used to control access to the privileged EXEC mode.
• Console: The console password is used to control access to user EXEC mode when connecting through the console port of the device.
• Terminal line: The terminal lines (also called virtual teletypewriter lines [VTY]) are mainly used to control access to the user EXEC mode when connecting through Telnet or Secure Shell (SSH).
On a Cisco device, there are two different methods that can be used to set the enable password; these include the enable password and enable secret commands. The difference between these two commands is the method that is used to store the password information when contained in the device configuration. By default, many of the passwords entered on these devices are entered into the configuration as plain text. This includes the enable password when configured with the enable password command. If a level of encryption on these passwords is required, two options exist:
• Configure the service password-encryption command. When this command is issued, all clear-text passwords will be stored in the configuration encrypted with a low-level reversible encryption. Because this encryption is easy to reverse, it is recommended only as a first level of password security.
• Configure the enable secret command. When using this command, the enable password is stored in the configuration using the message digest algorithm 5 (MD5) algorithm, which is not reversible and considerably harder to exploit.
Both the console and terminal line passwords are clear text by default and are affected by the service password-encryption command. However, neither of these passwords has an MD5 option like the enable password. With these passwords, the low-level encryption provided by the service password-encryption command is all that is available.
Table 10-2 describes the commands that are used to change each of these passwords.
Table 10-2. Configuring Device Passwords

Example 10-1 shows the configuration of the enable password using MD5, enables password encryption, and configures the console and terminal line passwords.
Example 10-1. Configuring Device Passwords
Router# configure terminal
Router(config)# enable secret ciscopress
Router(config)# service password-encryption
Router(config)# line console 0
Router(config-line)# password ciscopress
Router(config-line)# line vty 0 4
Router(config-line)# password ciscopress
Additional levels of protection are available through the use of privilege levels. By default, user EXEC mode is privilege level 1 and privileged EXEC mode is privilege mode 15. These levels, from 1 through 15, are available to be modified to suit the specific needs of an organization. There are three main ways in which privileges can be implemented: using different enable passwords that are each given a different level of authorization, through the use of usernames configured on the device, and using a server-based username solution. Obviously, the use of different enable passwords is easy, but quite configuration intensive should there be a number of different devices. The same is true of using usernames configured at each device. The best solution to use in large organizations is the use of server-based username authorization; however, this is outside the scope of this book. Table 10-3 outlines the configuration of privilege levels without the use of a server.
Table 10-3. Configuring Privilege Levels

Use the privilege reset option when trying to make command changes; there is no no form of the privilege command.
Example 10-2 shows the configuration of privilege level 7, which is configured to allow the clear counters command to be issued. An enable password and user “cisco” are configured to use privilege level 7 using “ciscopress” as a password.
Example 10-2. Configuring Privilege Levels
Router# configure terminal
Router(config)# privilege exec level 7 clear counters
Router(config)# enable secret level 7 ciscopress
Router(config)# username cisco privilege 7 secret ciscopress
When changing passwords on Cisco devices, they are not verified, which can lead to lockouts. Ensure that the passwords that you enter are correct. A good safeguard is to have two sessions open to the device when changing passwords; use one of them to change the password and to test that it works correctly. If there is an entry problem, the second session will still be able to change the password.
Role-Based Access Control (RBAC) is implemented on devices through the use of role-based CLI access. Role-based CLI access provides the ability to set up to 15 (not including the root view) CLI views that are configured to run commands that are configured for different job functions. The configuration is similar to setting up privileges but allows additional control that is not provided using privileges alone.
When using CLI views, all configurations are done using the root view. The root view has the privileges equivalent to level 15 but with the additional ability to configure CLI views. Role-based CLI access also allows the configuration of a superview that can be configured with the privileges from several existing CLI views; this can then be used by higher-level network operations personnel.
The configuration of a CLI view involves the creation of the CLI view, the setting of a password, and several commands that are used to specify the commands that will be allowed. Table 10-4 describes the different commands that are required to create and configure a CLI view.
Table 10-4. Configuring a CLI View

Unlike with user EXEC mode, which includes many basic CLI commands by default, a view, by default, is only allowed to perform the exact commands as specified by the configuration.
Example 10-3 shows the configuration of a new CLI view called ciscoview, shows a password of ciscopress, and allows the use of the show version command.
Example 10-3. Configuring a CLI View
Router# configure terminal
Router(config)# aaa new-model
Router(config)# end
Router# enable view
Router# configure terminal
Router(config)# parser view ciscoview
Router(config-view)# secret ciscopress
Router(config-view)# commands exec include show version
After the CLI views have been configured, the ability to create a superview is available. As stated previously, a superview is a view that is given the privileges of several existing CLI views. Table 10-5 describes the different commands that are required to create and configure a CLI superview.
Table 10-5. Configuring a CLI Superview

Example 10-4 shows the configuration of a new CLI superview called ciscosuper, shows a password of ciscopress, and associates CLI views ciscoview and ciscoview_2. When logged in using this superview, the user will have access to the commands from both of these views.
Example 10-4. Configuring a CLI Superview
Router# enable view
Router# configure terminal
Router(config)# parser view ciscosuper superview
Router(config-view)# view ciscoview
Router(config-view)# view ciscoview_2
Another method of securing the terminal lines into a device is through the use of an ACL that is configured on each terminal line into the device. These ACLs can be configured to only allow management traffic into these terminal lines from a specific host or network. Because ACLs were covered in Chapter 8, “Implementing and Configuring Cisco IOS Routed Data Plane Security,” this section only reviews the application of an ACL on specific terminal lines. Table 10-6 describes the different commands that are required to create and configure a management ACL.
Table 10-6. Configuring Management ACLs

Example 10-5 shows the configuration of access list 1 inbound on all terminal lines.
Example 10-5. Configuring a Management ACL
Router# configure terminal
Router(config)# access-list 1 permit 192.168.1.100
Router(config)# line vty 0 4
Router(config-line)# access-class 1 in
For a long time, the preferred method of managing devices was through the use of Telnet. The problem with Telnet is that it is not a secure protocol and can be easily intercepted, which can lead to significant security problems. The solution for this is the use of the Secure Shell (SSH) protocol, which provides an encrypted session between the device and the managing user.
Two different versions of SSH are supported on these devices: version 1 and version 2. Version 2 provides some additional capabilities, including support for larger bit modulus (key size) and RSA key enhancements.
There are two methods of SSH configuration. The first requires that both the device host name and the device domain name be configured before initial SSH configuration. This type of configuration is shown next. Table 10-7 describes the different commands that are required to create and configure SSH with a host name and domain name.
Table 10-7. Configuring SSH with Host Name and Domain Name

Example 10-6 shows the configuration of SSH using a host name of device, a domain name of ciscopress.com, and a modulus of 512.
Example 10-6. Configuring SSH with Host Name and Domain Name
Router# configure terminal
Router(config)# hostname device
device(config)# ip domain-name ciscopress.com
device(config)# crypto key generate rsa modulus 512
By default, if a key pair is generated that has a modulus that is greater than or equal to 768, both version 1 and version 2 of SSH are enabled and both types of connection are honored. If only a specific version of SSH is intended, either a modulus less than 768 must be used (to enable SSH version 1) or it can be individually configured.
The second method of SSH configuration uses key pair labels (names); this method does not require the prior configuration of a host name or domain name. Table 10-8 describes the different commands that are required to create and configure SSH without a host name or domain name.
Table 10-8. Configuring SSH Without a Host Name and Domain Name

Example 10-7 shows the configuration of SSH without a configured host name and domain name. This configuration includes a key pair name of ciscopair, with a modulus of 1024, and configures the use of only SSH version 2.
Example 10-7. Configuring SSH Without a Host Name and Domain Name
Router# configure terminal
Router(config)# ip ssh rsa keypair-name ciscopair
Router(config)# generate rsa usage-keys label ciscopair modulus 1024
Router(config)# ip ssh version 2
The Simple Network Management Protocol (SNMP) is used by many organizations to keep a good management and monitoring capability for all their devices. SNMP can be used for a number of different things, from the monitoring and triggering of alerts to device configuration.
SNMP is broken down into three components:

• SNMP manager: The SNMP manager controls and monitors the devices within the network using SNMP.
• SNMP agent: The SNMP agent is the component that is run directly on the device and maintains data and reports this data (if needed) to the SNMP manager.
• MIB: The Management Information Base (MIB) is a virtual information storage location that contains collections of managed objects. Within the MIB, there are objects that relate to different defined MIB modules (for example, the interface module).
The use of these three components can make a network easy to monitor and maintain. To obtain information from the MIB on the SNMP agent, several different operations can be used:

• Get: Used to get information from the MIB from an SNMP agent
• Set: Used to get information to the MIB from an SNMP manager
• Walk: Used to list information from successive MIB objects within a specified MIB
• Trap: Used by the SNMP agent to send a triggered piece of information to the SNMP manager
• Inform: The same as a trap, but adds an acknowledgment that is not provided with a trap.
There are also three main versions of SNMP that have been defined:

• Version 1: This version was defined in RFC 1157 and utilizes community-based security.
• Version 2c: This version was defined in RFCs 1901, 1905, and 1906 and utilizes community-based security. Version 2c added some additional protocol operations and data types to version 1; these include a bulk retrieval mechanism.
• Version 3: This version was defined in RFCs 3413 through 3415 and defines a new security model that includes features that support message integrity, authentication and, encryption.
The community-based security method is known to be a large security vulnerability to versions 1 and 2 because of its lack of encryption and authentication (other than a simple community name). While the configuration of SNMP version 3 is more intensive, it should be preferred when traffic is routed over untrusted networks. Table 10-9 shows the various SNMP security models and levels.
Table 10-9. SNMP Security Models and Levels

Typically, the first things that are configured on a device include the system contact, device location, and device serial number. The first SNMP command, which is used automatically, enables the SNMP agent on the device. Table 10-10 outlines the commands to configure the system contact, device location, and device serial number.
Table 10-10. Configuring Basic SNMP

Example 10-8 shows the configuration of basic SNMP parameters, including a contact, device location, and device serial number.
Example 10-8. Configuring Basic SNMP
Router# configure terminal
Router(config)# snmp-server contact John Smith at (919) 555-1212
Router(config)# snmp-server location Raleigh, NC
Router(config)# snmp-server chassis-id 123456
To limit the amount of information that is available for those accessing the MIB objects on a device, a view can be configured. A view is configured with the MIB objects that are allowed (or disallowed) to be accessed by a specific community or group. It is through the configuration of multiple view entries that the access control of the MIB objects is controlled. Table 10-11 outlines the commands to configure an SNMP view.
Table 10-11. Configuring SNMP Views

Example 10-9 shows the configuration of the ciscoview SNMP view, which is configured to allow access to the entire MIB-II subtree.
Example 10-9. Configuring SNMP Views
Router# configure terminal
Router(config)# snmp-server view ciscoview mib-2 included
With SNMP versions 1 and 2c, a community string is used as the only form of authentication. When configuring a community string, specific privileges can be given to those authenticating with the correct string. Access can be given broadly with global read-only and global read-write access as well as more specifically with an existing SNMP view. Access to the SNMP agent can also be restricted through the use of a standard IP access list. Table 10-12 describes the different commands that are required to create and configure SNMP communities.
Table 10-12. Configuring SNMP Communities

Example 10-10 shows the configuration of two communities, the first with read-only access to the entire MIB and the second with access to only the MIB-II subtree as provided by the ciscoview view created in Example 10-9.
Example 10-10. Configuring SNMP Communities
Router# configure terminal
Router(config)# snmp-server community first ro
Router(config)# snmp-server community second view ciscoview
The configuration of SNMP version 3 is different from that of the other versions because the security mechanism is much more complex and offers a much higher level of security. Security is configured through the creation of users and groups; the groups are given access to specific SNMP MIB objects through views, and the users are assigned to specific groups. Version 3 also supports the use of both authentication (MD5 or Secure Hash Algorithm [SHA]) and encryption (Data Encryption Standard [DES], Triple DES [3DES], or Advanced Encryption Standard [AES]) of SNMP traffic. Users can be set up on the local device and/or on the remote management server. The security digests required for authenticating and encrypting packets utilize an EngineID that is automatically generated on the local device (local EngineID) but is required to be configured for each remote device/remote management server when exchanging packets (remote EngineID). Remote users can also be configured, but the remote EngineID is required before these users can be created to ensure proper security exchange information. Table 10-13 describes the different commands that are required to create and configure SNMPv3 users and groups.
Table 10-13. Configuring SNMP v3 User and Groups

Example 10-11 shows the configuration of a new SNMP group called v3group that is used for authorization and provides a read view of ciscoview. This configuration also shows a new SNMP user called v3user configured to use MD5 for authorization with a password of ciscopass.
Example 10-11. Configuring SNMP v3 User and Groups
Router# configure terminal
Router(config)# snmp-server group v3group v3 auth read ciscoview
Router(config)# snmp-server user v3user v3group v3 auth md5 ciscopass
One of the main capabilities with SNMP is the ability to have the devices send messages to a central server for recording purposes or to alert a device of a problem. These messages can be in the form of a trap or inform; the difference between the two is that an inform requires an acknowledgment from the server while a trap does not. An SNMP version 3 inform also requires that a remote EngineID is configured to ensure that the acknowledgment security information is able to be correctly calculated. Table 10-14 describes the different commands that are required to configure SNMP notifications.
Table 10-14. Configuring SNMP Notifications

Example 10-12 shows the configuration of the EngineID for the remote network server at IP address 10.10.1.100 and with an EngineID string of 800000090300CA00144C0008, and configures a notification host at IP address 10.10.1.100. Then, it configures SNMP informs to be sent for alert events.
Example 10-12. Configuring SNMP v3 Notifications
Router# configure terminal
Router(config)# snmp-server engineID remote 10.10.1.100 800000090300CA00144C0008
Router(config)# snmp-server user v3remoteuser v3group remote 10.10.1.100 v3 auth
md5 ciscopass
Router(config)# snmp=server host 10.10.1.100 informs version 3 auth v3remoteuser
Router(config)# snmp-server enable traps alert
One of the ways to monitor whether an attack is occurring on a device is through the simple monitoring of device resources, including CPU and memory utilization. This is done by configuring the use of CPU or memory threshold monitoring. Both of these features can be combined with a remote management server to notify an organization when the CPU and memory conditions on a device become critical.
The configuration of CPU thresholding utilizes two different types of threshold: rising and falling. The rising threshold is triggered when the CPU utilization exceeds a configured threshold. A falling threshold is triggered when the CPU utilization falls back below a configured threshold. Table 10-15 describes the different commands that are required to configure CPU thresholding.
Table 10-15. Configuring CPU Thresholding

Example 10-13 shows the configuration of a CPU threshold that triggers when the total CPU utilization goes above 70 percent and when it falls back below 40 percent and is checked in 5-second intervals.
Example 10-13. Configuring CPU Thresholding
Router# configure terminal
Router(config)# snmp=server host 10.10.1.100 traps first
Router(config)# snmp-server enable traps cpu threshold
Router(config)# process cpu threshold type total rising 70 interval 5 falling 40
interval 5
The memory threshold feature also has two different options that can be configured. These include an ability to trigger a message when the device memory goes below a configured level and/or the ability to reserve an amount of memory to be used for critical notifications. Table 10-16 describes the different commands that are required to configure memory thresholding.
Table 10-16. Configuring Memory Thresholding

Example 10-14 shows the configuration of memory threshold of 10 MB (less than 10 MB is available) and a reservation of 2 MB for critical notifications.
Example 10-14. Configuring Memory Thresholding
Router# configure terminal
Router(config)# memory free low-watermark processor 10000
Router(config)# memory reserve critical 2000
In many situations, it is possible to know which device interface or interfaces will always be used for management traffic. It is in these situations when the Management Plane Protection (MPP) feature can be used. MPP enables you to limit the source of management traffic to a specific interface (or interfaces) on a device. This is important because many of these protocols are inherently insecure. This ability provides additional protection from management plane attacks that are sourced off of interfaces that should never contain management traffic.
To use the MPP feature, IP Cisco Express Forwarding (CEF) must be enabled on the device. Also note that if the management of a device is handled through the use of a loopback interface, the management interface to be used in MPP configuration is the physical interface where management traffic will be processed.
The MPP feature supports only the following specific management protocols:

• File Transfer Protocol (FTP)
• Hypertext Transfer Protocol (HTTP)
• Hypertext Transfer Protocol - Secure (HTTPS)
• Secure Shell (SSH), versions 1 and 2
• Simple Network Management Protocol (SNMP), all versions
• Telnet
• Trivial File Transfer Protocol (TFTP)
• Blocks Extensible Exchange Protocol (BEEP)
Table 10-17 describes the different commands that are required to configure management plane protection.

Example 10-15 shows the configuration of MPP using interface fastethernet0/0 and allowing only the SSH protocol.
Example 10-15. Configuring MPP
Router# configure terminal
Router(config)# ip cef
Router(config)# control-plane host
Router(config-cp-host)# management-interface fastethernet0/0 allow ssh
The AutoSecure feature can be used to disable many of the commonly exploited IP services on a device. The caveat is that many of these IP services are used for valid purposes and need to be left running. It is because of this that Cisco recommends that this feature not be used in a production environment but rather in a test environment as a reference to which services can be disabled and how to disable them.
The following global services are disabled on a device without prompting when AutoSecure is enabled:

• Finger
• PAD
• Small Servers
• BOOTP Server
• HTTP Server
• Identification Service
• Cisco Discovery Protocol (CDP)
• Network Time Protocol (NTP)
• Source Routing
The following global services are enabled on a device without prompting when AutoSecure is enabled:
• service password-encryption is enabled.
• service tcp-keepalives-in and service tcp-keepalives-out are enabled.
The following interface services are disabled on a device without prompting when AutoSecure is enabled:
• Internet Control Message Protocol (ICMP) redirects
• ICMP unreachables
• ICMP mask reply messages
• Proxy ARP
• Directed Broadcast
• Maintenance Operations Protocol (MOP)
The following options are available on the device when AutoSecure is enabled:
• If a device banner does not exist, a prompt will ask for one.
• A login and password are configured for the console, AUX, VTY, and TTY lines (if available), and the EXEC timeout is set to 10 minutes.
• If the device has a crypto image, SSH and secure copy (SCP) are enabled, and the timeout and authentication retries are set to minimums.
• If run in noninteract mode, SNMP is disabled if the community strings are set to public or private; if run in interactive mode, it is prompted whether to disable SNMP regardless of the configured community strings.
• If authentication, authorization, and accounting (AAA) is not configured, it will be prompted to configure a local username and password.
The following logging options are available on the device when AutoSecure is enabled:
• Sequence numbers and time stamps are enabled on all debug and log messages.
• Logging messages will be generated for login-related events.
• The logging console critical, logging buffered, and logging trap debugging commands are issued.
Table 10-18 describes the different commands that are required to configure AutoSecure.
Table 10-18. Configuring AutoSecure

Example 10-16 shows the configuration of the AutoSecure feature on all available options on a device without prompting.
Example 10-16. Configuring AutoSecure
Router# auto secure no-interact
A new feature that is only available in the new Cisco IOS Release 15.0.1M and later is digitally signed software. At the time of this writing, it is only supported by the 1900, 2900, and 3900 series routers.
Digitally signed software will come with an extension of .SPA or .SSA, depending on the type of image. The type of image can be calculated using the following key:
• First character: States that the image is digitally signed (S)
• Second character: Specifies which type of image (P = Production, S = Special)
• Third character: Indicates the key version
There are three different types of key:
• Production
• Special
• Rollover
The use and configuration of signed images are outside the scope of this book, but the information is provided because it will become more commonplace with newer versions of Cisco software.
You can find additional information about the digitally signed software feature and configuration at www.cisco.com/en/US/docs/ios/fundamentals/configuration/guide/cf_dgtly_sgnd_sw_ps10591_TSD_Products_Configuration_Guide_Chapter.html.
As mentioned in the section, “How to Use This Book,” in the Introduction, you have several choices for exam preparation: the exercises here, the memory tables in Appendix C, the final exam preparation chapter, and the exam simulation questions on the CD-ROM. The following questions present a bigger challenge than the exam itself because they use an open-ended question format. By using this more difficult format, you exercise your memory better and prove your conceptual and factual knowledge of this chapter. You can find the answers to these questions in Appendix A, “Answers to the DIKTA Quizzes and Fill in the Blanks Questions.”
Review the most important topics in the chapter, noted with the Key Topics icon in the margin of the page. Table 10-19 lists a reference of these key topics and the page numbers on which each is found.

Print a copy of Appendix C, “Memory Tables” (found on the CD), or at least the section for this chapter, and complete the tables and lists from memory. Appendix D, “Memory Table Answers,” also on the CD, includes completed tables and lists to check your work.
Define the following key terms from this chapter, and check your answers in the Glossary:
Table 10-20 lists the important commands from this chapter. To test your memory, cover the right side of the table with a piece of paper, read the description on the left side, and then see how much of the command you can remember.
Table 10-20. Command Reference







