Log management and compliance: What's the real story? by Dr. Anton Chuvakin
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Log management and compliance: What's the real story? by Dr. Anton Chuvakin

  • 1,598 views
Uploaded on

Title: Log management and compliance: What's the real story? by Dr. Anton Chuvakin...

Title: Log management and compliance: What's the real story? by Dr. Anton Chuvakin

One of the problems in making an Enterprise Content Management (ECM) strategy work with compliance initiatives is that compliance needs accountability at a very granular level. Consequently, IT shops are turning to log management as a solution, with many of those solutions being deployed for the purposes of regulatory compliance. The language however, regarding log management solutions can sometimes be vague which can lead to confusion. This session will lend some clarity to the regulations that affect log management. Topics will include:

Best practices for how to best mesh compliance ECM and compliance strategies with log management
Tips and suggestions for monitoring and auditing access to regulated content, with a focus on Microsoft Sharepoint logging.
An examination of a handful of the regulations affecting how organizations view log management and information security including The Payment Card Industry Data Security Standard (PCI DSS), ISO 27001, The North American Electric Reliability Council (NERC), HIPAA and the HITECH Act.

More in: Technology
  • 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
1,598
On Slideshare
1,593
From Embeds
5
Number of Embeds
2

Actions

Shares
Downloads
48
Comments
0
Likes
2

Embeds 5

https://www.linkedin.com 3
http://www.linkedin.com 2

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
  • One of the problems in making an Enterprise Content Management (ECM) strategy work with compliance initiatives is that compliance needs accountability at a very granular level. Consequently, IT shops are turning to log management as a solution, with many of those solutions being deployed for the purposes of regulatory compliance. The language however, regarding log management solutions can sometimes be vague which can lead to confusion. This session will lend some clarity to the regulations that affect log management. Topics will include: Best practices for how to best mesh compliance ECM and compliance strategies with log management Tips and suggestions for monitoring and auditing access to regulated content, with a focus on Microsoft Sharepoint logging. An examination of a handful of the regulations affecting how organizations view log management and information security including The Payment Card Industry Data Security Standard (PCI DSS), ISO 27001, The North American Electric Reliability Council (NERC), HIPAA and the HITECH Act.===ECM and compliance: what is the problem?Compliance needs accountability at granular level A lot of content has direct regulatory relevanceCustodian data and content: SSN, health records, etcLogging as a key vehicle for IT accountabilityLogging and complianceLogging practices and toolsECM + Compliance + Logging: how it all works togetherTips and suggestions for monitoring and auditing access to regulated contentExample: Sharepoint loggingConclusionsTrends in logging and compliance
  • Title: How to Gain Visibility and Control over Compliance Mandates, Security Threats and Data LeaksData integrity and confidentiality is critical. 62% of fraud is committed by insiders. Downtime is measured in millions of dollars per minute. Constant security threats and intense scrutiny by regulators and auditors require complete visibility and accountability, both in real-time and historically. Organizations face significant risks and exciting rewards during this period of economic and regulatory change.To meet the growing demands, you need to make a shift from worrying about the unknown to gaining a visibility and control over your operational threats. Top organizations are effectively managing their security threats and compliance requirements by building a foundation for internal investigations, forensics, and compliance that allows them to correlate information and detect real-time threats and fraud. By building pre-defined response plans they are able to significantly reduce the costs of managing network security and firewall policies. During this session we will cover how you can leverage the logs that you are already collecting to achieve regulatory compliance, protect valuable customer information and improve the efficiency of your IT operations team. This webcast will also feature a real world case study.(*) How to easily and cost-effectively automate your log management(*) How Log Management can be used to achieve compliance(*) How to protect valuable customer data(*) Best practices and tips for simplifying your life----I would like you to focus on the problem:(*) Data integrity and confidentiality is critical.(*) Constant security threats and intense scrutiny by regulators and auditors require complete visibility and accountability, both in real-time and historically.What organizations need to do:(*) To meet the growing demands, you need to make a shift from worrying about the unknown to gaining a visibility and control over your operational threats.(*) effectively managing the security threats and compliance requirements by building a foundation for internal investigations, forensics, and compliance that allows them to correlate information and detect real-time threats and fraud.(*) By building pre-defined response plans they are able to significantly reduce the costs of managing network security and firewall policies.=====We are trying to highlight all we do.This is infosec us audience====I'll be looking for a PPT presentation of between 12 and 20 slides, plus a spoken word preso of about 20 minutes from you - for submission one week ahead of the event itself - so can I suggest close of business on 01 December please?

Transcript

  • 1. Log Management and Compliance: What's the Real Story?
    Dr. Anton Chuvakin
    2010
  • 2. Outline
    Introduction to Logs and Log management
    Compliance Mandates Affecting IT
    Compliance and ECM = Disaster Brewing!
    Logging, an Ultimate Compliance Technology
    Logging for Compliance Practices
    Conclusions and Action Items
  • 3. Log Data Overview
    From Where?
    What Logs?
    • Firewalls/intrusion prevention
    • 4. Routers/switches
    • 5. Intrusion detection
    • 6. Servers, desktops, mainframes
    • 7. Business applications
    • 8. Databases
    • 9. Anti-virus
    • 10. VPNs
    • 11. Audit logs
    • 12. Transaction logs
    • 13. Intrusion logs
    • 14. Connection logs
    • 15. System performance records
    • 16. User activity logs
    • 17. Various alerts and other messages
  • Log Chaos: Login
    <18> Dec 17 15:45:57 10.14.93.7 ns5xp: NetScreendevice_id=ns5xp system-warning-00515: Admin User chuvakinhas logged on via Telnet from 10.14.98.55:39073 (2002-12-17 15:50:53)
    <57> Dec 25 00:04:32:%SEC_LOGIN-5-LOGIN_SUCCESS:LoginSuccess [user:antonc] [Source:10.4.2.11] [localport:23] at 20:55:40 UTC Fri Feb 28 2006
    <122> Mar 4 09:23:15 localhostsshd[27577]: Accepted password for anton from ::ffff:192.168.138.35 port 2895 ssh2
    <13> Fri Mar 17 14:29:38 2006 680 Security SYSTEM User Failure Audit ENTERPRISE Account Logon Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0    Logon account:  ACHUVAKIN   
  • 18. Why Manage Logs?
    Threatprotection and discovery
    Incidentresponse and forensics
    Regulatory compliance and audit
    Internal policies and procedure compliance
    IT system and network troubleshooting
    System performancemanagement
  • 19. Unfortunately …
    “The company’s server logs recorded only unsuccessful log-in attempts, not successful ones, frustrating a detailed analysis.”
  • 20. Compliance – Why is it Here?
    1. Corporations Stole
    2. Got Caught
    Sarbanes Oxley
    4. Bill gets passed
    5. Now we have to obey them
    3. Politicians wrote laws
  • 21. RegulationsRequire Logs
    MandatesDemand Logs
    ControlsInclude Logs
    • SOX
    • 22. GLBA
    • 23. FISMA
    • 24. JPA
    • 25. PCI
    • 26. HIPAA
    • 27. COBIT
    • 28. ISO
    • 29. ITIL
    • 30. PCI : Requirement 10 and beyond
    • 31. Logging and user activities tracking are critical
    • 32. Automate and secure audit trails for event reconstruction
    • 33. Review logs daily
    • 34. Retain audit trail history forat least one year
    • 35. COBIT
    • 36. Provide audit trailfor root-cause analysis
    • 37. Use logging to detect unusual or abnormal activities
    • 38. Regularly review access, privileges, changes
    • 39. Verify backup completion
    • 40. ISO27002
    • 41. Maintain audit logs for system access and use, changes, faults, corrections, capacity demands
    • 42. Review the results of monitoring activities regularly and ensure the accuracy of logs
    • 43. NIST 800-53
    • 44. Capture audit records
    • 45. Regularly review audit records for unusual activity and violations
    • 46. Automatically process audit records
    • 47. Protect audit information from unauthorized deletion
    • 48. Retain audit logs
    “Get fined, Get Sanctioned”
    “Lose Customers, Reputation, Revenue or Job”
    “Get fined, Go To Jail”
    At the Same Time…
  • 49. More Laws! Privacy Laws
    Mostly in Europe
    Thus affect transnational companies
    Govern not what MUST be logged, but what MUST NOT be logged!
    Logging is typically mentioned as something that might help violate privacy
    E.g. Google query logging and retention
  • 50. More Laws! Breach Laws Affected IR
    Laws that control consumer notification in case of a security breach
    Yesterday CA 1386
    Today more than 45 US States
    Tomorrow the world
    Who to notify is key:
    200,000 vs. 40,000,000 notifications? Major $$$ in play!
  • 51. What to do?
  • 52. Congressional Hearing: Subcommittee on Emerging Threats, Cybersecurity and Science and Technology
    April 2008
    http://geer.tinho.net/geer.housetestimony.070423.txt
    “In a free country, you don't have to ask permission for much of anything, but that freedom is buttressed by the certain knowledge that if you sufficiently screw things then up you will have to pay.”
    Daniel Geer, Sc.D.
  • 53. Why Logs for Accountability
    Everybody leaves traces in logs!
    Potentially, every action could be logged!
    Control doesn’t scale, accountability (=logs!) does!
    More controls -> more complexity -> less control!
    The only technology that makes IT users (legitimate and otherwise) accountable:logging!
  • 54. Control vs Visibility
    Myth: Stringent access controls will stop all attacks!
    What about those that have legitimate access? What about those who “break the rules”?
    The only control you can get is based on visibility and accountability!
  • 55. Corporate Accountability
    Accountability
    Accountability is answerability, enforcement, responsibility, blameworthiness, liability
    Log Management
    Log management is collecting, retaining and analyzing audit trails across the organization
    There is a strong link between accountability and logging
    Big Picture: Logs as Enabler of Corporate Accountability
  • 56. 11%
    82%
    8%
    14%
    77%
    9%
    17%
    74%
    9%
    15%
    73%
    12%
    15%
    69%
    16%
    19%
    66%
    15%
    17%
    66%
    17%
    24%
    54%
    22%
    22%
    51%
    28%
    Security detection and remediation
    Security analysis and forensics
    Monitoring IT controls for regulatory compliance
    Troubleshooting IT problems
    Monitoring end-user behavior
    Service level/performance management
    Configuration/change management
    Monitoring IT administrator behavior
    Capacity planning
    Business analysis
    7%
    90%
    2%
    0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
    (Percentage of respondants, N = 123)
    Yes, we use SIM technologies for this today
    No, we don’t use SIM technologies for this today, but plan or would like to do so in the future
    No, we don’t use SIM technologies for this today and have no plans to do so
    Source: Enterprise Strategy Group, 2007
    Use Cases for Log Data Continue to Expand
    Does your organization use log management for any of the following?
  • 57. Six Mistakes of Log Management
    1. Not logging at all
    2. Not looking at the logs
    3. Storing logs for too short a time
    4. Prioritizing the log records before collection
    5. Ignoring the logs from applications
    6. Only looking at what you know is bad
  • 58. “Compliance+” Model At Work
    You bought it for PCI DSS
    You installed it
    Your boss is happy
    Your auditor is … gone
    What are you going to do next?
  • 59. Conclusions
    In today’s complex IT, the only control comes from visibility and accountability
    Logs and log management is what enables it across all systems
    Start logging – then start collecting logs – then start reviewing and analyzing logs
    Prepare for incidents by deploying log management system!
  • 60. Questions?
    Dr. Anton Chuvakin
    Security Warrior Consulting
    Log management , SIEM, PCI DSS
    Email:anton@chuvakin.org
    Site:http://www.chuvakin.org
    Blog:http://www.securitywarrior.org
    Twitter:@anton_chuvakin
    Consulting:http://www.securitywarriorconsulting.com
  • 61. More on Anton
    Consultant: http://www.securitywarriorconsulting.com
    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, RSA, 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
  • 62. Want a PCI DSS Book?
    “PCI Compliance” by Anton Chuvakin and Branden Williams
    Useful reference for merchants, vendors – and everybody else