This chapter covers the following subjects:
• Vulnerabilities: This section reviews the various number of vulnerabilities that must be reviewed when analyzing a network.
• Intruder motivations: This section reviews the possible motivating factors that are used by the attacking parties.
• Types of network attacks: This section reviews a list of the current network attacks and describes how they are used.
This chapter discusses the potential network vulnerabilities and attacks that pose a threat to networks. In today’s open environment, it has become obvious that security must be a key part of everything up front in order to maintain a truly secured network. In the past, network security was able to be managed through the use of a single device (point solutions) or group of devices that existed at the main network entrance. Although this placement must be part of the security design, it is only one of many pieces. The threats that exist today have evolved in such a way that threat detection must be part of not only the main entrance of the network but also part of each networking element. This integration allows several different protection technologies to be deployed throughout the network; the use of these different technologies provides technology redundancy and better security.
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 eight-question quiz, derived from the major sections in the “Foundation Topics” portion of this chapter, helps you determine how to spend your limited study time.
Table 2-1 outlines the major topics discussed in this chapter and the “Do I Know This Already?” quiz questions that correspond to those topics.
Table 2-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. A good rule of thumb for “strong” passwords is that they follow which of the following guidelines?
a. Should be uppercase and lowercase, numbers, and special characters
b. Should be complex and documented someplace
c. Should be common words all strung together
d. Should be documented so that you can reference them
e. All of these answers are correct.
2. Which of the following are the main reasons why security attacks occur?
a. Lack of effective network security policy
b. Insecure physical premises
c. Network configuration weaknesses
d. Technology weaknesses
e. Improperly documented changes
3. Which of the following are the main categories of threats?
a. Categorized
b. Structured
c. Open
d. Closed
e. Unstructured
f. Uncategorized
4. Which of the following are major network attack types?
a. Reconnaissance
b. Access
c. Distributed
d. Aggressive
e. DoS
5. Which of the following are considered to be intruders on a computer system?
a. Crackers
b. Hackers
c. Phreakers
e. All of these answers are correct.
6. An intruder who enjoys the challenge of being able to bypass security measures is considered intruding for which of the following reasons?
a. Curiosity
b. Fun and pride
c. Revenge
d. Profit
e. Political purpose
f. None of these answers are correct.
7. Which of the following areas of the network are the most susceptible to configuration errors affecting security?
a. Firewall settings
b. DHCP settings
c. SNMP settings
d. IPS/IDS rules
e. IP assignment settings
8. Which of the following are methods for performing a fabrication access attack? (Select all that apply)?
a. Virus
b. DoS
c. Worm
d. Spoofing
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:
• 6 or less overall score: Read the entire chapter. This includes the “Foundation Topics” and the “Exam Preparation” sections.
• 7 or 8 overall score: If you want more review on these topics, skip to the “Exam Preparation” section. Otherwise, move on to Chapter 3, “Network Foundation Protection (NFP) Overview.”
Computer systems are a fundamental component of nearly every organization today. Large and small corporations, government agencies, and other organizations devote significant resources to maintaining their networks, and even the smallest organization is likely to use a computer to maintain its records and financial information. Because these systems can perform functions rapidly and accurately and because they make it easy to facilitate communication between organizations, computer networks continue to grow and become more interconnected. Any organization that wants to provide some public access to its network usually maintains an Internet connection; this access comes with certain risks. This chapter defines some of the risks to networks and explains how an ineffective network security policy can further increase the chance of a network security breach. The key issues in securing and maintaining a computer network are confidentiality, integrity, and availability.
To understand cyberattacks, you must remember that a computer, no matter how advanced, is a machine that operates based on predetermined instruction sets. The operating systems and other software packages are compiled instruction sets that the computer uses to transform input into output. A computer cannot determine the difference between authorized and unauthorized input unless specific filters and detection engines are in place to look for them. Any point in a software package that enables a user to alter the software or gain access to a system (that was not specifically designed into the software) is called a vulnerability. In many cases, crackers can exploit vulnerabilities and thus gain access to a network or computer. (See the section, “Threats.”) It is possible to remotely connect to a TCP/IP computer on any of 65,535 available ports. As hardware and software technology continues to advance, this “dark side” continues to search for and discover new vulnerabilities. For this reason, most software manufacturers continue to produce patches for their products as vulnerabilities are discovered.
Most computer networks contain a combination of public and private data. A properly implemented security scheme protects all the data on the network while allowing some data to be accessed by outside entities, usually without the ability to change that data (for example, a corporate website). Other data, such as payroll information, should not be made available to the public and should be restricted only to specific users within the organization. Network security, when properly implemented, secures the corporate data, reduces the effectiveness of hacking attempts, and ensures that systems are used for their intended purposes. Networks designed to be freely available to the public need to be secured to ensure confidentiality and integrity of the information and availability to the public. Additionally, properly securing a network ensures that network resources are not used as an attack point against other networks.
Security attacks occur and damage networks because of the following main reasons:
• Lack of effective network security policy
• Network configuration weaknesses
• Technology weaknesses
Because a network security policy directs administrators and engineers regarding how communications should be enabled and implemented, this policy serves as the basis for all security efforts. Security policies have weaknesses for numerous reasons, including the following:
• Politics: Politics within an organization can cause a lack of consistency within the security policies or, worse, a lack of uniform application of the security policies. Many security policies make so many exceptions for management and business owners that they become meaningless.
• Lack of a written security policy: The lack of a written security policy is essentially the same as not having a policy. Publishing and widely distributing the security policy, along with a thorough training program, prevents confusion about it within the organization.
• Lack of continuity: When personnel change too frequently, people often take less care regarding the enforcement of security policies. When a system administrator leaves a position, for example, all the passwords used by that administrator need to be changed. In an organization that changes administrators several times each year, there is a natural reluctance to change the passwords because users know they will be changed again soon because of administrator turnover.
• Lack of disaster recovery planning: A good disaster recovery plan must include contingencies for both physical and virtual security breaches. Confusion that results from a disaster can hamper the success of forensics efforts because administrators might not be careful in their recovery efforts.
• Lack of patch management within the security policy: A good security policy allows frequent hardware and software upgrades. A detailed procedure for implementing new hardware and software ensures that security does not become forgotten while implementing new equipment and software.
• Lack of monitoring: Failure to monitor logs from all available equipment exposes many organizations to attack without any knowledge that those attacks are occurring. Almost all equipment has the ability to log everything from simple events to security breaches; this information should be carefully monitored to ensure quick response.
• Lack of proper access controls: Unauthorized network access is made easier when poorly designed access controls are implemented on the network. Improper password length, infrequent password changes, passwords written on sticky notes adhered to monitors, and freely shared passwords are security risks that potentially can lead to security breaches. These can all be remedied when a thorough training program is used to educate users as to the risks of performing these actions.
The existence of all these different vulnerabilities is why Cisco developed the SAFE methodology and why it is best to follow the recommendations laid out in the methodology. There are so many pieces that exist within a network that in the past, much of the design was focused on the functionality of the network and had security added as an afterthought. With today’s networks and threats to them, it is best that these networks be designed with integrated security technologies.
As network devices become increasingly complex, the knowledge base required to configure systems correctly increases, too. This complexity represents more of an issue in smaller organizations in which a single administrator might be responsible for the LAN, WAN, servers, and workstations. In any organization, the most effective way to overcome network and system configuration issues is to establish and enforce a standardized baseline for all configurations. Configuration weaknesses normally fall into one of the following categories:

• Misconfigured equipment: A simple misconfiguration can cause severe security issues. Whether the error is caused by a lack of knowledge of the system or a lack of attention to detail, the result might be an open vulnerability that leaves the system or network exposed to security threats and potential damage. Some areas of networking that are most susceptible to configuration errors are the firewall settings, access lists, intrusion prevention system/intrusion detection system (IPS/IDS) rules, Simple Network Management Protocol (SNMP) settings, and routing protocols.
• Weak or exposed passwords: Passwords that are too short, easily guessed, or consist of common words make it easy for an intruder to gain access to company resources, networks, and data. A “strong” password must consist of at least eight characters and include uppercase and lowercase letters, as well as numbers and special characters. Additionally, using the default password on administrator accounts is an especially poor practice. It is also important that users do not create a password that is too complex to remember. In such a scenario, users tend to write down their password on a sticky note, defeating the purpose of the password in the first place, and affix it to their monitor. One common method for creating and remembering passwords is the “vanity plate” method: Think of a word or phrase and convert it into the characters used on a vanity license plate, and then change the case of a letter or two and substitute one or more numbers for letters. Here is an example: In Virginia, for example, a Honda owner is apparently not fond of mayonnaise. The Honda owner’s license plate reads IH8 Mayo. You can drop in an underscore and an exclamation point and you get IH8_Mayo!. Not too fancy and easy to remember. Another password technique that poses a risk is the use of “common accounts” shared by many users. Common accounts prevent accurate accounting of which actions were taken by specific users and make it impossible to determine (to a legal standard) whether a specific user is responsible for a specific action.
• Misconfigured Internet services: Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), Terminal Network (Telnet), and other service security settings can all be configured in ways that are considered unsafe. Knowing exactly which services are required and which services are running ensures that Internet services do not create potential network security breaches.
• Using default settings: The default settings of many products are designed to assist in device configuration and production environment placement. One of the most common default settings is the default password, or the lack of a password by default. Examples of default configuration settings include the following:
• On initial configuration, there are no access lists limiting Telnet access on Cisco routers; if Telnet is enabled, you must ensure that the access is limited to authorized source addresses only (from your management network).
• On the Cisco Linksys line of routers, the default password is “admin” and the default SSID on wireless devices is “linksys.” Both of these make configuring and accessing them very easy but make their initial configuration very insecure.
These are just two examples of how default settings prove to be insufficient for production use.
All technologies have intrinsic weaknesses. These weaknesses can reside in the operating system, within the protocol, or within the networking equipment. Each of these weaknesses is discussed further in the following list:

• Operating system weakness: This weakness was discussed earlier in the “Vulnerabilities” section. Operating systems are complex, coded instructions written for the computer. If an intruder can inject additional instructions into the system by exploiting a vulnerability within the operating system, the intruder might be able to affect how that system functions. Entire organizations are dedicated to discovering and exploiting operating system vulnerabilities. Some operating systems tend to present a greater challenge and therefore receive significantly more attention from hackers, crackers, and script kiddies. This is most likely the reason why operating system developers dedicate tremendous resources to identifying and resolving possible vulnerabilities in a timely manner by releasing software patches. Many manufacturers have implemented an automated method to distribute patches and updates, such as Microsoft Windows Update, Linux up2date, Fedora YUM (Yellowdog Updater Modified), and Debian apt-get. It is now easier to immediately implement patches throughout the enterprise using automated techniques, thus ensuring the security posture of the network against the emerging threats that take advantage of new vulnerabilities. The flip side to this added security, however, is that some security patches have and will continue to be released without thorough testing. At times, this lack of up-front testing causes more problems than it fixes and should be considered as part of the security policy.
• Protocol weakness: Some protocol suites, such as Transmission Control Protocol/Internet Protocol (TCP/IP), were designed without an emphasis on security aspects. Some of the security weaknesses of protocols are as follows:
• As discussed in the previous section, some manufacturers receive significantly more attention from the hacker community. Microsoft has received more than its fair share of attention in this area. As a result, a significant number of vulnerabilities have been identified within the Microsoft Windows operating system, Microsoft Windows products, and Microsoft networking. It is common for perimeter firewalls to block nearly all the ports utilized for Microsoft networking to help protect against this common vulnerability.
• The TCP/IP suite consists of Internet Control Message Protocol (ICMP), User Datagram Protocol (UDP), and Transmission Control Protocol (TCP) and has several inherent weaknesses. For example, the header and footer of an IP packet can be intercepted and modified without leaving evidence of the change. ICMP packets are routinely used in denial of service (DoS) attacks, as discussed in the “Types of Network Attacks” section.
• As routing protocols were being developed, the emphasis was on functionality and communication and less on security. The lack of security in routing protocols resulted in a vulnerability that made it possible to inject incorrect information into the protocol and force a network disruption. There has been an increased emphasis on the security of routing protocols, along with the general elevation in the priority of network security.
• Application weaknesses: Many applications continue to be written without regard to security. Sometimes, this is caused by a lack of programming experience and sometimes, the company’s timelines restrict the time for coding securely. Because the primary objective of application development is functionality, security can easily become an item that is not heavily prioritized. Service packs, upgrades, and patches are normally released by the application developer as vulnerabilities are identified. As technology continues to develop, however, security is becoming a greater priority and is now being written into newly created applications during design. Another factor that affects the relative strength of an application is the application’s production timeline. The tremendous competition to get products to market sometimes forces software manufactures to introduce products that have not been thoroughly tested. In this case, the actual product testing might occur in a production environment.
• Network equipment weakness: Although all manufacturers strive to produce the best product possible, any system of sufficient complexity is prone to configuration errors or system design vulnerabilities. Additionally, all systems have their particular strengths and weaknesses. For example, one product might be efficient and secure when it processes a specific protocol or traffic for a specific application, but it might be weak or not support a different protocol or application. It is important to focus on exactly which type of network traffic you need to support and ensure that you implement the correct device in the correct location on the network. Additionally, always test your systems to ensure that they perform their functions as expected. Administrators who know the strengths and weaknesses of their equipment can overcome these shortcomings through the proper deployment and configuration of equipment.
Potential threats are divided into the following two categories, but their motivations tend to be more diverse and are detailed in the next section:

• Structured threats: A structured threat is an organized effort to breach a specific target. This can be the most dangerous threat because of its organized nature. Structured threats are preplanned attacks by a person or group seeking a specific target.
• Unstructured threats: Unstructured threats are by far the most common. They are usually a result of scanning the Internet by persons seeking targets of opportunity. Many different types of scanning files or “scripts” are available for download from the Internet and can be used to scan a host or network for vulnerabilities. Although the threat does not change, the attacker might change his methodology after vulnerabilities are identified.
Several motivations might prompt someone to intrude on another’s network. Although no text can list all the reasons why someone would decide to steal or corrupt data, some common themes become evident when looking at the motivations of previous intruders. To refine the discussion of intruder motivations, it is first necessary to define some terms. In the context of this chapter, an intruder refers to someone who attempts to gain access to a network or computer system without authorization. Intruders can be further classified as follows:

• Phreaker: Phreakers are individuals who have extensive knowledge of telephone networks and switching equipment. Their goal is to gain free access to telephone networks so that they can make local and long-distance calls.
• Cracker: Crackers use an advanced knowledge of networking and the Internet to compromise network security without proper authorization. Crackers are usually thought of as having a malicious intent.
• Hacker: Hackers investigate the integrity or security of a network or operating system, usually relying on advanced programming techniques. Ethical hacker (white hats) is a term that refers to security consultants or those with good intentions; companies often hire ethical hackers to test current defenses (and thus perhaps expose weaknesses). Hackers with mixed priorities between good and bad objectives are called grey hats, and hackers with malicious intent are referred to as black hats.
• Script kiddie: Script kiddies are novice hackers who rely heavily on publicly available scripts to test the security of a network and scan for vulnerabilities and weaknesses.
The dividing line between phreakers, crackers, hackers, and script kiddies is that phreakers, crackers, and hackers tend to be more skilled and normally develop their own tool sets; script kiddies, on the other hand, tend to be less skilled and use publicly available scripts. The motivation for someone to attempt to access, alter, or disrupt a network differs for each intruder. Some of the most common motivations are discussed in the sections that follow.
Not all network or system intrusions are a directed effort. Sometimes, a user initiates a security breach through a lack of understanding. For example, an uneducated user with administrative rights on a Microsoft Windows Vista or Microsoft Windows 7 system can easily remove or change critical settings, resulting in an unusable system. Having too much trust combined with a lack of understanding can be equally dangerous. Often, network administrators open their entire network to someone else when access to a single machine is all that is required. A poorly trained or inexperienced firewall administrator can easily open connectivity to a point that the firewall becomes ineffective. Another possibility is that a temporary firewall opening becomes a permanent opening because of a lack of procedures to ensure that temporary openings are closed after the need has passed. Although some security breaches occur without malicious intent, a good security policy can help prevent them.
Sometimes, people are just curious about data contained in a system or network. One incident typical of this type is a 14-year-old boy who accessed a credit-card company’s computer systems. When asked why he broke into the system, he said that he wanted to see whether he could get in and he wanted to see what was there. Employees, for example, might attempt to access the payroll system to see whether their pay accords with coworkers. Alternatively, an employee might be curious about the financial status of the company or wonder whether employee personnel files contain anything interesting. Despite the focus of the curiosity, the common theme among those intruding because of curiosity is that the data usually suffers little or no damage.
Some intruders enjoy the challenge of bypassing security measures. Many times, the more sophisticated the security measures, the greater the challenge. Whether these intruders are crackers, hackers, or script kiddies, their motivation is fun, pride, or a combination of the two. When George Leigh Mallory was asked why he wanted to climb Mount Everest, his reply was, “Because it is there.” This seems to be the motivation for a number of potential intruders. On several bulletin boards and in several discussion groups, members list their latest conquests and the challenges posed to breaking into an organization’s systems. The members of these groups applaud successful attempts and guide those who are unsuccessful. Additionally, many hacker websites publish tools, scripts, and code used to create viruses, worms, and Trojans. These websites are good places for a security administrator to monitor for information on the latest vulnerabilities and new techniques used for breaking into networks and systems.
Revenge can be powerful motivation. Disgruntled or former employees who have a good understanding of the network and know specific assets they want to target can cause substantial problems for an organization. Therefore, organizations should establish and enforce an “out-processing” procedure for employees to ensure that all the user accounts are removed or disabled and that any passwords for common accounts (which are not recommended in the first place) are changed. Whenever key personnel leave the organization, pay additional attention to network monitoring and intrusion detection to ensure that the former employee is not attempting to access the network using his knowledge of the network or perhaps any back-door access that might have been put in place during his employment.
Profit is a powerful motivator for breaking into computer networks and systems. Credit-card information, unauthorized bank transfers, and manipulation of billing information can be extremely profitable if successful; however, not all intrusions for profit are based on money. A perfect example of this is the TJX companies’ identity theft case, which has been in the news over the past few years. In this case, hackers compromised 45.7 million accounts over a two-year time period. The hackers involved in this case were caught, but the magnitude of such a breach is obviously large.
Because economies depend largely on electronic transactions, those economies are vulnerable to disruptions by an attacker. Cyberwarfare does exist and can pose a real threat to an economy. If disruption of an economy is desired, doing so through electronic means might become the ideal method for a number of reasons. These reasons include the ability to launch an attack from virtually any location, low equipment cost, low connectivity cost, and a lack of sufficient protection. A good example of this type of attack was the breach of the U.S. energy grid by foreign entities (China and Russia are accused). If these hackers were able to get in and deposit enough code to alter security and/or were able to map the infrastructure of the grid, much of the security that people take for granted could easily be circumvented. Another more common political motivation is known as hactivism, which is the act of targeting an organization and disrupting its communications or defacing its website for political purposes. A good example of this is the recent hacking of Sarah Palin’s email accounts; these accounts were hacked by a person attempting to expose what he thought was her political hypocrisy.
Before learning about the characteristics of specific network attacks, you need to understand the different types of attacks. Attacks are defined by the goal of the attack rather than the motivation of the attacker. The three major types of network attacks, each with its own specific goal, are as follows:

• Reconnaissance attacks: A reconnaissance attack is designed not to inflict immediate damage to a system or network but only to map out the network and discover which address ranges are used, which systems are running, and which services are on those systems. One must “access” a system or network to some degree to perform reconnaissance, but normally the attacker does not cause any damage at that time.
• Access attacks: An access attack is designed to exploit vulnerability and gain access to a system on a network. When access is gained, the user can do the following:
• Retrieve, alter, or destroy data
• Add, remove, or change network resources, including user access
• Install other exploits that can be used later to gain access to the system or network
• DoS attacks: A DoS (and DDos) attack is designed solely to cause an interruption to a system or network.
The goal of a reconnaissance attack is to perform reconnaissance of a system or network, and the goal of the reconnaissance is to determine the makeup of the targeted system or network and to search for and map any vulnerabilities. A reconnaissance attack indicates potential for other, more invasive attacks. Many reconnaissance attacks have been written into scripts that enable novice hackers or script kiddies to launch attacks on networks with a few mouse clicks. The following list identifies the more common reconnaissance attacks:
• DNS queries: A Domain Name System (DNS) query can provide a tremendous amount of information about an organization because the DNSs are designed to resolve IP address space to DNS names. Most DNS information is publicly available and simple to query. The two most informative DNS queries are the “DNS lookup” and the “whois query.” The DNS lookup provides you with the specific IP address information for servers using a specific domain name. A whois query provides the unauthorized user with the following information:
• Organization name
• Organization ID (assigned by the American Registry of Internet Numbers)
• Street address
• Assigned public IP address space
• Public name server addresses
• Technical contact name, telephone number, and email address
• Ping sweep: The output from a ping sweep can tell the unauthorized user the number of hosts active on a network.
• Vertical scans: Vertical scans scan the service ports of a single host and request different services at each port. This method enables the unauthorized user to determine which type of operating system is running and which services are running on the system.
• Horizontal scans: Horizontal scans scan an address range for a specific port or service. A common horizontal scan is the FTP sweep, which is the process of scanning a network segment, searching for replies to connection attempts on port 21.
• Block scans: Block scans are a combination of the vertical and horizontal scans. In other words, they scan a network segment and attempt connections on multiple ports of each host on that segment.
As the name implies, the goal of an access attack is to gain access to a system or a network. Having gained access, the user can perform many different functions. These functions fall into three distinct categories:
• Interception: If the unauthorized user can capture traffic going from the source to the destination, that user can store the data for later use. The data might be anything crossing the network segment connected to the sniffer (including confidential data such as personnel records, payroll, or research and development projects). If network management data is crossing the network, it is possible to acquire passwords for specific components and take control of that equipment. For example, this is why it is so important to use Secure Shell (SSH) over Telnet for device management. The methods used for intercepting traffic vary but usually require physical connectivity with the network. The most effective way to protect your sensitive data is to save it in an encrypted format or to send it through an encrypted connection. The encryption prevents the intruder from being able to read the data. Figure 2-1 and Figure 2-2 show how interceptions can occur.
Figure 2-1. A Computer Physically Connected Inline to “Sniff” Traffic

Figure 2-2. A Computer Connected Wirelessly to “Sniff” Traffic

• Modification: Having access, the unauthorized user can now alter the resource. This not only includes altering file content, but it also includes system configurations, unauthorized system access, and unauthorized privilege escalation. Unauthorized system access is completed by exploiting vulnerabilities in either the operating system or another application running on that system. Unauthorized privilege escalation refers to a user with a low level but authorized account attempting to gain higher-level or more privileged user account information to raise the unauthorized user’s privilege level. This higher-privilege level then enables the intruder to have greater control of the target system or network. A more network central example includes router and switch spoofing along with Address Resolution Protocol (ARP) poisoning. These different attacks offer the attacker the ability to change a large number of network variables.
• Fabrication: Having access to the target system or network, the unauthorized user can create false objects and introduce them into the environment. This could include altering data or inserting packaged exploits such as a virus, worm, or Trojan horse that can continue to attack the network from within:
• Virus: A computer virus can range from annoying to destructive. It consists of computer code that attaches itself to other software running on the computer. This way, each time the attached software opens, the virus reproduces and can continue to grow until it wreaks havoc on the infected system.
• Worm: A worm is a virus that exploits vulnerabilities on networked systems to replicate itself. A worm scans a network looking for a system with a specific vulnerability. When it finds a host, it copies itself to that system and begins scanning from there, too.
• Trojan horse: A Trojan horse is a program that usually claims to perform one function (such as a game) but does something completely different in addition to the claimed function (such as corrupting the data on your hard disk). Many different types of Trojan horses get attached to systems, and the effects of these programs range from a minor irritation for the user to total destruction of the computer file system. Trojan horses are sometimes used to exploit systems by creating user accounts on systems that enable unauthorized users to gain access or upgrade their privilege level. Some Trojan horses capture data from the host system and send it back to a location where it can be accessed by the attacker. One of the most popular Trojan horses is used on computers to make them part of a botnet. After being compromised, these computers can be used along with others in any number of different attack types including identity theft.
A denial of service (DoS) attack is designed to deny user access to systems or networks. These attacks usually target specific services and attempt to overwhelm them by making numerous requests concurrently. If a system is not protected and cannot react to a DoS attack, it can be easy to overwhelm that system by running scripts that generate multiple requests. It is possible to greatly increase the magnitude of a DoS attack by launching the attack from multiple systems (botnets) against a single target. This practice is referred to as a distributed DoS (DDoS) attack.
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 D, 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 this chapter, noted with the Key Topics icon in the margin. Table 2-2 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:
denial of service (DoS) attacks