Connect and Protect Networks and Network Security
Connect and Protect Networks and Network Security
Next, you can review the format of an IP version 4 (IPv4) packet and review a
detailed graphic of the packet header. An IPv4 packet is made up of two sections,
the header and the data:
An IPv4 header format is determined by the IPv4 protocol and includes the IP
routing information that devices use to direct the packet. The size of the IPv4
header ranges from 20 to 60 bytes. The first 20 bytes are a fixed set of information
containing data such as the source and destination IP address, header length, and
total length of the packet. The last set of bytes can range from 0 to 40 and consists
of the options field.
The length of the data section of an IPv4 packet can vary greatly in size. However,
the maximum possible size of an IPv4 packet is 65,535 bytes. It contains the
message being transferred over the internet, like website information or email text.
There are 13 fields within the header of an IPv4 packet:
Version (VER): This 4 bit component tells receiving devices what protocol the
packet is using. The packet used in the illustration above is an IPv4 packet.
IP Header Length (HLEN or IHL): HLEN is the packet’s header length. This value
indicates where the packet header ends and the data segment begins.
Type of Service (ToS): Routers prioritize packets for delivery to maintain quality
of service on the network. The ToS field provides the router with this information.
Total Length: This field communicates the total length of the entire IP packet,
including the header and data. The maximum size of an IPv4 packet is 65,535
bytes.
Identification: For IPv4 packets that are larger than 65, 535 bytes, the packets are
divided, or fragmented, into smaller IP packets. The identification field provides a
unique identifier for all the fragments of the original IP packet so that they can be
reassembled once they reach their destination.
Flags: This field provides the routing device with more information about whether
the original packet has been fragmented and if there are more fragments in transit.
Fragmentation Offset: The fragment offset field tells routing devices where in the
original packet the fragment belongs.
Time to Live (TTL): TTL prevents data packets from being forwarded by routers
indefinitely. It contains a counter that is set by the source. The counter is
decremented by one as it passes through each router along its path. When the TTL
counter reaches zero, the router currently holding the packet will discard the packet
and return an ICMP Time Exceeded error message to the sender.
Protocol: The protocol field tells the receiving device which protocol will be used
for the data portion of the packet.
Header Checksum: The header checksum field contains a checksum that can be
used to detect corruption of the IP header in transit. Corrupted packets are
discarded.
Source IP Address: The source IP address is the IPv4 address of the sending
device.
Destination IP Address: The destination IP address is the IPv4 address of the
destination device.
Options: The options field allows for security options to be applied to the packet if
the HLEN value is greater than five. The field communicates these options to the
routing devices.
Difference between IPv4 and IPv6
In an earlier part of this course, you learned about the history of IP addressing. As
the internet grew, it became clear that all of the IPv4 addresses would eventually
be depleted; this is called IPv4 address exhaustion. At the time, no one had
anticipated how many computing devices would need an IP address. IPv6 was
developed to mitigate IPv4 address exhaustion and other related concerns.
One of the key differences between IPv4 and IPv6 is the length of the addresses.
IPv4 addresses are made of four decimal numbers, each ranging from 0 to 255.
Together they span numeric, made of 4 bytes, and allow for up to 4.3 billion
possible addresses. IPv4 addresses are made up of four strings and the numbers
range from 0 to 255. An example of an IPv4 address would be: 198.51.100.0. IPv6
addresses are made of eight hexadecimal numbers consisting of four hexadecimal
digits, Together, they span made up of 16 bytes, and allow for up to 340
undecillion addresses (340 followed by 36 zeros). An example of an IPv6 address
would be: 2002:0db8:0000:0000:0000:ff21:0023:1234.
There are also some differences in the layout of an IPv6 packet header. The IPv6
header format is much simpler than IPv4. For example, the IPv4 Header includes
the IHL, Identification, and Flags fields, whereas the IPv6 does not. The IPv6
header only introduces the Flow Label field, where the Flow Label identifies a
packet as requiring special handling by other IPv6 routers.
Terms and definitions from Course 3, Module 1
Bandwidth: The maximum data transmission capacity over a network, measured by
bits per second
Cloud computing: The practice of using remote servers, application, and network
services that are hosted on the internet instead of on local physical devices
Cloud network: A collection of servers or computers that stores resources and data
in remote data centers that can be accessed via the internet
Data packet: A basic unit of information that travels from one device to another
within a network
Hub: A network device that broadcasts information to every device on the network
Internet Protocol (IP): A set of standards used for routing and addressing data
packets as they travel between devices on a network
Internet Protocol (IP) address: A unique string of characters that identifies the
location of a device on the internet
Local Area Network (LAN): A network that spans small areas like an office
building, a school, or a home
Media Access Control (MAC) address: A unique alphanumeric identifier that is
assigned to each physical device on a network
Modem: A device that connects your router to the internet and brings internet
access to the LAN
Network: A group of connected devices
Open systems interconnection (OSI) model: A standardized concept that describes
the seven layers computers use to communicate and send data over the network
Packet sniffing: The practice of capturing and inspecting data packets across a
network
Port: A software-based location that organizes the sending and receiving of data
between devices on a network
Router: A network device that connects multiple networks together
Speed: The rate at which a device sends and receives data, measured by bits per
second
Switch: A device that makes connections between specific devices on a network by
sending and receiving data between them
TCP/IP model: A framework used to visualize how data is organized and
transmitted across a network
Transmission Control Protocol (TCP): An internet communication protocol that
allows two devices to form a connection and stream data
User Datagram Protocol (UDP): A connectionless protocol that does not establish a
connection between devices before transmissions
Wide Area Network (WAN): A network that spans a large geographic area like a
city, state, or country.
Module 02
Network Protocols: A set of rules used by two or more devices on a network to
describe the order of delivery and the structure of the data.
Transmission Control Protocol: An internet communications protocol that allows
two devices to form connection and stream data.
Handshaking: Verifying both the devices before transmission is known as
Handshaking and TCP does this job.
Address Resolution Protocol: A network protocol used to determine the MAC
address of the next router or device on the path.
Hyper Text Transfer Protocol Secure: A network protocol that provides a secure
method of communication between clients and website servers.
Domain Name Systems: A network protocol that translates internet domain names
into IP Addresses.
Overview of network protocols
A network protocol is a set of rules used by two or more devices on a network to
describe the order of delivery and the structure of data. Network protocols serve as
instructions that come with the information in the data packet. These instructions
tell the receiving device what to do with the data. Protocols are like a common
language that allows devices all across the world to communicate with and
understand each other.
Even though network protocols perform an essential function in network
communication, security analysts should still understand their associated security
implications. Some protocols have vulnerabilities that malicious actors exploit. For
example, a nefarious actor could use the Domain Name System (DNS) protocol,
which resolves web addresses to IP addresses, to divert traffic from a legitimate
website to a malicious website containing malware. You’ll learn more about this
topic in upcoming course materials.
Three categories of network protocols
Network protocols can be divided into three main categories: communication
protocols, management protocols, and security protocols. There are dozens of
different network protocols, but you don’t need to memorize all of them for an
entry-level security analyst role. However, it’s important for you to know the ones
listed in this reading.
Communication protocols
Communication protocols govern the exchange of information in network
transmission. They dictate how the data is transmitted between devices and the
timing of the communication. They also include methods to recover data lost in
transit. Here are a few of them.
Transmission Control Protocol (TCP) is an internet communication protocol that
allows two devices to form a connection and stream data. TCP uses a three-way
handshake process. First, the device sends a synchronize (SYN) request to a server.
Then the server responds with a SYN/ACK packet to acknowledge receipt of the
device's request. Once the server receives the final ACK packet from the device, a
TCP connection is established. In the TCP/IP model, TCP occurs at the transport
layer.
User Datagram Protocol (UDP) is a connectionless protocol that does not establish
a connection between devices before a transmission. This makes it less reliable
than TCP. But it also means that it works well for transmissions that need to get to
their destination quickly. For example, one use of UDP is for internet gaming
transmissions. In the TCP/IP model, UDP occurs at the transport layer.
Hypertext Transfer Protocol (HTTP) is an application layer protocol that provides
a method of communication between clients and website servers. HTTP uses port
80. HTTP is considered insecure, so it is being replaced on most websites by a
secure version, called HTTPS. However, there are still many websites that use the
insecure HTTP protocol. In the TCP/IP model, HTTP occurs at the application
layer.
Domain Name System (DNS) is a protocol that translates internet domain names
into IP addresses. When a client computer wishes to access a website domain using
their internet browser, a query is sent to a dedicated DNS server. The DNS server
then looks up the IP address that corresponds to the website domain. DNS
normally uses UDP on port 53. However, if the DNS reply to a request is large, it
will switch to using the TCP protocol. In the TCP/IP model, DNS occurs at the
application layer.
Management Protocols
The next category of network protocols is management protocols. Management
protocols are used for monitoring and managing activity on a network. They
include protocols for error reporting and optimizing performance on the network.
Simple Network Management Protocol (SNMP) is a network protocol used for
monitoring and managing devices on a network. SNMP can reset a password on a
network device or change its baseline configuration. It can also send requests to
network devices for a report on how much of the network’s bandwidth is being
used up. In the TCP/IP model, SNMP occurs at the application layer.
Internet Control Message Protocol (ICMP) is an internet protocol used by devices
to tell each other about data transmission errors across the network. ICMP is used
by a receiving device to send a report to the sending device about the data
transmission. ICMP is commonly used as a quick way to troubleshoot network
connectivity and latency by issuing the “ping” command on a Linux operating
system. In the TCP/IP model, ICMP occurs at the internet layer.
Security Protocols
Security protocols are network protocols that ensure that data is sent and received
securely across a network. Security protocols use encryption algorithms to protect
data in transit. Below are some common security protocols.
Hypertext Transfer Protocol Secure (HTTPS) is a network protocol that provides a
secure method of communication between clients and website servers. HTTPS is a
secure version of HTTP that uses secure sockets layer/transport layer security
(SSL/TLS) encryption on all transmissions so that malicious actors cannot read the
information contained. HTTPS uses port 443. In the TCP/IP model, HTTPS occurs
at the application layer.
Secure File Transfer Protocol (SFTP) is a secure protocol used to transfer files
from one device to another over a network. SFTP uses secure shell (SSH),
typically through TCP port 22. SSH uses Advanced Encryption Standard (AES)
and other types of encryption to ensure that unintended recipients cannot intercept
the transmissions. In the TCP/IP model, SFTP occurs at the application layer.
SFTP is used often with cloud storage. Every time a user uploads or downloads a
file from cloud storage, the file is transferred using the SFTP protocol.
Note: The encryption protocols mentioned do not conceal the source or destination
IP address of network traffic. This means a malicious actor can still learn some
basic information about the network traffic if they intercept it.