Discussion Locked

Syslog

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello...I made a small computer on my network the syslog. Now it perpetually prints pages and pages of authentication errors and tons of error messages, of which I am having problems interpreting...is there an easier way to read or interpret these messages? I need something to prove to auditors that I am reviewing possible intrusion detections, but this continuous feed printer printing all day has got to GO!

Please help...

thanks
pmharlan

1 reply

by erikdr

A) As this is a Windows area I suppose you mean the Windows eventlog instead of (Unix) syslog. However the concepts are 99% the same, it's just that the solutions I mention will go with Windows examples.

B) Why do you automatically print all logs?
Having them on disk for analysis might be enough...

C) Generally spoken, to catch intrusions inside Windows and Win apps does require some level of auditing/logging which will, unavoidingly, create a level of 'noise'. Filtering out the signal from the noise 'on eyesight'is by no means easy and can sometimes become impossible.
So it might become time to make (scripting) or buy filtering tools which angle out the signal in the streams of noise. Commercial tools can become quite expensive and are known under the 'security incident management' header, and even with them you do need to customise their OOTB scripts quite a lot. Makeware will be based on e.g. VBScript and its eventlog reading commands.

Hope this helps a bit,

- The Netherlands

This discussion is closed to new replies.