{"id":201,"date":"2011-07-04T17:29:00","date_gmt":"2011-07-04T17:29:00","guid":{"rendered":"https:\/\/belayclientstaging.zone\/securityeverafter\/2011\/07\/04\/critical-control-6-maintenance-monitoring-and-analysis-of-audit-logs\/"},"modified":"2011-07-04T17:29:00","modified_gmt":"2011-07-04T17:29:00","slug":"critical-control-6-maintenance-monitoring-and-analysis-of-audit-logs","status":"publish","type":"post","link":"https:\/\/securityeverafter.com\/critical-control-6-maintenance-monitoring-and-analysis-of-audit-logs\/","title":{"rendered":"Critical Control 6: Maintenance, Monitoring, and Analysis of Audit Logs"},"content":{"rendered":"
Logs are the single most important place to look when it is time to answer the question “what just happened”. The more systems you have, the more impractical it is to review at system logs individually. To facilitate this, configure each system to send its logs to a centralized log review and retention solution. This will put all of the logs in one place and also keeps another copy in an alternate location.<\/p>\n
SANS provides a Log Vendor Listing<\/a> that includes popular vendors. Martin Holste wrote his own Enterprise Log Search and Archive<\/a> (ELSA) solution.<\/p>\n A good tool not only allows you to search through the logs, but also lets you schedule recurring searches and alert when something is found. The following examples of reports and alerts can serve as the foundation of your indications and warnings of attack or misconfiguration.<\/p>\n\n