Escolar Documentos
Profissional Documentos
Cultura Documentos
Log Management
How to Develop
the Right Strategy
for Business
and Compliance
An Allstream / Dell SecureWorks White Paper
1
Table of contents
Executive Summary 1
Conclusion 8
The purpose of this whitepaper is to provide the reader with guidance on developing a strategic approach to managing and
monitoring logs that enables more efficient compliance with regulatory mandates and more effective defense against security threats.
Executive Summary
The amount of data collected by network and security devices is growing at an astounding rate. From compliance
requirements to data gathering for forensic purposes, companies have opened up the floodgates to log data. Based on
audit findings and internal investigations, many have deployed expensive technologies and lots of personnel without a
full understanding of what to log and why. Others simply lack the resources and expertise for this, leaving their company
vulnerable to audits, penalties and breaches. Organizations need a business-based approach to creating a log management
strategy that will help them detect attacks, deal with mounds of data collected by network and security devices, and meet
compliance requirements. This more strategic approach reduces the complexity associated with this process, enables more
efficient and transparent compliance with regulatory requirements, and provides more effective identification and response to
security threats.
In addition, current security monitoring approaches rely too heavily on the collection of data at the network layer, generating
volumes of data and leaving the application layer at risk. Network monitoring can complement and enhance host and
application-based monitoring, but rarely substitutes for it. After all, the typical end result of an attack is access to a host or
application such as a credit card database. Host- and application-based monitoring identify events that actually did occur,
not what could occur. The combined analysis of network events with log data from critical applications and hosts can point
to high risk activity that may be overlooked in network-only analysis. The key is to know which systems to monitor, for what,
how frequently, and what to do about exceptions and anomalies.
This white paper helps security and IT executives design a strategy for more effective log management with a five step
process:
• Identify the systems and applications that fall into the scope of monitoring efforts.
A business-focused log management strategy matrix helps guide decisions about technology, processes and services,
instead of the reverse. The result is better compliance with information security regulations and the ability to effectively
respond to information security threats, through a more focused collection and retention of data.
1
Log Management | How to Develop the Right Strategy for Business and Compliance
Because applications are difficult to monitor, companies have neglected to include them in their log monitoring efforts,
hoping to catch an intrusion at the network layer. Applications log via different means, in different formats, and capture
different variables, making it difficult to centralize information for analysis and reporting. Some applications are not configured
to generate security logs at all. Those that are may generate logs that only make sense within the application and cannot be
read by a centralized analysis tool. This complexity has kept auditors from focusing in on application logging… until now.
Concerns about control of financial information, unauthorized access to confidential information, and identify theft, have led
to information security regulations such as Sarbanes-Oxley (SOX), the Health Information Portability and Accountability Act
(HIPAA), the Gramm-Leach-Bliley Act (GLBA) and industry standards such as the Payment Card Information Data Security
Standard (PCI DSS). These laws and industry standards require log monitoring of systems that collect or store personal
information and store financial records, but rarely offer specific guidance about what types of data to collect and how long to
keep it. While PCI has some specificity, HIPAA, GLBA and SOX all take materiality-based approaches, leaving interpretation
and the ultimate state of controls varying from company to company.
A log management strategy puts the emphasis on business priorities such as customer service, operations, legal protection
and intellectual property. Developing a matrix starts with a list of the key drivers, or the reasons you need to collect, retain
and monitor log data:
2
Log Management | How to Develop the Right Strategy for Business and Compliance
2) Identify the systems and applications that fall into the scope of monitoring efforts.
The simplistic approach to log monitoring is to identify what can be captured easily and save it all. A strategic approach
targets the scope and includes all systems and applications that will help monitor security events related to key drivers.
For example:
• SOX compliance requires log monitoring of financial statement and processing systems
• PCI compliance requires log monitoring on credit card processing and data storage systems
• GLBA compliance requires log monitoring on systems that store personal financial data
• HIPAA compliance requires log monitoring on protected systems that store personal health data
In addition to compliance requirements, the scope should include systems that are of high risk to the organization due to their
intrinsic value, and systems related to intellectual property assets. Legal and compliance officers are often consulted during
the data gathering process for this step.
Many regulations require retention of reasonable amounts of data for reasonable amounts of time, leaving interpretation up to
security officers and auditors. Creating a matrix based on compliance as well as business goals, such as intellectual property
requirements, offers a clear definition of reasonable. One way to limit the amount of data is to distinguish between retention of
raw data and exception events.
Because the log data may contain sensitive information, PCI and other regulations require the protection of the logs
themselves as well as their retention. Log security requirements may require access controls, encryption, integrity checking,
and notification of changes. For example, Requirement 10.5 of PCI DSS mandates companies to “secure audit trails so they
cannot be altered.” This includes limiting access, protecting the logs from modification and having a means to know if the logs
have been changed.
The amount of information generated by most log monitoring tools can overwhelm a security organization. Limiting the types
of events and transactions that require retention and review to those related to the key drivers makes the process manageable.
Once again, regulatory requirements and security best practices provide a starting point. Events may include: certain login
attempts, account modifications, remote connections, changes to policies and permissions, and firewall connections.
Event combinations play a critical role in tracking intrusions into the unique infrastructure of each company. A login from an
unexpected source may indicate an imposter using authorized credentials. Malicious traffic followed by an account creation
within a set time frame may point to the source of an attack, requiring a quick, targeted response. Meta events may occur
within applications or across applications, platforms and network systems.
3
Log Management | How to Develop the Right Strategy for Business and Compliance
Each event should have a defined monitoring and response requirement. Event data may simply be collected for future review,
or require periodic review and sign-off for compliance purposes. Security events that suggest a likely threat to critical systems
should generate an alert for immediate review. The response should clearly articulate the process from detection to response,
including appropriate ticketing and workflow documentation.
The log management requirements matrix serves as a documented set of business requirements around log management.
The matrix should be regularly reviewed to update standards and include new applications and systems. Most importantly,
companies should use this tool to guide purchases of technology and other tactical means to meet business objectives.
The technology should not drive the log management strategy.
Part I: Background/Drivers
Company X has identified the following key drivers for our log management strategy:
• Compliance with the Payment Card Industry Data Security Standard (PCI DSS), Sarbanes-Oxley (SOX),
and the Gramm-Leach-Bliley Act (GLBA)
• Financial systems: accounting software, Oracle database environment, finance department file servers
• Credit card processing systems: POS application, POS databases, AS-400 servers storing card numbers
4
Log Management | How to Develop the Right Strategy for Business and Compliance
Company X has reviewed applicable regulations, industry standards and our intellectual property policy, and identified the
following retention requirements:
Intellectual Minimum
Source PCI SOX GLBA Best practices
Property Required
* varies by auditor.
** unless details are captured in reports that are retained for 7 years.
Company X has reviewed applicable regulations, industry standards, our intellectual property policy, and identified the
following security requirements:
Intellectual
Requirement PCI SOX GLBA Best Practices Company X
Property
Access Control R R* R R -- R
R = required O = optional
5
Log Management | How to Develop the Right Strategy for Business and Compliance
Based on retention and security requirements, Company X has identified the following events for collection and assigned
an appropriate review period:
Access
User successful login C C C CP CP
User failed login CP CP CP CP CP
Object access CP CP CP CP CP
Accounts
Account create/modify/delete C CP C CP CP
Remote Connections
Configuration Changes
Permission changes CP CP CP CP CP
Firewall/IDS
Denied connections CP CP CP CP CP
Accepted connections C C C C C
6
Log Management | How to Develop the Right Strategy for Business and Compliance
C = collect for future review P = conduct periodic review A = alert for immediate review
Note: Most of the regulatory requirements and standards do not specify event types. The events listed above are interpretations based on the intent of the
control requirements.
Customized databases and mainframes require more flexibility and creativity. Some applications are not configured to
generate security logs, while others generate logs that can only be read by the application, not a centralized analysis tool. At
the highest degree of difficulty are the applications where data types, formats, organization and meaning all differ. There may
be several ways to retrieve logs that need to be balanced with performance and ongoing management requirements, working
closely with the system administrators.
7
Log Management | How to Develop the Right Strategy for Business and Compliance
Conclusion
The word “strategic” is not often associated with information security, and even less so with compliance. Too often,
companies solve security and compliance requirements for log monitoring through technology purchases or expanded staffing
resources. It is clear that the cost and complexity of developing and maintaining an effective log management system draws
focus and resources away from core business needs. A more cost-effective solution approaches log management like any
other strategic planning exercise. By starting with the drivers, building the business requirements and executing against the
plan, companies will have a monitoring capability that reaches deep into their systems and applications, focusing resources
where the risks are greatest.
8
Connect with confidence through Allstream and Dell SecureWorks
Together Allstream and Dell SecureWorks deliver managed security services that are unrivalled by other Canadian service providers.
The combination of deep expertise in voice, data and IP networking, in conjunction with intense focus on intelligent defence and threat
visibility, allow our customers to connect with confidence. Allstream is recognized as an industry-leading communications provider to
Canada’s Fortune 100 and mid-market businesses. Dell SecureWorks is a leading global provider of world-class information security
services for Fortune 500 and mid-sized businesses.
Allstream
200 Wellington Street West
Toronto, Ontario M5V 3G2
Copyright © 2009-2011 SecureWorks, Inc. All rights reserved. All other products
and services mentioned are trademarks of their respective companies.
WP_22175 V2 11/14 ® Allstream Inc.