Analysis and Evaluation of the Windows Event Log - Bill Buchanan

More documents

Recommendations

Info

Barrie Codona, BSc (Hons) Network Computing, 2007 Figure 35: Updated Client-Server communications 6.4 Experiment 1: Performance This experiment will be used to measure the performance of the application; it will also measure the load that it places on the system. A simple application (see Figure 36) was developed that would poll the processor every 100 milliseconds and return its value as a percentage. This data along with the current system time is then displayed on screen; the system time is used so that the data can be cross referenced to the event log data. An option is given for the user to save this information to a text file, so that it can easily be imported into a spreadsheet application to produce a graphical analysis of the results. 53
Barrie Codona, BSc (Hons) Network Computing, 2007 Figure 36: Processor monitor application First is to create a baseline without any encryption happening, this test will be run to measure the load being placed on the processor when 1,000, 5,000, 10,000 and 20,000 files are being created. Each test will run over a 30 second interval, this will provide ample time to complete the test and will also visually depict the information more clearly. Figures 37, 38, 39 and 40 show these results. As these experiments have been carried out on a quad core processor the pink line represents a single core. 100% 90% 80% Processor Load (%) 70% 60% 50% 40% 30% 20% 10% 0% Load 1 Core 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 48 50 52 54 56 58 60 62 64 66 68 Time (Seconds) Figure 37: Generating 1,000 files with no encryption 54
Page 1 and 2:
Analysis and Evaluation of the Wind
Page 3 and 4: Barrie Codona, BSc (Hons) Network C
Page 53: Barrie Codona, BSc (Hons) Network C
Page 75 and 76: Appendix A: Diary Sheets
Page 77 and 78: NAPIER UNIVERSITY SCHOOL OF COMPUTI
Page 85 and 86: Appendix B: Preliminary Gantt Chart
Page 87 and 88: Nov '07 Dec '07 Jan '08 Feb '08 Mar
Page 89 and 90: C:\Documents and Settings\Barrie\My
Page 95 and 96: Appendix D: Server Application Code
Page 99 and 100: Appendix E: Event Viewer Code
Page 105 and 106:
Appendix G: Processor Monitor Code
Page 107 and 108:
Appendix H: HMAC Brute Force Cracke
Page 109 and 110:
C:\Documents and Settings\Barrie\My
Page 111 and 112:
C:\Documents and Settings\Barrie\My
Page 113 and 114:
Appendix I: Windows Event Log Tests
Page 115 and 116:
Copy Security Log C:\windows\system
Page 117 and 118:
Another look at the Security Log re
Page 119 and 120:
The Event Service is then restarted
Page 121 and 122:
Another look at the ‘c:\windows\s
Page 123 and 124:
CO42019 - Project 4 Computer Name P
Page 125 and 126:
CO42019 - Project 4 Turned off the
Page 127 and 128:
CO42019 - Project 4 And then restar
Page 129 and 130:
CO42019 - Project 4 Modify the ‘l
Page 131 and 132:
CO42019 - Project 4 Project - Week
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
CO42019 - Project 4 As previously d
Page 139 and 140:
CO42019 - Project 4 The screenshot
Page 141 and 142:
CO42019 - Project 4 Displaying the
Page 143 and 144:
CO42019 - Project 4 Modifying the r
Page 145 and 146:
CO42019 - Project 4 Master File Tab
Page 147 and 148:
CO42019 - Project 4 Modify the sect
Page 149 and 150:
CO42019 - Project 4 Sectors 3748520
Page 151 and 152:
CO42019 - Project 4 This now shows
show all

Analysis and Evaluation of the Windows Event Log - Bill Buchanan

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

Delete template?

Save as template?