Implementing and Running SIEM: Approaches and Lessons

  • 6,318 views
Uploaded on

Implementing and Running SIEM: Approaches and Lessons

Implementing and Running SIEM: Approaches and Lessons

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
6,318
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
15

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Security Information and Event Management = security-relevant log collection, aggregation, normalization, retention; context data collection; analysis (correlation, prioritization); presentation (reporting, visualization); related workflow and relevant content.Log management = comprehensive log collection, aggregation, original log retention; analysis; presentation (search, reporting, visualization); related workflow and relevant content.
  • Security Information and Event Management = relevant log collection, aggregation, normalization, retention; context data collection; analysis (correlation, prioritization); presentation (reporting, visualization); related workflow and relevant content.Also: WHY SIEM – too many IDS alerts!
  • SIEM use casesSOC – full real-time monitoringMini-SOC / ”morning after”Remote monitoring + investigationsCompliance status reporting

Transcript

  • 1. Implementing and RunningSIEM: Approaches and Lessons
    Dr. Anton Chuvakin
    Security Warrior Consulting
    www.securitywarriorconsulting.com
    St Andrews, Scotland, UK
    November 11-13, 2009
  • 2. Outline
    Brief: What is SIEM?
    Implementation Choices: Build/Outsource/Buy
    Detailed Analysis of Choices
    SIEM and Log Management “Worst Practices”
    Conclusions
  • 3. SIEM and LM Defined
    Security Information and Event Management = relevant log collection, aggregation, normalization, retention; context data collection; analysis (correlation, prioritization); presentation (reporting, visualization); related workflow and relevant content.
    Log Management = comprehensive log collection, aggregation, original log retention; analysis; presentation (search, reporting, visualization); related workflow and relevant content.
  • 4. SIEM vs LM
    SIEM = SECURITY information and event management
    vs
    LM = LOG management
  • 5. What SIEM MUST Have?
    Log and Context Data Collection
    Normalization
    Correlation (“SEM”)
    Notification/alerting (“SEM”)
    Prioritization (“SEM”)
    Reporting (“SIM”)
    Security role workflow
  • 6. SIEM Use Cases
    Security Operations Center (SOC)
    RT views, analysts 24/7, chase alerts
    Mini-SOC / “morning after”
    Delayed views, analysts 1/24, review and drill-down
    “Automated SOC” / alert + investigate
    Configure and forget, investigate alerts
    Compliance status reporting
    Review reports/views weekly/monthly
  • 7. Secret to SIEM Magic!
  • 8. APPROACHES
    Build / Buy / Outsource
  • 9. How Do You Do It?
    Now that you are convinced about SIEM…
    Outsource
    Built
    Buy
    Combined strategies are also possible
  • 10. Outsource
    Risks
    Somebody else will worry about your problems!
    Requirements not met
    SLA risks and lost control of data
    Volume and log access challenges
    Advantages
    • Somebody else will worry about your problems!
    • 11. Likely, no need to run any equipment in house
    • 12. Less staff needed
    • 13. Management will like it
  • What to Be Aware Of?
    Will all your log and context data be going to the MSSP?
    Does MSSP have skills to analyze your site-specific logs?
    Can you still take a peek at your original logs?
    Do you need to call for that?
    Can you access them directly?
    Cloud SIEM?
  • 14. Build
    Risks
    Ongoing maintenance will KILL you
    No support, apart from you
    Does it pass the “bus test”?
    Handling log volume
    Will it scale with you?
    Advantages
    • Likely will get exactly what you want (*)
    • 15. You can do things that no vendor has
    • 16. Choose platform, tools, methods
    • 17. No up front cost
    • 18. Its fun to do! 
  • Open-Source Tools to the Rescue!
    Log collection
    Syslog-ng, kiwi, Snare, LASSO, Apache2syslog, logger, etc
    Secure centralization
    Stunnel, ssh, OpenSSL
    Pre-processing
    LogPP
    Storage
    MySQL or design your own file-based storage
    Analysis – a tough one! 
    OSSEC and OSSIM for [some] intelligence
    Swatch, logwatch, logsentry, other match-n-bug scripts
  • 19. Example: How to Deal with A Trillion Log Messages?
    How to analyze a trillion (~1000 billions) of log messages for some specific goal?
    Hundreds of terabytes (1/2 of a petabyte …) of data
    Which tool to pick?
    “Sorry, buddy, you are writing some code here!”
    See loganalysis list or my blog for details about this case
  • 20. Buy
    Advantages
    • “Cash and carry” – pay and get a “solution”
    • 21. Support for log sources
    • 22. Ongoing improvements, support
    • 23. “Have a face(s) to scream at!”
    Risks
    “Cash and carry” – pay and get a tool you need to use now
    Skilled staff needed to get value out of a purchase
    Requirements not met
    Vendor longevity
  • 24. Questions to Discuss With Your Vendor
    Are you collecting and aggregating 100% of all log data from all data sources on the network?
    Are your logs transported and stored securely?
    Are there packaged reports that suit your needs? Can you create the needed reports to organize collected log data quickly?
    Can you set alerts on anything in the logs?
    Are you looking at log data on a daily basis? Can you prove that you are?
    Can you perform fast, targeted searches for specific data?
    Can you contextualize log data (comparing application, network and database logs) when undertaking forensics and other operational tasks?
    Can you readily prove that security, change management,and access control policies are in use and up to date?
    Can you securely share log data with other applications and users?
  • 25. Combined Strategies: Often the Best…
    Buy + Build: great idea – enhance vendor tools with internal custom development OR combine vendor tools with open-source tools (build, then buy or the opposite)
    Buy + Outsource: split the work with an MSSP team and retain more control
    Combined approaches mitigate some of the risks, but at a cost (see TANFL principle )
  • 26. Build + Buy: Surprisingly Effective!
    Capture buy advantages:
    Support
    Ongoing improvement
    Routine log analysis tasks done by vendor!
    Capture build advantages:
    Build analysis you want
    Present the data you want to the people that need it
    Critical SIEM tasks done by you!
  • 27. Finally, How to Choose?
    Breadth/depth of project requirements
    Just how unusual you are?
    Unique needs or volumes
    Size of organization
    Available resources
    Money, development talent
    Organization culture and management support
    Deployed hardware and software
    Run any Tandem? 
  • 28. WORST PRACTICES
    Lessons Learned: SIEM “Worst Practices”
  • 29. So, You Decided to Acquire a SIEM
    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?
    How to be happy with your SIEM?
  • 30. 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
  • 31. SIEM or LM 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
  • 32. 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, ‘do SIEM’ and stuff” 
    Questions: Real-time? Platform? Appliance? Service? Correlation? Indexing? RDBMS vs files? Volume of logs? Agents? Collectors? Connectors? Users? Youruse cases?
  • 33. 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?
  • 34. 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
    “Steakholders”? What’s that? 
    Common consequence: two or more
    simiilartools are bought
  • 35. Case Study B: “We Use’em All”
    At SANS Log Management Summit 200X…
    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!
  • 36. 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…”
  • 37. 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!”
  • 38. 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” 
    Q: “Can you prove it?!”
    A: Results:
    Vendor A claims 75,000 MPS, dies at 2300 (!)
    Vendor B claims 75,000 MPS, runs at 85000 (!!)
  • 39. 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 …
  • 40. 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…
  • 41. 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.”
  • 42. 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
  • 43. 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”
  • 44. 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 …
  • 45. Conclusions – Serious!
    Turn ON logging!
    Learn about SIEM and log management
    Read NIST 800-92 and other industry document; do the research!
    Read some of the stuff I wrote on SIEM too 
    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’
  • 46. Final Word
    Final word: do big IT projects have “shortcuts” to easy and effortless success – what are they?
    The answer is …
    NO!
  • 47. Questions
    Dr. Anton Chuvakin
    Email:anton@chuvakin.org
    Google Voice: 510-771-7106
    Site:http://www.chuvakin.org
    Blog:http://www.securitywarrior.org
    LinkedIn:http://www.linkedin.com/in/chuvakin
    Consulting: www.securitywarriorconsulting.com
    Twitter:@anton_chuvakin
  • 48. More on Anton
    Book author: “Security Warrior”, “PCI Compliance”, “Information Security Management Handbook”, “Know Your Enemy II”, “Hacker’s Challenge 3”, etc
    Conference speaker: SANS, FIRST, GFIRST, ISSA, CSI, Interop, many, many others worldwide
    Standard developer: CEE, CVSS, OVAL, etc
    Community role: SANS, Honeynet Project, WASC, CSI, ISSA, OSSTMM, InfraGard, ISSA, others
    Past roles: Researcher, Security Analyst, Strategist, Evangelist, Product Manager, Consultant
  • 49. Security Warrior Consulting Services
    Logging and log management policy
    Develop logging policies and processes, log review procedures, workflows and periodic tasks as well as help architect those to solve organization problems
    Plan and implement log management architecture to support your business cases; develop specific components such as log data collection, filtering, aggregation, retention, log source configuration as well as reporting, review and validation
    Customize industry “best practices” related to logging and log review to fit your environment, help link these practices to business services and regulations
    Help integrate logging tools and processes into IT and business operations
    Content development
    Develop of correlation rules, reports and other content to make your SIEM and log management product more useful to you and more applicable to your risk profile and compliance needs
    Create and refine policies, procedures and operational practices for logging and log management to satisfy requirements of PCI DSS, HIPAA, NERC, FISMA and other regulations
    More at www.SecurityWarriorConsulting.com