of 4


Published on January 2017 | Categories: Documents | Downloads: 13 | Comments: 0



As one of essential elements in network and information system security, firewalls
have been widely deployed in defending suspicious traffic and unauthorized access
to Internet-based enterprises. Sitting on the border between a private network and
the public Internet, a firewall examines all incoming and outgoing packets based
on security rules. To implement a security policy in a firewall, system
administrators define a set of filtering rules that are derived from the organizational
network security requirements. Firewall policy management is a challenging task
exacerbated by the continuous evolution of network and system environments. For
instance, Al-Shaer and Hamed [1] reported that their firewall policies contain
anomalies even though several administrators including nine experts maintained
those policies. In addition, Wool [2] recently inspected firewall policies collected
from different organizations and indicated that all examined firewall policies have
security flaws. The process of configuring a firewall is tedious and error prone.
Therefore, effective mechanisms and tools for policy management are crucial to
the success of firewalls. Recently, policy anomaly detection has received a great
deal of attention [1], [3], [4], [5]. Corresponding policy analysis tools, such as
Firewall Policy Advisor [1] and FIREMAN [5], with the goal of detecting policy
detecting pairwise anomalies in firewall rules. FIREMAN can detect anomalies
among multiple rules by analyzing the relationships between one rule and the
collections of packet spaces derived from all preceding rules. However, FIREMAN
also has limitations in detecting anomalies [3]. For each firewall rule, FIREMAN
only examines all preceding rules but ignores all subsequent rules when

rules, but cannot accurately indicate all rules involved in an anomaly. On the other
hand, due to the complex nature of policy anomalies, system administrators are
often faced with a more challenging problem in resolving anomalies, in particular,
resolving policy conflicts. An intuitive means for a system administrator to resolve
policy conflicts is to remove all conflicts by modifying the conflicting rules.
However, changing the conflicting rules is significantly difficult, even impossible,
in practice from many aspects. First, the number of conflicts in a firewall is
potentially large, since a firewall policy may consist of thousands of rules, which
are often logically entangled with each other. Second, policy conflicts are often
very complicated. One rule may conflict with multiple other rules, and one conflict
may be associated with several rules. Besides, firewall policies deployed on a
network are often maintained by more than one administrator, and an enterprise
firewall may contain legacy rules that are designed by different administrators.
Thus, without a priori knowledge on the administrators’ intentions, changing rules
will affect the rules’ semantics and may not resolve conflicts correctly.
Furthermore, in some cases, a system administrator may intentionally introduce
certain overlaps in firewall rules knowing that only the first rule is important. In
reality, this is a commonly used technique to exclude specific parts from a certain
action, and the proper use of this technique could result in a fewer number of
compact rules [5]. In this case, conflicts are not an error, but intended, which
would not be necessary to be changed. Since the policy conflicts in firewalls
always exist and are hard to be eliminated, a practical resolution method is to
identify which rule involved in a conflict situation should take precedence when
multiple conflicting rules (with different actions) can filter a particular network
packet simultaneously. To resolve policy conflicts, a firewall typically implements
a first-match resolution mechanism based on the order of rules. In this way, each

packet processed by the firewall is mapped to the decision of the first rule that the
packet matches. However, applying the first-match strategy to cope with policy
conflicts has limitations. When a conflict occurs in a firewall, the existing first
matching rule may not be a desired rule that should take precedence with respect to
conflict resolution. In particular, the existing first matching rule may perform
opposite action to the rule which should be considered to take precedence. This
situation can cause severe network breaches such as permitting harmful packets to
sneak into a private network, or dropping legal traffic which in turn could
encumber the availability and utility of network services. Obviously, it is necessary
to seek a way to bridge a gap between conflict detection and conflict resolution
with the first-match mechanism in firewalls. In this paper, we represent a novel
anomaly management framework for firewalls based on a rule-based segmentation
technique to facilitate not only more accurate anomaly detection but also effective
segment associated with a unique set of firewall rules accurately indicates an
risk assessment of protected networks and the intention of policy definition.
Besides, a more effective redundancy elimination mechanism is provided in our
framework, and our experimental results show that our redundancy discovery
mechanism can achieve approximately 70 percent improvement compared to
traditional redundancy detection approaches [1], [6]. Moreover, the outputs of prior
policy analysis tools [1], [5] are mainly a list of possible anomalies, which does not
give system administrators a clear view of the origination of policy anomalies.
Since information visualization technique [7] enables users to explore, analyze,

reason, and explain abstract information by taking advantage of their visual
cognition, our policy analysis tool adopts an information visualization technique to
facilitate policy analysis. A grid based visualization approach is introduced to
represent policy anomaly diagnosis information in an intuitive way, enabling an
efficient anomaly management.1 In addition, we implement a visualization-based
firewall anomaly management environment (FAME) based on our approach. To
evaluate the practicality of our tool, our extensive experiments deal with a set of
real-life firewall policies.

Sponsor Documents

Or use your account on DocShare.tips


Forgot your password?

Or register your new account on DocShare.tips



Back to log-in