KCI ArcSight ESM Evaluation
KCI ArcSight ESM Evaluation
com
I. Executive Summar y
It is the opinion of Kahn Consulting, Inc., that ArcSight’s Enterprise Security Management (“ESM”)
system provides capabilities that support its use as a platform for the management of computer
security log files as evidence. ArcSight ESM is designed in a manner that protects the security and
trustworthiness of the information collected, processed, correlated, and managed by the system.
By providing information protection capabilities, and processing data according to documented
processes, ArcSight ESM works to ensure that the security and trustworthiness of the information
that it manages is protected.
Introduction
Kahn Consulting, Inc. (“KCI”) was engaged by ArcSight,
Inc. (“ArcSight”) to evaluate the company’s ArcSight “Organizations should con-
Enterprise Security Management system. The primary sider implementing a log
purpose of this Evaluation is to assess the product’s management infrastructure
utility as a platform for collecting, analyzing, correlating, that includes centralized log
and generally managing computer security log files as servers and log data stor-
evidence. In conducting this Evaluation, KCI has assessed age.”
ArcSight capabilities against criteria derived from broad
legal and regulatory requirements and best practices for Guide to Computer Security
the management of electronic information and records. Log Management, National
The proper management of computer security log file Institute of Standards and
information should be undertaken by organizations in Technology, Special Pub.
the context of a formal, policy-driven program of people, 800-92 (Draft)
Not a legal opinion or processes, and technology.1
legal advice. For all
questions regarding
compliance with specific
laws and regulations seek
legal counsel.
August 2006
KAHN P O B OX 1 0 4 5 • H I G H L A N D PA R K I L • 6 0 0 3 5
CONSULTING INC. PH O N E : 8 4 7 . 2 6 6 . 0 7 2 2 • FA X : 8 4 7 . 2 6 6 . 0 7 3 4 • E M A I L : I N F O @ K A H N C O N S U LT I N G I N C . C O M
Special Report: Product Evaluation: ArcSight ESM -2-
Evaluation Background
Today more than ever before, organizations rely upon digital information to do business. Not only
are more transactions executed electronically than ever before, transactions of greater value and risk
continue to move into the electronic environment. As electronic business has proliferated, so too
has the volume and diversity of threats to the security, confidentiality, and integrity of the digital
information that provides the foundation of business today.
Organizations have responded appropriately to these threats by incorporating software and hardware
throughout their networks designed to monitor and control access to information systems and the
information these systems contain. However, several factors have worked together to make the
management and use of this information a challenge for many organizations:
The increasing volume of software applications and hardware devices that generate log
files that may be important from an evidentiary perspective
Increasingly distributed networks and systems with more access points requiring
management
Increasing complexity and interdependency of systems (e.g., the increasing use of Service
Oriented Architectures)
The increasing sophistication of attacks from malicious parties both inside and outside
the network
The growing scrutiny of information management and information protection practices
by courts, regulators, and other parties
Increasing penalties, fines, sanctions, and other negative consequences for information
management and information protection failures
Lack of standardization in the log file formats generated by security systems
As a result of these and other challenges, organizations are turning to systems that can help them
better collect, process, and act on the information found in log files generated by security software
and devices throughout their network.
ArcSight can ingest security log file information from over one hundred and fifty different security
devices, and is designed to integrate with existing networks.2 ArcSight is delivered with default
security, processing, and report settings, but is configurable to network design specifics and security
priorities.
ArcSight is also designed to store and manage information in a manner that maintains evidentiary
quality, as detailed in Sections V and VI of this Evaluation. In this regard, ArcSight is designed to
enable authorized access, management, and processing of data; the secure storage and retrieval of
various data categories; secure data transport; and the retention of information for audit and legal
purposes.
However, computer log files are also increasingly used as evidence during the course of internal
investigations, lawsuits, government investigations, audits, and other formal matters. As such, rather
than viewing log file information as merely “technical” or tactical information, many organizations
today view certain computer security log files as a unique form of “evidence” that must be managed
in a manner that reflects its intended or possible future use.
The use of computer security log files as evidence raises several issues regarding the legal admissibility
and credibility of the information. Any organization wishing to rely upon electronic information for
legal and regulatory purposes, or wishing to submit it as legal evidence must address two separate
- but related - challenges. First, the information must be admissible – that is, it must be acceptable
to the court or to the regulator. The admissibility of electronic information is governed by a variety
of laws, but, with some limited exceptions, in most instances and in most jurisdictions, there are no
specific prohibitions on the admissibility of electronic information as evidence.
The second challenge for electronic information is that it must be credible. In other words, electronic
information must be authentic, complete, and trustworthy enough to deserve to influence the
outcome of a legal proceeding. Even if such evidence is found to be generally admissible, its integrity
can nonetheless still be attacked, and it can be excluded or its influence on the proceeding can be
severely diminished.
Overview
From a high level, the normalization process, which is executed by the ArcSight SmartConnectors,
is designed to convert log file information from proprietary, heterogeneous formats, into a universal
format that ArcSight ESM can process and analyze. During normalization, “event data,” such as
data indicating a security event’s priority, time of occurrence, and so on, is converted into a common
ArcSight ESM data schema (i.e., format). This common format can be filtered and aggregated,
with the primary intent being the reduction of the volume of duplicative or otherwise unnecessary
information processed by ArcSight.
Because the normalization process alters the log file as it is initially created by the originating data
source (i.e., security software or device), the impact of the normalization process on the evidentiary
quality of data stored and managed by ArcSight ESM bears evaluation.
Various laws and regulations have made clear that authentic electronic information can be admissible.
However, these laws and regulations have also made clear that standards of information integrity
and accuracy must be met. In fact, the courts have excluded electronic evidence that they have
deemed untrustworthy. In addition, it does an organization little good to expend the resources
necessary to capture and store electronic information if the organization itself cannot be sure of the
information’s integrity.
WHERE LAW & TECHNOLOGY MEET
Evidentiary Issues
When evaluating the impact, if any, of the normalization process on the evidentiary quality of
computer security log file information in ArcSight ESM, organizations should consider the following
issues.
Rules regarding the admissibility and credibility of evidence are based on the foundational concept
of “the original.” Evidentiary statutes such as the Federal Rules of Evidence indicate a preference for
“original” documents.3 However, in the electronic world, where it is possible to make infinite perfect
copies of a document, the concept of an “original” loses some of its significance.
Various laws and regulations have responded to this reality by clarifying that, in the electronic world,
there might be no difference between an “original” and a “duplicate” for evidentiary purposes. For
example, the ESIGN Act4 states that electronic information may be used to satisfy legal requirements,
provided that it:
“Accurately reflects the information set forth in the contract or other record;” 5
“Remains accessible” 6 for the period the law requires;
Can be “accurately reproduced” 7 in the future.
Furthermore, ESIGN clarifies that an electronic record that meets these conditions can satisfy the
requirement for an “original.”
Given this reality, evaluating the evidentiary impact of normalization on an “original” computer
security log file should focus on the nature and extent of the alteration that occurs during the
normalization process.
The ArcSight ESM normalization process is designed to translate divergent, proprietary approaches
to describing security event information into a universal format that maintains the meaning of
the original. In fact, it is readily apparent that the utility of the product itself would be severely
diminished if the normalization process did in fact materially alter the meaning of the original
information.
As an added point, it should be noted that the Federal Rules of Evidence establish a basic principle
that, if an organization routinely relies upon a given record in the course of their business, that
record is generally admissible.8
and hardware was reliable and operating properly, and that appropriate policies and procedures
were implemented and adhered to. For example, IRS rules mandate various “controls to ensure the
integrity, accuracy, and reliability” of record keeping systems,9 as do several other federal and state
regulations.
It should be noted, however, that the volume of log file information generated by many devices
is too great to be stored on the device itself over the long term. For devices that generate log file
information that must be retained only for short periods of time, it may be appropriate to retain the
information on the device itself and allow the information to be cyclically rewritten. However, for
log file information that may have longer term retention requirements, or otherwise is expected to
be used as evidence in the future, there is often a practical need to move the data from the device to
another storage location.
Access Control
Desired Capability. Log file management systems should ensure that users can only access
information that they are authorized to access.
ArcSight ESM Capabilities. ArcSight ESM defines several user roles that correlate to different
levels of responsibility and access. These roles include: Admin, Author, Operator, Analyst, Security
Manager, and Business User. ArcSight ESM also provides a comprehensive implementation of
Access Control Lists. In this manner ArcSight ESM provides organizations with the ability to ensure
that only authorized individuals are able to access (and perform other operations on) private and
confidential information.
In addition, ArcSight ESM allows customized workflows to be programmed. Such workflows could
be utilized to help ensure that only authorized parties involved in an investigation, for example, are
able to access information related to that investigation. Workflow capabilities may also be useful for
compliance-related monitoring and control activities, such as those related to the Sarbanes-Oxley
Act.10
Records Retention
Desired Capability. Organizations may be required to securely retain certain types of electronic
information in order to comply with laws and regulations regarding records retention. The retention
of records is also necessary for normal business operations and for internal and external audits.
ArcSight ESM Capabilities. ArcSight SmartStorage and the ArcSight Database both provide
storage capabilities designed to ensure that retained data is stored in an efficient and effective
manner. ArcSight archiving technologies include the extraction and storage of chronological data
slices, and the option of configuring the frequency, categorization, and access to archived electronic
information.
KAHN
operation) is transmitted in a secure manner.
Information Management Principle. The integrity of electronic information used as evidence for
legal and regulatory purposes must be protected so that its admissibility and creditability can be
maintained.
ArcSight ESM Capabilities. Communication between ArcSight ESM and ArcSight Connectors,
ArcSight Consoles and Web Browsers is encrypted with 128-bit SSL encryption and 1024-bit key
exchange. ArcSight ESM also supports authentication techniques such as RADIUS, LDAP, Active
Directory, Two-Factor Authentication, and Public Key Infrastructure.
Auditing
Desired Capability. Log file management systems should generate, make available, and securely
store information regarding its operation for auditing purposes.
Information Management Principle. Systems used to store and manage information used as evidence
must provide reliable information regarding their functioning and regarding critical operations such
as information access, deletion, and so on.
ArcSight ESM Capabilities. ArcSight ESM provides logging and auditing for user access to the
ArcSight system and audit logs listing what that user accessed, when, and what changes were made.
In this manner ArcSight provides auditing capabilities designed to support the use of computer log
file information as evidence.
VII. Summar y
It is the opinion of Kahn Consulting, Inc., that ArcSight’s Enterprise Security Management
(“ESM”) system provides capabilities that support its use as a platform for the management of
computer security log files as evidence. ArcSight ESM is designed in a manner that protects the
security and trustworthiness of the information collected, processed and managed by the system.
By providing information protection capabilities and processing data according to documented
processes, ArcSight ESM works to ensure that the security and trustworthiness of the information
that it manages is protected.
IX. Endnotes
1
In undertaking this engagement, KCI exclusively relied upon information supplied by ArcSight through internal and
external documentation, and interviews with ArcSight representatives. KCI does not conduct independent laboratory
testing of information technology products, and as such, did not evaluate ArcSight ESM in a laboratory setting or
otherwise field-test any ArcSight products.
2
For a current list of devices supported by ArcSight ESM, please see http://www.arcsight.com/product_supported.htm.
3
See, for example, Rule 1002.
4
Public Law 106-229, Section 101(d), “Retention of Contracts and Records.”
5
Ibid.
6
Ibid.
7
Ibid.
8
Provided certain conditions are met - the conditions provided in Rule 902 are that the record: (A) was made at or near
the time of the occurrence of the matters set forth by, or from information transmitted by, a person with knowledge of
those matters; (B) was kept in the course of the regularly conducted activity; and (C) was made by the regularly conducted
activity as a regular practice.
9
IRS Revenue Procedure 97-22.
10
For further information about the Sarbanes-Oxley Act, please refer to http://www.sec.gov/about/laws.shtml.
Entire contents © 2006 Kahn Consulting, Inc. (“KCI”). Reproduction of this publication in any form
without prior written permission is forbidden. KCI and ArcSight, Inc. shall have no liability for errors,
omissions or inadequacies in the information contained herein or for interpretations thereof. The
reader assumes sole responsibility for the selection of these materials to achieve its intended
results. The opinions expressed herein are subject to change without notice. All rights reserved.
www.KahnConsultingInc.com info@KahnConsultingInc.com 847-266-0722