Nis Unit 3 Notes
Nis Unit 3 Notes
Network Attacks
1. Malware:
Malicious software which is specifically designed to disrupt, damage, or gain
authorized access to a computer system. Much of the malware out there today is
self-replicating. Once it infects one host, from that host it seeks entry into other
hosts over the Internet, and from the newly infected hosts, it seeks entry into yet
more hosts. In this manner, self-replicating malware can spread exponentially
fast.
2. Virus:
A malware which requires some form of user’s interaction to infect the user’s
device. The classic example is an e-mail attachment containing malicious
executable code. If a user receives and opens such an attachment, the user
inadvertently runs the malware on the device.
3. Worm:
A malware which can enter a device without any explicit user interaction. For
example, a user may be running a vulnerable network application to which an
attacker can send malware. In some cases, without any user intervention, the
application may accept the malware from the Internet and run it, creating a worm.
4. Botnet:
A network of private computers infected with malicious software and controlled as
a group without the owners’ knowledge, e.g. to send spam.
7. Packet sniffer:
A passive receiver that records a copy of every packet that flies by is called a
packet sniffer. By placing a passive receiver in the vicinity of the wireless
transmitter, that receiver can obtain a copy of every packet that is transmitted.
These packets can contain all kinds of sensitive information, including passwords,
social security numbers, trade secrets, and private personal messages. Some of the
best defenses against packet sniffing involve cryptography.
8. IP Spoofing:
The ability to inject packets into the Internet with a false source address is known
as IP spoofing, and is but one of many ways in which one user can masquerade as
another user. To solve this problem, we will need end-point authentication, that is,
a mechanism that will allow us to determine with certainty if a message originates
from where we think it does.
9. Man-in-the-Middle Attack:
As the name indicates, a man-in-the-middle attack occurs when someone between
you and the person with whom you are communicating is actively monitoring,
capturing, and controlling your communication transparently. For example, the
attacker can re-route a data exchange. When computers are communicating at low
levels of the network layer, the computers might not be able to determine with
whom they are exchanging data.
11. Phishing:
The fraudulent practice of sending emails purporting to be from reputable
companies in order to induce individuals to reveal personal information, such as
passwords and credit card numbers.
Intrusion detection consists of procedures and systems that identify system intrusions.
Information security intrusion detection systems (IDSs) became commercially available
in the late 1990s. An IDS works like a burglar alarm in that it detects a violation and
activates an alarm. This alarm can be a sound, a light or other visual signal, or a silent
warning, such as an e-mail message or pager alert. Intrusion detection system (IDS) is a
system capable of automatically detecting an intrusion into an organization’s
networks or host systems and notifying a designated authority.
Need for Intrusion Monitoring and Detection
The primary purpose of an IDS is to identify and report intrusions promptly.
Notification is crucial for the effectiveness of an IDS; without it, the system serves
no purpose.
IDSs help protect assets even when networks and systems are exposed to
vulnerabilities or unable to respond to rapidly changing threats.
1. Signature-Based Detection
Signature-based technology is widely used because many attacks have clear and distinct
signatures:
• Footprinting and fingerprinting activities use Internet Control Message Protocol
(ICMP), DNS querying, and e-mail routine analysis.
• Exploits use a specific attack sequence designed to take advantage of a
vulnerability to gain access to a system.
• DoS and DDoS attacks, during which the attacker tries to prevent the normal
usage of a system, overload the system with requests so that its ability to process
them efficiently is compromised or disrupted.
A potential problem with the signature-based approach is that new attack patterns
must continually be added to the IDS’s database of signatures; otherwise, attacks that
use new strategies will not be recognized and might succeed. Another weakness of the
signature based method is that a slow, methodical attack involving multiple events
might escape detection.
The only way signature-based detection can resolve this vulnerability is to collect and
analyze data over longer periods of time, a process that requires substantially greater
data storage capability and additional processing capacity. However, detection in real
time becomes extremely unlikely. Similarly, using signature-based detection to
compare observed events with known patterns is relatively simplistic; the
technologies that deploy it typically cannot analyze some application or network
protocols, nor can they understand complex communications.
2. Anomaly-Based Detection
The advantage of anomaly-based detection is that the IDS can detect new types of
attacks because it looks for abnormal activity of any type. Unfortunately, these
systems require much more overhead and processing capacity than signature-based
IDSs because they must constantly compare patterns of activity against the baseline.
Another drawback is that these systems may not detect minor changes to system
variables and may generate many false positives. If the actions of network users or
systems vary widely, with periods of low activity interspersed with periods of heavy
packet traffic, this type of IDS may not be suitable because the dramatic swings will
almost certainly generate false alarms. Because of the complexity of anomaly-based
detection, its impact on the overhead computing load of the host computer, and the
number of false positives it can generate. This type of IDS is less commonly used than
the signature-based type.
3. Stateful Protocol Analysis
An IDS extension of this concept is stateful protocol analysis (SPA). SPA uses the
opposite of a signature approach. Instead of comparing known attack patterns against
observed traffic or data, the system compares known normal protocol profiles against
observed traffic.
State table:
A fundamental component of stateful protocol analysis is the state table, also
known as a connection table or stateful inspection table.
This table serves as a repository for maintaining records of active connections
between computers on the network. Key information stored in the state table
includes:
o Source and destination IP addresses: Identifies the communicating parties.
o Source and destination port numbers: Specifies the application or service
associated with the connection.
o Protocol: Indicates the network protocol being used (e.g., TCP, FTP UDP).
o Each entry in the state table represents a unique connection, allowing the
IDS to track the state and progress of ongoing communications.
Event horizon:
In the context of stateful protocol analysis, the "event horizon" refers to the
entire duration of an attack or suspicious activity.
During an attack, the IDS needs to maintain state information consistently to
effectively analyze and respond to malicious behavior.
This involves tracking the progression of the attack from its initiation to its
conclusion, ensuring that no stage of the attack goes unnoticed.
By maintaining state information throughout the event horizon, the IDS can
correlate multiple packets or network events to identify patterns indicative of
an attack.
Timely detection and response during the entire length of the attack are
essential for mitigating potential damage and minimizing the impact on the
network's security.
Stateful protocol analysis approaches:
Traffic rate monitoring
monitoring- If IDSS detects sudden increase in traffic it can stop
and reset all TCP traffic.
Protocol state tracking
tracking- IDS maintains
intains a record of connection’s
connection’ state and
allows packets to pass through if it is an established connection.
Dynamic Application layer protocol analysis- Can identify applications not
using standard ports.
IP packet reassembly
reassembly- Can reassemble fragmented packets to prevent
fragments from passing through to the internal network.
Categories of IDS
IDS in general has three basic types based on its location:
1. Host IDS
2. Network IDS
3. Hybrid IDS
Advantages of HIDS:
Can detect local events on host systems, catching attacks that may bypass
network-based IDS.
Operates directly on the host system, allowing processing of decrypted traffic.
Unaffected by switched network protocols.
Can identify inconsistencies in application and system program usage through
audit log analysis, aiding in Trojan horse detection.
Disadvantages of HIDS:
Require more management effort as they are configured and managed on each
host.
Vulnerable to direct attacks and attacks against the host OS, risking compromise
of HIDS functionality.
Not optimized for detecting multi-host scanning or attacks from non-host network
devices without complex correlation analysis.
Susceptible to some DoS attacks.
Demand large disk space for retaining host OS audit logs, potentially requiring
additional disk capacity.
Impose performance overhead on host systems, potentially reducing system
performance to unacceptable levels.
When examining incoming packets, an NIDS looks for patterns within network traffic
such as large collections of related items of a certain type, which could indicate that a
DoS attack is under way. NIDS can detect many more types of attacks than a host-based
IDS, but it requires a much more complex configuration and maintenance program. An
NIDS is installed at a specific place in the network, such as inside an edge router, where
it is possible to monitor traffic into and out of a particular network segment.
Advantages of NIDS:
Effective network design allows monitoring of large networks with few devices.
NIDSs are passive and can be integrated into existing networks without disrupting
operations.
Typically not directly susceptible to attack, making them difficult for attackers to
detect.
Disadvantages of NIDS:
May struggle to keep up with high network volumes, potentially missing attacks.
Require access to all monitored traffic, which can be challenging in switched
Ethernet networks.
Unable to analyze encrypted packets, reducing effectiveness.
Some types of attacks, like those involving fragmented packets, are challenging
for NIDS to detect.
Characteristics of IDS
1. ID monitors a whole system or just a part of it.
2. ID occurs either during an intrusion or after it.
3. ID can be stealth or openly advertised.
4. If suspicious activity occurs it produces an alarm and keeps logs that can be used for
reports on long term development.
5. Human (administrator )needed for alarm processing.
6. ID systems can produce an alarm and/or produce an automated response.
Role of Router in IDS
Routers play a crucial role in the broader network infrastructure, and they can contribute
to the effectiveness of an Intrusion Detection System (IDS) in several ways:
Logging and Monitoring: Routers often have logging capabilities that record
information about network traffic passing through them. IDS can utilize these
router logs as a data source for detecting and analyzing potential security threats.
High rate of false alarms: False positives, where legitimate activity is incorrectly
flagged as malicious, can overwhelm security teams and reduce trust in IDS alerts,
impacting overall system performance and effectiveness.
Alert Correlation
“Correlating alarms”: Combining the fragmented information contained in the alert
sequences and interpreting the whole flow of alerts.
Functional requirements:
– Modifying alarms
– Suppressing alarms
– Clearing active alarms
– Generating new alarms
– Delaying alarms
Organizations should ensure that all IDS components are secured appropriately.
IDSs are a prime target for attackers. If they can compromise the IDS, they are
then free to conduct unobserved attacks on other systems.
Before evaluating IDS products, organizations should define the requirements that
the products should meet. Knowing what you need in an IDS can prevent
purchasing a product that does not solve the organization’s problems, and can save
time and money in the long haul.
IDS Deployment
As an organization selects an IDS and prepares for implementation, planners must select
a deployment strategy that is based on a careful analysis of the organization’s information
security requirements and that integrates with the existing IT infrastructure while causing
minimal impact. Given the highly technical skills required to implement and configure
IDSs and the imperfection of the technology, great care must be taken when deciding
where to locate the components, both in their physical connection to the network and host
devices and in how they are logically connected to each other.
1. Deploying Network-Based IDSs:
The placement of the sensor agents is critical to the operation of all IDSs, but especially
for NIDSs. NIST recommends the following four locations for NIDS sensors, as
illustrated in Figure.:
Location 1: Behind each external firewall, in the network demilitarized zone (DMZ).
This location has the following characteristics:
The IDS sees attacks that originate from the outside and may penetrate the
network’s perimeter defenses.
The IDS can identify problems with the network firewall policy or performance.
The IDS sees attacks that might target the Web server or FTP server, both of
which commonly reside in this DMZ.
Even if the incoming attack is not detected, the IDS can sometimes recognize
patterns in the outgoing traffic that suggest the server has been compromised.
Location 2: Outside an external firewall. This location has the following characteristics:
The IDS documents the number of attacks originating on the Internet that target
the network.
The IDS documents the types of attacks originating on the Internet that target the
network.
Installation proceeds until all systems are deployed or until the organization
achieves the planned coverage level.
Technicians can install HIDSs on offline systems to develop expertise and identify
problems, while users and managers can learn about HIDS operation through a test
facility connected to the organization's backbone.
The test facility allows HIDSs to process actual network traffic and technicians to
establish a baseline of normal traffic.
Training scenarios can be developed during system testing to help users recognize
and respond to common attacks effectively.
The management team can establish policies for the operation and monitoring of
HIDSs to ensure effective and efficient operation.
Future of IDS
Potential implementation of Artificial Intelligence techniques on alert correlation.
Multilayer perception and Support Vector Machine.
Probabilistic output of these methods support the causal relationships of alerts, which
is helpful for constructing attack scenarios
Fuzzy Cognitive Modelling.
A causal knowledge based reasoning mechanism with fuzzy cognitive modelling is
used to correlate alerts by discovering causal relationships in alert data
Firewalls
A firewall acts as a security guard controlling access between an internal, protected
network and an external, untrusted network based on a given security policy. Firewalls
can be an effective means of protecting a local system or network of systems from
network-based security threats while at the same time affording access to the outside
world via wide area networks and the Internet. A firewall may be implemented in
hardware as a stand-alone “firewall appliance” or in software on a PC. In addition, many
routers support basic firewall functionality. A single firewall may be adequate for small
business and homes. However, in several large enterprises, multiple firewalls are
deployed to achieve defense in depth.
The Need For Firewalls
Information systems in corporations, government agencies, and other organizations have
undergone a steady evolution. Internet connectivity is no longer optional for
organizations. The information and services available are essential to the organization.
While the Internet access provides benefits to the organization, it enables the outside
world to reach and interact with local network assets. This creates a threat to the
organization. While it is possible to equip each workstation and server on the premises
network with strong security features, such as intrusion protection, this may not be
sufficient and in some cases is not cost-effective.
Firewall Characteristics
The following are the design goals for a firewall:
1. All traffic from inside to outside, and vice versa, must pass through the firewall.
This is achieved by physically blocking all access to the local network except via
the firewall.
2. Only authorized traffic, as defined by the local security policy, will be allowed to
pass. Various types of firewalls are used, which implement various types of
security policies.
3. The firewall itself is immune to penetration. This implies the use of a hardened
system with a secured operating system. Trusted computer systems are suitable for
hosting a firewall and often required in government applications.
Types Of Firewall
A firewall can monitor network traffic at a number of levels, from low-level network
packets either individually or as part of a flow, to all traffic within a transport connection,
up to inspecting details of application protocols. The choice of which level is appropriate
is determined by the desired firewall access policy. It can operate as a positive filter,
allowing to pass only packets that meet specific criteria, or as a negative filter, rejecting
any packet that meets certain criteria. Depending on the type of firewall, it may examine
one or more protocol headers in each packet, the payload of each packet, or the pattern
generated by a sequence of packets. In this section, we look at the principal types of
firewalls.
A packet filtering firewall applies a set of rules to each incoming and outgoing IP packet
and then forwards or discards the packet. The firewall is typically configured to filter
packets going in both directions (from and to the internal network).
Source IP address: The IP address of the system that originated the IP packet (e.g.,
192.178.1.1)
Destination IP address: The IP address of the system the IP packet is trying to
reach (e.g., 192.168.1.2)
Source and destination transport-level address: The transport-level (e.g., TCP
or UDP) port number, which defines applications such as SNMP or TELNET
IP protocol field: Defines the transport protocol
Interface: For a firewall with three or more ports, which interface of the firewall
the packet came from or which interface of the firewall the packet is destined for.
The packet filter is typically set up as a list of rules based on matches to fields in the IP or
TCP header. If there is a match to one of the rules, that rule is invoked to determine
whether to forward or discard the packet. If there is no match to any rule, then a default
action is taken.
1. Limited Protection: packet filter firewalls do not examine upper-layer data, they
cannot prevent attacks that employ application-specific vulnerabilities or
functions. For example, a packet filter firewall cannot block specific application
commands; if a packet filter firewall allows a given application, all functions
available within that application will be permitted.
3. Limited Support for Advanced Authentication: Most packet filter firewalls lack
support for advanced user authentication methods, primarily because of their
inability to handle upper-layer functionalities.
4. Vulnerability to Protocol Exploits: Packet filter firewalls are susceptible to attacks
exploiting TCP/IP specification and protocol stack vulnerabilities, such as network
layer address spoofing. They often fail to detect altered OSI Layer 3 addressing
information, which is commonly exploited by intruders to bypass firewall security
controls.
5. Configuration Vulnerabilities: The simplicity of access control decisions in packet
filter firewalls makes them prone to security breaches caused by
misconfigurations. Accidentally allowing traffic types, sources, or destinations
contrary to an organization's security policy is a common risk.
SPI firewalls, also called stateful inspection firewalls, keep track of each network
connection between internal and external systems using a state table. A state table tracks
the state and context of each packet in the conversation by recording which station sent
what packet and when. Like first-generation firewalls, stateful inspection firewalls
perform packet filtering, but they take it a step further. Whereas simple packet-filtering
firewalls only allow or deny certain packets based on their address, a stateful firewall can
expedite incoming packets that are responses to internal requests. If the stateful firewall
receives an incoming packet that it cannot match in its state table, it refers to its Access
Control List (ACL) to determine whether to allow the packet to pass.
The primary disadvantage of this type of firewall is the additional processing required to
manage and verify packets against the state table. Without this processing, the system is
vulnerable to a DoS or DDoS attack. In such an attack, the system receives a large
number of external packets, which slows the firewall because it attempts to compare all
of the incoming packets first to the state table and then to the ACL.
On the positive side, these firewalls can track connectionless packet traffic, such as UDP
and remote procedure calls (RPC) traffic. Some stateful firewalls also keep track of
TCP sequence numbers to prevent attacks that depend on the sequence number, such as
session hijacking. Some even inspect limited amounts of application data for some
well-known protocols like FTP, IM and SIPS commands, in order to identify and track
related connections. Dynamic SPI firewalls keep a dynamic state table to make changes
to the filtering rules within predefined limits, based on events as they happen.
A packet filtering firewall, even with the added functionality of stateful packet
inspection, is still severely limited. It understands the network and transport layer headers
but is indifferent to the application being run. What is needed is a firewall that can
examine the application payload and scan packets for worms, viruses, spam mail, and
inappropriate content.
A special kind of application-level firewall is built using proxy agents. Such a “proxy
firewall” or “application proxy” acts as an intermediary between the client and server.
The client establishes a TCP connection to the proxy and the proxy establishes another
TCP connection with the server. To a client, the proxy appears as the server and to the
sever, the proxy appears as the client. Since there is no direct connection between the
client and server, worms and other malware will not be able to pass between the two,
assuming that the proxy can detect and filter out the malware. Hence, the presence of the
proxy enhances security.
The gateway/proxy can be configured to support only specific features of an
application that the network administrator considers acceptable while denying all
other features.
Application-level gateways tend to be more secure than packet filters. Rather than
trying to deal with the numerous possible combinations that are to be allowed and
forbidden at the TCP and IP level, the application-level gateway need only
scrutinize a few allowable applications. In addition, it is easy to log and audit all
incoming traffic at the application level.
A prime disadvantage of this type of gateway is the additional processing
overhead on each connection. In effect, there are two spliced connections between
the end users, with the gateway at the splice point, and the gateway must examine
and forward all traffic in both directions.
4) Circuit-Level Gateway
A fourth type of firewall is the circuit-level gateway or circuit-level proxy. This can be a
stand-alone system or it can be a specialized function performed by an application-
level gateway for certain applications.
Once the two connections are established, the gateway typically relays TCP
segments from one connection to the other without examining the contents.
The security function consists of determining which connections will be allowed.
A common scenario for employing circuit-level gateways is when the system
administrator has trust in internal users. In such cases, the gateway can be set up to
facilitate application-level or proxy services for inbound connections while using circuit-
level functions for outbound connections. In this configuration, the gateway can incur
the processing overhead of examining incoming application data for forbidden
functions but does not incur that overhead on outgoing data.
Bastion host
It is a system identified by the firewall administrator as a critical strong point in the
network’s security. The Bastion host serves as a platform for an application level and
circuit level gateway.
Common characteristics of a Bastion host are as follows:
The Bastion host hardware platform executes a secure version of its operating
system, making it a trusted system.
Only the services that the network administrator considers essential are installed
on the Bastion host.
It may require additional authentication before a user is allowed access to the
proxy services.
Each proxy is configured to support only a subset of standard application’s
command set.
Each proxy is configured to allow access only to specific host systems.
Each proxy maintains detailed audit information by logging all traffic, each
connection and the duration of each connection.
Each proxy is independent of other proxies on the Bastion host.
A proxy generally performs no disk access other than to read its initial
configuration file.
Each proxy runs on a non-privileged user in a private and secured directory on the
Bastion host.
In this configuration, the firewall consists of two systems: a packet filtering router
and a bastion host.
Typically, the router is configured so that for traffic from the internet, only IP
packets destined for the bastion host are allowed in.
For traffic from the internal network, only IP packets from the bastion host are
allowed out.
The bastion host performs authentication and proxy functions.
This configuration has greater security than simply a packet filtering router or an
application level gateway alone, for two reasons:
o This configuration implements both packet level and application level
filtering, allowing for considerable flexibility in defining security policy.
o An intruder must generally penetrate two separate systems before the
security of the internal network is compromised.
Imagine you have a house with only one entrance, and there's a security guard
stationed there. This security guard checks everyone who enters the house. In this
setup, your house is like your network, and the security guard is your firewall.
The firewall (security guard) inspects all incoming traffic from the internet (people
trying to enter the house) and only allows authorized traffic (people with proper
identification) to pass through to the internal network.
This configuration is called "single-homed" because the firewall has only one
network interface connected to the internal network (your house).
In the previous configuration, if the packet filtering router is compromised, traffic could
flow directly through the router between the internet and the other hosts on the private
network. This configuration physically prevents such a security break.
Now, imagine you have a house with two entrances: one facing the street and
another facing a backyard. There's a security guard stationed at each entrance.
In this setup, one security guard checks incoming traffic from the street (internet),
while the other checks traffic from the backyard (a trusted network, such as your
workplace network).
Both security guards only allow authorized traffic to enter the house, ensuring that
both external and internal traffic meet security requirements.
This configuration is called "dual-homed" because the firewall has two network
interfaces—one connected to the internet and the other to the internal network.
In this configuration, two packet filtering routers are used, one between the bastion host
and internet and one between the bastion host and the internal network. This
configuration creates an isolated sub network, which may consist of simply the bastion
host but may also include one or more information servers and modems for dial-in
capability. Typically both the internet and the internal network have access to hosts on
the screened subnet, but traffic across the screened subnet is blocked.
Imagine you have a house with a front yard, a fence, and a backyard. The front
yard faces the street (internet), the backyard is your internal network, and the
fence is your firewall.
The firewall (fence) separates the front yard (internet) from the backyard (internal
network) and inspects all traffic passing through.
Additionally, there's a guard stationed at the gate of the fence who checks
incoming traffic from the street (internet) before allowing it into the backyard
(internal network).
This configuration creates a "screened subnet" or "demilitarized zone (DMZ)"
between the internet and the internal network, providing an extra layer of security
for servers or services that need to be accessible from the internet while keeping
the internal network protected.
A current extension of IDS technology is the intrusion prevention system (IPS), which
can prevent an intrusion from successfully attacking the organization by means of an
active response. Because we seldom find an IPS that does not also have detection
capabilities, the term intrusion detection and prevention system (IDPS) is commonly
used.
• Intrusion prevention systems are contemplated as augmentation of Intrusion
Detection Systems (IDS) because both IPS and IDS operate network traffic and
system activities for malicious activity.
• IPS typically record information related to observed events, notify security
administrators of important observed events and produce reports.
• Many IPS can also respond to a detected threat by attempting to prevent it from
succeeding. They use various response techniques, which involve the IPS stopping
the attack itself, changing the security environment or changing the attack’s
content.
Types of IPS
There are two main types of IPS:
• Network-Based IPS: A Network-Based IPS is installed at the network perimeter
and monitors all traffic that enters and exits the network.
• Host-Based IPS: A Host-Based IPS is installed on individual hosts and monitors
the traffic that goes in and out of that host.
Why Do You Need an IPS?
An IPS is an essential tool for network security. Here are some reasons why:
• Protection Against Known and Unknown Threats: An IPS can block known
threats and also detect and block unknown threats that haven’t been seen before.
• Real-Time Protection: An IPS can detect and block malicious traffic in real-time,
preventing attacks from doing any damage.
• Compliance Requirements: Many industries have regulations that require the use
of an IPS to protect sensitive information and prevent data breaches.
• Cost-Effective: An IPS is a cost-effective way to protect your network compared
to the cost of dealing with the aftermath of a security breach.
• Increased Network Visibility: An IPS provides increased network visibility,
allowing you to see what’s happening on your network and identify potential
security risks.