25.12.2014 Views

Analysis and Evaluation of the Windows Event Log - Bill Buchanan

Analysis and Evaluation of the Windows Event Log - Bill Buchanan

Analysis and Evaluation of the Windows Event Log - Bill Buchanan

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Barrie Codona, BSc (Hons) Network Computing, 2007<br />

by <strong>the</strong> data archiving system, <strong>and</strong> also by <strong>the</strong> event viewer when reading <strong>the</strong> contents<br />

<strong>of</strong> <strong>the</strong> event log.<br />

Unfortunately due to time constraints, <strong>the</strong>se components <strong>of</strong> <strong>the</strong> application were not as<br />

fully developed was <strong>the</strong>y could have been. The original design <strong>of</strong> <strong>the</strong> Data Archiving<br />

System specification was to allow for both <strong>of</strong> <strong>the</strong> <strong>Event</strong> <strong>Log</strong>ging Application <strong>and</strong><br />

<strong>Event</strong> Viewer Application to be able to remotely access <strong>the</strong> event log that was stored<br />

on <strong>the</strong> Server, unfortunately <strong>the</strong>re is no support within <strong>the</strong> Server Application to allow<br />

for a remote connection to <strong>the</strong> Server, it will however run on <strong>the</strong> Server without any<br />

problems.<br />

It had been originally planed that <strong>the</strong> encryption between <strong>the</strong> Client <strong>and</strong> Server could<br />

also be done using synchronous encryption with <strong>the</strong> secret key being exchanged using<br />

asynchronous encryption. The communications that both <strong>the</strong> Client <strong>and</strong> Server use is<br />

only asynchronous encryption; this will obviously cause problems with <strong>the</strong><br />

performance.<br />

Also, <strong>the</strong> Server does not run in a finite state, that is after a Client has terminated its<br />

connection to <strong>the</strong> Server, <strong>the</strong> Server application will shutdown. It could have been<br />

written so that <strong>the</strong> Server returns back to its original listening state.<br />

Ano<strong>the</strong>r unachieved goal <strong>of</strong> <strong>the</strong> <strong>Event</strong> Viewer Application was for it to be able to<br />

display a list <strong>of</strong> all <strong>the</strong> events that have happened <strong>and</strong> for it to allow <strong>the</strong> user to be able<br />

to browse for a specific event.<br />

Apart from <strong>the</strong>se minor short comings <strong>the</strong> overall concept <strong>of</strong> having an <strong>Event</strong> <strong>Log</strong>ger<br />

that securely stores its <strong>Event</strong> <strong>Log</strong>s <strong>of</strong>f site using a remote connection has been<br />

achieved. If time permits a maintenance phase could be used to try <strong>and</strong> address some<br />

<strong>of</strong> <strong>the</strong>se issues.<br />

50

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

Saved successfully!

Ooh no, something went wrong!