Anton's Log Management 'Worst Practices'
8 likes5,275 views
The document outlines common pitfalls in log management practices, emphasizing the importance of proper planning and execution to avoid negative outcomes. It details a series of 'worst practices' that organizations often fall into, such as poor vendor selection and inadequate infrastructure preparation. The author advocates for thorough understanding and research on log management systems to ensure successful implementation and compliance with regulations.
Anton's Log Management 'Worst Practices'
- 1. Log Management “ Worst Practices” Anton Chuvakin, Ph.D., GCIH, GCFA Chief Logging Evangelist LogLogic, Inc Mitigating Risk. Automating Compliance.
- 2. Outline Are you convinced: why log management? Hey, why not just ignore the logs, as usual ! How to do log management WRONG – an idiot’s guide Planning Purchasing Deploying Running Conclusions
- 3. Log Data Overview Audit logs Transaction logs Intrusion logs Connection logs System performance records User activity logs Various alerts and other messages Firewalls/intrusion prevention Routers/switches Intrusion detection Servers, desktops, mainframes Business applications Databases Anti-virus VPNs What logs? From Where?
- 4. Why Log Management? Threat protection and discovery Incident response Forensics , “e-discovery” and litigation support Regulatory compliance Internal policies and procedure compliance Internal and external audit support IT system and network troubleshooting IT performance management
- 5. Log Management Mandate and Regulations Regulations Require LMI SOX GLBA FISMA JPA NIST 800-53 Capture audit records Regularly review audit records for unusual activity and violations Automatically process audit records Protect audit information from unauthorized deletion Retain audit logs PCI HIPAA SLAs Mandates Demand It PCI : Requirement 10 and beyond Logging and user activities tracking are critical Automate and secure audit trails for event reconstruction Review logs daily Retain audit trail history for at least one year COBIT ISO ITIL COBIT 4 Provide audit trail for root-cause analysis Use logging to detect unusual or abnormal activities Regularly review access, privileges, changes Verify backup completion ISO17799 Maintain audit logs for system access and use, changes, faults, corrections, capacity demands Review the results of monitoring activities regularly and ensure the accuracy of logs Controls Require it “ Get fined, Get Sanctioned” “ Lose Customers, Reputation, Revenue or Job” “ Get fined, Go To Jail”
- 6. Also: NIST 800-92 “This publication seeks to assist organizations in understanding the need for sound computer security log management. It provides practical, real-world guidance on developing, implementing, and maintaining effective log management practices throughout an enterprise. “
- 7. Log Management Process Files, syslog, other Immutable Logs Secure Share Collect SNMP, Email, etc Alert Search, Report and Analytics Store Search Report Make Conclusions “ As needed “ basis
- 8. So, You Decided to Acquire a LM Tool … What’s next? What do you want, specifically? How to choose a product? How not to screw it up? How to make sure that it goes smoothly, now and later? Overall, how to be wildly happy … with your log management purchase?
- 9. What is a “Worst Practice”? As opposed to the “ best practice ” it is … What the losers in the field are doing today A practice that generally leads to disastrous results , despite its popularity
- 10. Log Management Project Lifecycle Determine the need Define scope of log management Select and evaluate the vendor Run proof of Concept – POC Deploy (in phases) Run the tool Expand deployment
- 11. 1. Determine the Need WP1: Skip this step altogether – just buy something “ John said that we need a correlation engine” “ I know this guy who sells log management tools …” WP2: Define the need in general “ We need, you know, manage logs and stuff” Questions : Real-time? Platform? Appliance? Service? Correlation? Indexing? RDBMS vs files? Volume of logs? Agents? Collectors? Connectors? Users? Your use cases?
- 12. Case Study A – Just Buy a SIEM! Medium-sized financial company New CSO comes in from a much larger organization “We need a SIEM! ASAP!” Can you spell “boondoggle? Lessons learned: which problem did we solve? Huh!? None?
- 13. 2. Define scope WP3: Postpone scope until after the purchase “ The vendor says ‘it scales’ so we will just feed ALL our logs” Windows, Linux, i5/OS, OS/390, Cisco – send’em in! WP4: Assume you will be the only user of the tool “ Steak holders”? What’s that? Common consequence: two or more similar tools are bought Forgetting that logs are useful to many people for many reasons …
- 14. Case Study B: “We Use’em All” SANS Log Management Summit 2006 Vendors X, Y and Z claim “Big Finance” as a customer How can that be? Well, different teams purchased different products … About $2.3m wasted on tools that do the same!
- 15. 3. Initial vendor selection WP5: Choose by price alone Ignore hardware, extra modules, training, service, support, etc costs “OMG, this tool is 30% cheaper. And it is only twice as bad. ” Advanced version : be suckered by the vendor’s TCO and ROI “formulas” WP6: Choose by relationship or “PowerPoint power” “We got it with the latest router purchase…”
- 16. 4. Vendor evaluation and POC WP7: Don’t ask for and don’t check references “Our environment is unique” WP8: Don’t do a POC “We can save time!” “We can just choose the best product, right?” “The vendor said it works just peachy ” WP9: If doing a POC, let vendor dictate how OR ignore what the vendor says “Windows? Sure, we will test on Windows!” “ Proof of concept!? Why prove what we already know! ”
- 17. Case Study C: Performance-Shmerformance Retail organization deciding between two log management products, A and B Vendor A: “We scale like there is no tomorrow” Vendor B: “We scale like we invented scaling” “Can you prove it?!” Results : Vendor A claims 75,000 MPS, dies at 2300 (!) Vendor B claims 75,000 MPS, runs at 85000 (!!) <- LogLogic
- 18. 5. Deployment WP10: Expect The Vendor To Write Your Logging Policy OR Ignore Vendor Recommendations “ Tell us what we need – tell us what you have” forever… WP11: Unpack the boxes and go! “ Coordinating with network and system folks is for cowards!” Do you know why LM projects take months sometimes? WP12: Don’t prepare the infrastructure “ Time synchronization? Pah, who needs it” WP13: Ignore legal team Pain …
- 19. Case Study D: Shelfware Forever! Financial company gets a SIEM tool after many months of “evaluations” Vendor SEs deploy it One year passes by A new CSO comes in; looks for what is deployed Finds a SIEM tool – which database contains exactly 53 log records (!) It was never connected to a production network…
- 20. 6. Running the Tool WP14: Deploy Everywhere At Once “ We need log management everywhere!” WP15: “Save Money” on Vendor Support Contract “ We Have to Pay 18% for What? ” WP16: Ignore Upgrades “ It works just fine – why touch it?” WP17: Training? They said it is ‘ intuitive ’! “’ A chance to “save” more money here? Suuure.”
- 21. Case Study E: Intuitive? To Me It Isn’t! A major retailer procures a log management tool from an integrator A classic “high-level” sales, golf and all “Intuitive UI” is high on the list of criteria The tool is deployed in production Security engineers hate it – and don’t touch it Simple: UI workflow doesn’t match what they do every day
- 22. 7. Expanding Deployment WP18: Don’t Bother With A Product Owner “We all use it – we all run it (=nobody does)” WP19: Don’t Check For Changed Needs – Just Buy More of the Same “We made the decision – why fuss over it?” WP20: If it works for 10, it will be OK for 10,000 “1,10,100, …, 1 trillion – they are just numbers”
- 23. Case Study F: Today - Datacenter, Tomorrow … Oops! Log management tool is tested and deployed at two datacenters – with great success! PCI DSS comes in; scope is expanded to wireless systems and POS branch servers The tool is prepared to be deployed in 410 (!) more locations “ Do you think it will work?” - “Suuuuure!”, says the vendor Security director resigns …
- 24. Conclusions – Serious ! Turn ON logging! Learn about logging and log management Read NIST 800-92 and other guides; do the research! Match what you need with what they have Not doing it as a key source of PAIN Plan carefully – and plan your planning too Work WITH the vendor – not ‘against’, not ‘without’, not ‘for’ Final word : do big IT projects have “shortcuts” to easy and effortless success – what are they?
- 25. Thank You for Attending! Dr Anton Chuvakin, GCIH, GCFA Chief Logging Evangelist LogLogic, Inc http://www.chuvakin.org See www.info-secure.org for my papers, books, reviews, etc and other security and logging resources; check my blog at www.securitywarrior.org
Editor's Notes
- #2: Not LOGGING worst practices