|< Day Day Up >|
The information in logfiles can be extremely rich but unfortunately sometimes the sheer amount of information can complicate analysis. Data rates of several gigabytes of audit information are not uncommon for a large company, especially if network transaction information is being logged. While many methods exist to make this information storable , making it analyzable and applicable for routing monitoring (and not only as a postmortem) is another story. Having logs from multiple machines collected in one place increases the overall volume but simplifies both day-to-day maintenance and incident response, due to higher log accessibility. More effective audit, secure storage, and possibilities for analysis across multiple computing platforms are some of the advantages of centralized logging. In addition, secure and uniform log storage might be helpful if an intruder is prosecuted based on log evidence. In this case, careful documentation of the log-handling procedure might be needed.
While Unix log centralization can easily be achieved with standard syslog, "syslog replacements " do a better job. Log centralization (also called aggregation ) serves many important purposes within the enterprise. On the one hand, it is more secure ”an intruder would need to hack one more or maybe even several more servers to erase his tracks. On the other hand, it is also more convenient ”the administrator simply needs to connect to one machine to look at all logfiles from the entire network. But there are many problems with log aggregation, the most important of which is the incredible amount of log information.
|< Day Day Up >|