Overview of System Center Essentials 2007 from the internal network
More often than not, a DMZ will also be backed up by a honey pot, which is a machine designed to appear as if it has vital information to an organization that may be of interest to a malicious hacker but in reality is merely a trap to isolate the malicious user and iden- tify them in order to prevent access or aid in prosecution. However, there are now certain legal issues in place that have made these less popular.
Almost always, a DMZ is separated from the internal network by a ?rewall, which is a hardware or software device that ?lters packets and determines where they will and will not be allowed to forward based on their origin, destination, 70-680 protocol, and other such information. When designing a perimeter network, you have to take into account the avail- able budget for your network, number of users, redundancy requirements, availability, and scalability. Each of these factors will determine what type of ?rewall you can use and how many of them you can use.
Although it may not be a complete list, Microsoft has listed in its recommendation for perimeter network design a list of possible attacks you will need to plan against in case of network instruction:
Packet sniffers These are applications of hardware that monitor the network at the packet
level for the purpose of exploitation.
IP spoofing This is falsifying an IP address for the purpose of gaining false authorization.Denial-of-service attacks These are attacks that attempt to deny a service from running by compromising the service through constant software or with a hardware attack.
Application layer attacks These are exploitations of software at the application level.
Network reconnaissance This is using detailed information gained by extensive study to
find weak points in the network.
Viruses These are malicious programs designed to penetrate a network and cause adverse
effects.
Firewalls can be either hardware or software and come in many CCNA Exam different shapes, sizes, and capabilities. Microsoft has de?ned ?ve classes of ?rewalls, as outlined in Table 2.5.
ClassType Design Purpose
1 Personal (software) firewall Small, individual users requiring little to no exten-
sive firewall protection
2 Router firewall Small to medium businesses requiring packet-level
routing and inspection NAT
3 Low-end hardware firewall Dedicated firewalls that require little configuration
and can incorporate switch and VPN capabilities
4 High-end hardware firewall High-performance, dedicated firewalls that require
setup and firewall specifications
5 High-end server firewall
Dedicated server-based firewall using both hardware and software procedures to ensure an incredibly fast and secure network