21.03.2013 Views

Problem - Kevin Tafuro

Problem - Kevin Tafuro

Problem - Kevin Tafuro

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.

tion with the logging service. When log entries are made, only a small amount of<br />

information is stored; this information includes a timestamp, an integer value representing<br />

the log message, and possibly some additional “metadata” that makes up the<br />

variable portion of the log message. The full textual message is never stored; instead,<br />

the DLLs that have been registered with the logging service provide the message on<br />

demand when the logs are viewed.<br />

Logging to CD-R<br />

On the surface, the idea of logging to read-only media sounds like a good idea, but in<br />

practice, it does not usually work out very well. There are a surprising number of<br />

serious problems with logging to CD-R. In fact, we recommend against it; we feel<br />

that the problems greatly outweigh the benefits.<br />

One of the primary problems with logging to CD-R is the lack of hardware and software<br />

support for doing so. In order to write log entries out to CD-R in real time,<br />

writing must be done in what is known as packet-writing mode. Packet-writing mode<br />

allows data to be written to the CD-R incrementally instead of all at once. Most<br />

available hardware does not support packet-writing mode for CD-R. As a direct consequence<br />

of this, most operating systems do not have support for it either.<br />

Perhaps the most obvious problem with logging to CD-R is that it requires constant<br />

monitoring and manual intervention. CD-R media is small, holding only roughly<br />

660MB. A busy system could fill this up quite quickly, so someone must keep a close<br />

eye on the logging system, being prepared to swap media when necessary. In most<br />

environments, having someone around to swap CDs is not an effective use of<br />

resources. More importantly, if a busy system can fill up the media quickly under<br />

normal conditions, imagine what an attacker could do!<br />

Other problems with packet-writing mode are performance and reliability. Because<br />

operating in packet-writing mode is slow, a busy system is very likely going to fall well<br />

behind the activity that is going on in real time. Reliability is also an issue. If an error<br />

of some kind occurs, there is a high probability that any data written to the CD-R will<br />

be lost. In addition, if an attacker were to reboot the system before the CD-R was<br />

finalized, all of the data on that CD-R would be lost.<br />

If you still want to log to CD-R in “real time,” be sure that you don’t rely solely on<br />

CD-R copies. You should also keep local copies on the system’s hard drive and log to<br />

a network server if you can.<br />

Signing and encrypting log entries<br />

Signing and encrypting entries made to log files can help ensure the integrity of the<br />

logs that are generated. Ideally, the logging server would be responsible for performing<br />

the cryptographic operations on all entries submitted to it, but neither syslog nor<br />

the Windows logging service provide built-in support for either signing or encrypt-<br />

736 | Chapter 13: Other Topics<br />

This is the Title of the Book, eMatter Edition<br />

Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.

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

Saved successfully!

Ooh no, something went wrong!