12.07.2015 Views

Journal of Emerging Technologies in Web Intelligence Contents

Journal of Emerging Technologies in Web Intelligence Contents

Journal of Emerging Technologies in Web Intelligence Contents

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

112 JOURNAL OF EMERGING TECHNOLOGIES IN WEB INTELLIGENCE, VOL. 2, NO. 2, MAY 2010IV. IMPLEMENTATIONThe proposed architecture has been implemented <strong>in</strong>Red Hat L<strong>in</strong>ux environment. Our architecture does notemphasis on underly<strong>in</strong>g technology used by host based<strong>in</strong>trusion detection system to detect <strong>in</strong>trusion. Rather thanconstruct a HIDS from scratch, we decided to leverage anHIDS with<strong>in</strong> current implementation <strong>of</strong> our architecture.The two hypotheses that underlie this dissertation arepractical <strong>in</strong> nature. First, they <strong>in</strong>tend to show that it isfeasible to protect HIDS us<strong>in</strong>g proposed architecture.Second, proposed architecture does not affect systemperformance adversely. Therefore, an implementationwas a center po<strong>in</strong>t for the development <strong>of</strong> this dissertationand was used both for practical verification <strong>of</strong> the<strong>in</strong>tended features <strong>of</strong> the architecture and for aid<strong>in</strong>g <strong>in</strong>reason<strong>in</strong>g about and experiment<strong>in</strong>g with itscharacteristics.V. NEW PROCESSES PROPOSED INARCHITECTUREPractically MonitorIDS process (<strong>in</strong>troduced <strong>in</strong> ourproposed architecture) has implemented with two subprocesses :1. MonitorProcesses2. MonitorFilesTo ensure that MoitorIDS processes live forever werun these processes as system processes. When theadversary tries to kill this process kernel automaticallyrestarts it. A respawn labeled entry related to theseprocesses has been written <strong>in</strong> system file ‘\etc\<strong>in</strong>ittab’ torun these processes as system processes.MonitorProcesses process ensures that all processesrelated to OSSEC are always runn<strong>in</strong>g. If it found anyprocess dead it restarts the process correspond<strong>in</strong>g HIDSprocess. MonitorProcesses also prevents modificationrelated to these entries <strong>in</strong> ‘\etc\<strong>in</strong>ittab’ file. In case <strong>of</strong>deletion or modification <strong>of</strong> these entries from‘\etc\<strong>in</strong>ittab’ file, this process writes new entries. Thepurpose <strong>of</strong> MonitorFiles sub-process is to protect HIDSfiles from unauthorized modification. If it detects anymodification or deletion, it restores the victim file withgenu<strong>in</strong>e file from backup directory.VI. AFFECTS ON PERFORMANCE OF THESYSTEMTo evaluate the affects on the performance on systemfollow<strong>in</strong>g steps are carried out :1. To evaluate the affects on execution time <strong>of</strong> basicL<strong>in</strong>ux commands, some time measurementswere carried out.2. System Monitor<strong>in</strong>g Utility was used to check thechanges <strong>in</strong> utilization <strong>of</strong> processor due toprocesses related to our proposed architecture.A. Affects on execution <strong>of</strong> L<strong>in</strong>ux commandsFor this purpose, most <strong>of</strong> the time measurements werecarried out regard<strong>in</strong>g basic L<strong>in</strong>ux commands (ps, f<strong>in</strong>d,who). Each Command was executed 100 times and allcorrespond<strong>in</strong>g 100 execution times were recorded. Theaverage <strong>of</strong> these tim<strong>in</strong>gs has been considered as theAverage Execution Time(ATE). Average Execution Time(AET) was calculated twice. In first run, we calculateexecution time (ATE1) without runn<strong>in</strong>g processes (suchas MonitorIDS process) related to our architecture. And<strong>in</strong> second run we calculate execution time (ATE2) whileprocesses related to our architecture were runn<strong>in</strong>g.Table-1 Average Execution Time <strong>in</strong> millisecondsCommand ps –ef f<strong>in</strong>d / >/dev/nullNumber <strong>of</strong> systemcalls 536 10055(a) Average Execution Time(AET 1) 25.9 63.1(time required to executeon mach<strong>in</strong>e while not runn<strong>in</strong>gprocesses related to proposedarchitecture )(b)Average Execution Time(AET 2) 30.1 65.5(time required to executeon mach<strong>in</strong>e while processesrelated to proposed architectureare runn<strong>in</strong>g )Overhead relative to (a) 0.16% 0.03%Table 1 represents average execution time (<strong>in</strong>milliseconds) and correspond<strong>in</strong>g overhead. Very smallfraction <strong>of</strong> time was observed as overhead due to theMonitorIDS process.B. Changes <strong>in</strong> processor utilization due MonitorIDSProcessMonitorIDS process is a very lightweight processthat works <strong>in</strong> iterative manner. In each iteration checksthe state (process term<strong>in</strong>ated or runn<strong>in</strong>g) <strong>of</strong> HIDSprocesses and <strong>in</strong>tegrity <strong>of</strong> HIDS related files. Oneiteration requires approximately .001 Second time forexecution.Figure 3 represents the CPU utilization graph whenMonitorIDS process was not runn<strong>in</strong>g. Because theprocessor <strong>in</strong> use is Dual Core two l<strong>in</strong>es representsutilizations <strong>of</strong> processor. As shown <strong>in</strong> the graph CPUutilization is between 0% to 20%. Most <strong>of</strong> the time theCPU utilization is below 10%.Figure 3: Graph show<strong>in</strong>g CPU utilization while MonitorIDS not runn<strong>in</strong>g© 2010 ACADEMY PUBLISHER

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

Saved successfully!

Ooh no, something went wrong!