Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ... Military Communications and Information Technology: A Trusted ...

22.01.2015 Views

352 Military Communications and Information Technology... has mechanism that allows the Decision Module to efficiently execute multiple queries over the data streams in order to perform event correlation. The result of a correlation process is an intermediate event that is further processed by CLIPS rule engine [12]. CLIPS uses ontology that describes broad range of network security aspects (we use ‘’FCDS ontology’’ developed in our project). CLIPS engine identifies whenever some attacks or malicious network events have been discovered. The information describing the network incident and reconfiguration procedures (Common Decision Rule – CDR) are sent to Translator. Moreover, detailed information in human readable format are generated and visualized to network administrators via DM GUI. Figure 3. UML diagram of DM Data received from network sensors is arranged in streams. Each stream is built of multiple tuples (events). Each tuple, depending on sensor type, may have different schema. Borealis allows to process streams in order to correlate information coming from different sources and to detect network incidents more efficiently. The query that is executed over the multiple streams consists of operators. There are different kinds of operators provided by the Borealis engine that allow for aggregation, filtering and joining data coming from different streams. According to Figure 2. only intermediate events are matched with the knowledge stored in the ontology. The intermediate events are obtained via the Borealis query that is executed over the streams of a network events. Their names, types and schemas are maintained in the ontology. Each intermediate event received by CLIPS rule engine is considered as attack symptom and as such is matched with knowledge in the ontology in order infer the most probable attack [13]. The example of symptom matching is graphically presented in Figure 4. When the symptoms are received by CLIPS rule engine the most probable attacks are inferred. However one symptom could match several attacks, therefore CLIPS is responsible for computing the probability score and alerting about these attacks, for which the calculated score exceeds the detection threshold.

Chapter 4: Information Assurance & Cyber Defence 353 Figure 4. Matching sensor events (symptoms) with knowledge in ontology [13] If the attack is detected it may have accompanying (described in ontology) general decision rule that will minimize consequences. There are several pre-defined general reactions such as blocking, traffic redirection (e.g. to a trap or back to the attacker), administrator notification or service disabling. The ontology defines different security policies (what reactions are recommended/allowed in the particular domain) for different domains, therefore CLIPS additionally matches this knowledge with appropriate general reaction rule to avoid policy violation. Each Decision Module can react to network events and attacks by sending information (CDR) to the Translator element and then to RE. The output information from DMs is the CDR describing attack symptoms (information about network events) and particular reaction rule to be applied by reaction elements. Translator has the knowledge about its subnet capabilities and can access the necessary reaction elements (e.g. firewalls, filters or IDS). Reaction elements can be reconfigured by Translator in order to apply commands sent by the Decision Module. All Decision Modules within the federation can also interact with each other and exchange security information. Particularly information about network incidents, like attack in one domain, may be sent to different Decisions Modules in order to block the attacker before the consequent attack takes place on another domain. Communication between domains and Decision Modules is based on P2P (Peerto-Peer) in order to increase communication resiliency and enable data replication. Moreover, P2P approach allows the proposed system to overcome IP addressing issues and minimize the configuration cost. The proposed approach allows the system to have redundant communication channels between Decision Modules. Particularly, when a physical connection is under attack or is congested, the communication packets still have an opportunity to reach the destination DM using a different path. The used communication channels are encrypted using the SSL algorithm. This allows to protect the communication against the packet sniffing (by third

352 <strong>Military</strong> <strong>Communications</strong> <strong>and</strong> <strong>Information</strong> <strong>Technology</strong>...<br />

has mechanism that allows the Decision Module to efficiently execute multiple<br />

queries over the data streams in order to perform event correlation. The result<br />

of a correlation process is an intermediate event that is further processed by<br />

CLIPS rule engine [12]. CLIPS uses ontology that describes broad range of network<br />

security aspects (we use ‘’FCDS ontology’’ developed in our project). CLIPS<br />

engine identifies whenever some attacks or malicious network events have been<br />

discovered. The information describing the network incident <strong>and</strong> reconfiguration<br />

procedures (Common Decision Rule – CDR) are sent to Translator. Moreover,<br />

detailed information in human readable format are generated <strong>and</strong> visualized to<br />

network administrators via DM GUI.<br />

Figure 3. UML diagram of DM<br />

Data received from network sensors is arranged in streams. Each stream is built<br />

of multiple tuples (events). Each tuple, depending on sensor type, may have different<br />

schema. Borealis allows to process streams in order to correlate information<br />

coming from different sources <strong>and</strong> to detect network incidents more efficiently.<br />

The query that is executed over the multiple streams consists of operators. There<br />

are different kinds of operators provided by the Borealis engine that allow for aggregation,<br />

filtering <strong>and</strong> joining data coming from different streams.<br />

According to Figure 2. only intermediate events are matched with the knowledge<br />

stored in the ontology. The intermediate events are obtained via the Borealis<br />

query that is executed over the streams of a network events. Their names, types<br />

<strong>and</strong> schemas are maintained in the ontology. Each intermediate event received by<br />

CLIPS rule engine is considered as attack symptom <strong>and</strong> as such is matched with<br />

knowledge in the ontology in order infer the most probable attack [13].<br />

The example of symptom matching is graphically presented in Figure 4.<br />

When the symptoms are received by CLIPS rule engine the most probable attacks<br />

are inferred. However one symptom could match several attacks, therefore CLIPS<br />

is responsible for computing the probability score <strong>and</strong> alerting about these attacks,<br />

for which the calculated score exceeds the detection threshold.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!