Dr. Aly, O.
Computer Science
Introduction
The purpose of this discussion is to discuss and analyze the type of devices and methods which are required to be implemented and employed in an enterprise, and the reasons for such devices and methods. The discussion also addresses the location of these devices within the network to provide intrusion detection.
Intrusion Detection System (IDS)
The IDS is a system which is responsible for detecting unauthorized access or attacks against systems and networks. IDS can verify, itemize and characterize threats from outside and inside the network. Most IDSs are programmed to react certain ways in a specific situation. Event notification and alerts are critical to the IDS. They inform administrators and security professional when and where attacks are detected (Abernathy & McMillan, 2016).
The most common method to classify IDS is based on its information source: network-based (NIDS) or host-based (HIDS). The NIDS is the most common IDS to monitor the network traffic on a local network segment. The network interface card must be operating in a promiscuous mode to monitor the traffic on the network segment. The NIDS can only monitor the network traffic. It cannot monitor the internal activity which occurs within a system, such as an attack against a system which is carried out by logging on to the local terminal of the system. The NIDS is affected by a switched network because the NIDS only monitors a single network segment (Abernathy & McMillan, 2016).
The HIDS monitors traffic on a single system. The primary role of the HIDS is to protect the system on which it is installed. The HIDS uses information from the operating system audit trails and system logs. The detection capabilities of the HIDS are limited by how complete the audit logs and system logs are (Abernathy & McMillan, 2016).
The implementation of IDS is divided into four categories. The first category is the “signature-based” which analyzes traffic and compares it to attack or state patterns, and reside within the IDS database. The signature-based IDS is also referred to as a misuse-detection system. This type of IDS is popular despite the fact that it can only recognize attacks as compared with its database and is only as effective as the signatures provided. The signature-based IDS requires frequent updates. The signature-based IDS has two types: the pattern-matching, and stateful matching. The pattern-matching signature-based IDS compares traffic to a database of attack patterns. It carries out specific steps when it detects traffic which matches an attack pattern. The stateful-matching signature-based IDS records the initial operating system states. Any changes to the system state which violate the defined rules result in an alert or notification being sent (Abernathy & McMillan, 2016).
The anomaly-based IDS is another type of IDS, which analyzes the traffic and compares it to normal traffic to determine whether said traffic is a threat. This type of IDS is also referred to as behavior-based or profile-based system. The limitation of this type of IDS is that any traffic outside of expected norms is reported, resulting in more false positives than signature-based IDS. There are three types of anomaly-based IDS. The statistical anomaly-based, protocol anomaly-based, and traffic anomaly-based. The statistical anomaly-based IDS samples the live environment to record activities. The more accurate a profile will be built, the longer the IDS is in operation. However, the development of a profile which will not have a large number of false positive can be difficult and time-consuming. The threshold for activity deviation is important in this IDS. When the threshold is too low, the result is a false positive. However, when the threshold is too high, the result is false negatives. The protocol anomaly-based IDS knows the protocols which it will monitor. A profile of normal usage is built and compared to activity. The last type of the anomaly-based is the traffic anomaly-based IDS which tracks traffic pattern changes. Using this types allows all future traffic patterns to be compared to the sample (Abernathy & McMillan, 2016).
The rule-based and heuristic-based IDS is another type of IDS which is described to be an expert system using a knowledge base, inference engine, and rule-based programming. The knowledge is configured as rules. The traffic and the data are analyzed, and the rules are applied to the analyzed traffic. The inference engine uses its intelligent software to learn, and if the characteristics of an attack are discovered and met, alerts or notification trigger. This IDS type is also referred to as IF/THEN or expert system. The last type of IDS is application-based which analyzes transaction log files for a single application. This type of IDS is provided as part of the application or can be purchased as an add-on.
Additional tools can be employed to complement IDS such as vulnerability analysis system, honeypots, and padded cells. The honeypots are systems which are configured with reduced security to entice attackers so that administrators can learn about attack techniques. Padded cells are special hosts to which an attacker is transferred during an attack.
IDS monitors the system behavior and alert on potentially malicious network traffic. It can be set inline, attached to a spanning port of a switch, or make use of a hub in place of a switch. The underlying concept is to allow access to all packets that are required to be monitored by the IDS. Tuning IDS is important because of a balancing act between these four event categories: true positive, false positive, true negative and false negative. Table 1 shows the relationship between these points, adapted from (Robel, 2015).

Table 1. Relationship of Event Categories (Robel, 2015).
The ideal IDS tuning maximize instances of events categorized in the cells with a shaded background. True positive occur when the system alerts on intrusion attempts or other malicious activity, while false negative is of a null situation but are important nonetheless. The false negative is comprised of the system failing to alert on malicious traffic, while false positive is alerting on benign activity. There are few methods to connect IDS to capture and monitor traffic. IDS needs to collect network traffic for analysis. Three main methods can be applied to IDS: IDS using hub or switch spanning port, IDS using network tap, and IDS connected inline. Figure 1 illustrates the IDS on the edge of a network or zone (Robel, 2015).

Figure 1. IDS on the Edge of a Network or Zone. Adapted from (Robel, 2015)
Intrusion Prevention System (IPS)
The IPS is responsible for preventing attacks. When an attack begins, the IPS takes action to prevent and contain the attack. The IPS can either be network-based IPS or host-based IPS. IPS can also be signature-based or anomaly-based, or rate-based metric which analyzes the volume of traffic and the type of traffic. IPS is more costly than the IDS because of the added security of preventing attacks versus detecting attacks. Moreover, running IPS is more of an overall performance load than running IDS (Abernathy & McMillan, 2016).
A firewall is commonly used to provide a layer of security. However, the firewall has a limitation, as most firewalls can only block based on IP addresses or port. In contrast, Network Intrusion Prevention System (NIPS) can use signatures designed to detect and defend from specific attacks such as DoS. This feature is advantages for sites hosting web servers. IPS have also been known to block buffer overflow type attacks and can be configured to report on network scans which typically signal a potential attack. The advanced usage of IPS may not drop malicious packets but rather redirect specific attacks to a honeypot (Robel, 2015).
The IPS is connected inline. This inline requirement enables IPS to drop selected packets, and defend against an attack before it takes hold of the internal network. IPS connected inline to capture the traffic is illustrated in Figure 2, adapted from (Robel, 2015).

Figure 2. IPS on the border of a network or zone (Robel, 2015).
References
Abernathy, R., & McMillan, T. (2016). CISSP Cert Guide: Pearson IT Certification.
Robel, D. (2015). SANS Institute InfoSec Reading Room.






