Lesson 12: Implementing Secure Network Access Protocols Flashcards
Dynamic Host Configuration Protocol (DHCP)
- provides an automatic method for network address allocation
- key point about DHCP is that only one server should be running
- DHCP broadcasts are typically limited to the local subnet
- more than one DHCP server may be running for fault tolerance, as long as they are all configured correctly, and address pools don’t overlap
- best defenses against attacks on DHCP are accomplished by general network security best practices:
- Use scanning and intrusion detection to pick up suspicious activity.
- Enable logging and review the logs for suspicious events.
- Disable unused ports and perform regular physical inspections to ensure that unauthorized devices are not connected via unused jacks.
- Enable DHCP snooping on switch access ports to prevent the use of unauthorized DHCP servers.
Domain Name System (DNS)
resolves host names and domain labels to IP addresses
DNS spoofing
- an attack that compromises the name resolution process
- one use of DNS spoofing is to facilitate a pharming attack
- in a pharming attack, the attacker compromises the process of DNS resolution in some way to replace the valid IP address for a trusted website such as mybank.com with the attacker’s IP address
HOSTS
before DNS was developed (in the 1980s), name resolution took place using a text file named HOSTS. Each name:IP address mapping was recorded in this file and system administrators had to download the latest copy and install it on each Internet client or server manually. Even though all name resolution now functions through DNS, the HOSTS file is still present and most operating systems check the file before using DNS. Its contents are loaded into a cache of known name:IP mappings and the client only contacts a DNS server if the name is not cached
DNS server cache poisoning (or pollution)
- another redirection attack, but instead of trying to subvert the name service used by the client, it aims to corrupt the records held by the DNS server itself
- typical attack would proceed as follows:
1. The server in grommet.com wants to find an address in widget.com. It queries the root and .com name servers and gets an address for the name server for widget.com.
2. The attacker spoofs the name server for widget.com. To do this, the attacker must compromise the genuine widget.com name server through some sort of DoS attack. The attacker just needs to ensure that his or her malicious DNS responds to grommet.com’s queries before the legitimate one.
3. The attacker spoofs responses to the grommet.com server and poisons its cache, meaning that traffic for widget.com from grommet.com gets directed to the attacker’s IP address.
DNS footprinting
- means obtaining information about a private network by using its DNS server to perform a zone transfer (all the records in a domain) to a rogue DNS or simply by querying the DNS service, using a tool such as nslookup or dig
- to prevent this, you can apply an Access Control List to prevent zone transfers to unauthorized hosts or domains, to prevent an external server from obtaining information about the private network architecture
- DNS is a critical service that should be configured to be fault tolerant. DoS attacks are hard to perform against the servers that perform Internet name resolution, but if an attacker can target the DNS server on a private network, it is possible to seriously disrupt the operation of that network
DNS Security Extensions (DNSSEC)
- help to mitigate against spoofing and poisoning attacks by providing a validation process for DNS responses
- with DNSSEC enabled, the authoritative server for the zone creates a “package” of resource records (called an RRset) signed with a private key (the Zone Signing Key). When another server requests a secure record exchange, the authoritative server returns the package along with its public key, which can be used to verify the signature.
cybersquatting
- an attack where an adversary acquires a domain for a company’s trading name or trademark, or perhaps some spelling variation thereof
- domain name must be re-registered every year
- following attacks all exploit the domain name registration process in some way:
- Domain hijacking—an adversary gains control over the registration of a domain name, allowing the host records to be configured to IP addresses of the attacker’s choosing. This might be accomplished by supplying false credentials to the domain registrar when applying for a new domain name or re-registering an existing one
- Typosquatting—misspelled domains can be profitable depending on the frequency that users enter the misspelled name (for example, visiting amazoon.com or amazun.com). This is also referred to as URL hijacking
- Kiting—a domain name can be registered for up to five days without paying for it. Kiting means that the name is continually registered, deleted, then re-registered
- Tasting—this is the registration of a domain to test how much traffic it generates within the five-day grace period; if the domain is not profitable, the registration is never completed
Simple Network Management Protocol (SNMP)
- widely used framework for management and monitoring
- consists of an SNMP monitor and agents:
• The agent is a process (software or firmware) running on a switch, router, server, or other SNMP-compatible network device.
- This agent maintains a database called a Management Information Base (MIB) that holds statistics relating to the activity of the device (for example, the number of frames per second handled by a switch). The agent is also capable of initiating a trap operation where it informs the management system of a notable event (port failure, for instance). The threshold for triggering traps can be set for each value. Device queries take place over port 161 (UDP); traps are communicated over port 162 (also UDP).
• The SNMP monitor (a software program) provides a location from which network activity can be overseen
Network Time Protocol (NTP)
- provides a transport over which to synchronize these time dependent applications. NTP works over UDP on port 123
- Top-level NTP servers (stratum 1) obtain the Coordinated Universal Time (UTC) from a highly accurate clock source, such as an atomic clock
- Lower tier servers then obtain the UTC from multiple stratum 1 servers and sample the results to obtain an authoritative time
- most organizations will use one of these stratum 2 servers to obtain the time for use on the LAN
remote access
- means that the user’s device does not make a direct cabled or wireless connection to the network. The connection occurs over or through an intermediate network, usually a public Wide Area Network
- historically, remote access might have used analog modems connecting over the telephone system or possibly a private link (a leased line). These days, most remote access is implemented as a Virtual Private Network (VPN), running over the Internet
tunneling
technology used when the source and destination computers are on the same logical network but connected via different physical networks
VPN concentrator
clients connect to a VPN gateway (a VPN-enabled router, or sometimes called a VPN concentrator) on the local network. This is the “telecommuter” model, allowing home-workers and employees working in the field to connect to the corporate network. The VPN clients will connect over the Internet
site-to-site VPN
connects two or more local networks, each of which runs a VPN gateway (or router/VPN concentrator). Where remote access VPN connections are typically initiated by the client, a site-to-site VPN is configured to operate automatically. The gateways exchange security information using whichever protocol the VPN is based on. This establishes a trust relationship between the gateways and sets up a secure connection through which to tunnel data. Hosts at each site do not need to be configured with any information about the VPN. The routing infrastructure at each site determines whether to deliver traffic locally or send it over the VPN tunnel.
Point-to-Point Tunneling Protocol (PPTP)
legacy protocols such as the Point-to-Point Tunneling Protocol (PPTP) have been deprecated because they do not offer adequate security