McAfee Total Protection Jun09
McAfee Total Protection Jun09
McAfee Total Protection Jun09
Executive Summary Data Protection in Review Requirements Methodology SANS Review of McAfee Endpoint Encryption for PC (v5.1.8) and for Files and Folders (v3.1.3) SANS Review of McAfee Host and Network Data Protection SANS Review: NDLP, HDLP, and Endpoint Encryption Integration
www.verizonbusiness.com/resources/security/reports/2009_databreach_rp.pdf
In this document, we describe the results of our review of a broad range of features and functions within McAfees Total Protection for Data suite. This includes McAfees Phase I integration of host (Host DLP v3.0) and network (Network DLPDiscover, Manager, Monitor, and Prevent v8.5) data protection tools and management dashboards, along with McAfees host-based full disk, file/folder and device control encryption (Endpoint Encryption (EE) for PC v5.1.8 and EE for Files and Folder v3.1.3). Each of these products met or exceeded review objectives in all categories. Furthermore, McAfee has made strong headway in integrating management among the products, starting with its Host DLP integration into the ePO framework. Some of the grades the products received reflect elements that are prioritized and planned for integration in McAfees next release, but which arent integrated in the versions in this review.
In the following pages, we include more detailed report cards for DLP, encryption, and dashboard integration, with descriptions of review results for both the EE and DLP toolsets. Preceding the report cards is a description of review requirements and methodology.
Requirements
Data protection tools need to include fast, deep and accurate content identification for a variety of use scenarios that involve data at rest, data in use and data in motion. Policy creation and tuning must be flexible and intuitive for monitoring, discovering and taking appropriate action on critical data traversing the networkon data at rest or in use on the host, and as it attempts to leave the host on removable media, via e-mail or by other means. Any data protection toolkit should also include broad environmental coverage (network and host platforms, integration with directory services and e-mail platforms, and auxiliary functions like encryption.) While there are myriad requirements to consider, they essentially fall into the following five categories: Discovery and Capture: Both host and network discovery tools should be capable of discovering sensitive content stored on key systems across the enterprise, a critical first step many organizations still need to takeand one that large enterprises cannot reasonably conduct without leveraging automated tools. Monitoring: Data in use and in motion should be monitored at line-speed as it traverses network links. Monitoring of data on critical applications and systems, including storage devices, should be comprehensive, port agnostic and flexible enough to change policy on the fly when needed. Alerting and Prevention: Host and network tools should be able to match detected events to policies, which then tie into an incident response (alerting and blocking specific actions). Workflow/alerting should involve specified participants from affected business units (Compliance, Human Resources, Legal, Help Desk, etc.). The system should also be self-learning, that is able to discover and alert on unknown or unclassified data types. Encryption: Deployed encryption models should be flexibly and easily created and enforced for a variety of uses, such as file, folder, e-mail and full disk encryption as well as copying data to USB devices and other removable media. Compliance: Policies and reports should be available out of the box, with the ability to easily modify these for internal compliance standards and changing regulations. See our accompanying Data Protection Requirements Worksheet, which can be used to create individually tailored lists of requirements based on organizational needs and rank vendor ability to meet those requirements.
Methodology
The following McAfee products were included in the review: Endpoint Encryption (EE) for PC version 5.1.8 EE for Files and Folders version 3.1.3 (V3.2 now available but was not yet released at time of review) Host DLP version 3.0 Network DLP (Discover, Manager, Monitor, and Prevent) version 8.5 Integration of these into the ePolicy Orchestrator version 4.0 (version 4.5 available soon)
Figure 1: Review Lab Architecture For this product review, a number of separate products and components were installed and configured. In the lab, the following systems were configured as illustrated in Figure 1: One Windows 2003 Server Domain Controller One Windows 2003 Server running Exchange Server 2003 One Windows 2003 Server acting as a file server One Cisco 2960 switch with a span port activated, connected to a hub One Cisco 2800 connected to the Internet One Red Hat Linux Enterprise server running NFS and TCPreplay Four Windows workstations (two each of XP and Windows 2000) One Windows Server 2003 system running ePolicy Orchestrator (ePO)
SANS Analyst Program
The data formats used for testing included Microsoft Office documents and spreadsheets, text files, e-mail content, and PDF documents. Sensitive data types of interest included Social Security numbers, payment card data, customer lists, board meeting minutes, pharmaceutical formulas, tax information, and other intellectual property. The product review methodology, at a high level, involved the following: 1. Installing and configuring the products, including integration with Active Directory and an e-mail server, as well as pointing components and agents to the ePO and the McAfee network DLP management platform. 2. Creating host and network DLP policies to implement within the test network and on workstations and servers. 3. Conducting network and host content discovery, capture and fingerprinting. 4. Testing modification of data on endpoints and attempting to remove data to external media, create screen captures, and so on. 5. Testing network data leakage detection by sending data across the network using TCPreplay and preconfigured PCAP files, as well as custom e-mails, file transfers and other such transmissions. 6. Testing encryption capabilities by defining policies for handling certain documents and data types and then moving the files to removable media or transmitting them via e-mail to determine whether encryption was properly maintained. In this review, we refer to our accompanying Data Protection Requirements Worksheets severity level ratings as we set up scores for features and functions. Priorities are described as follows: Priority 1: Essential, critical features that must be considered for all organizations when evaluating DLP solutions. Priority 2: Important features that deserve attention, but may not be deemed as critical depending on the organization. Priority 3: Interesting features that may be worthy of focus and attention. Assigned grades in this review are subjective. They are based on the reviewers experience with the products, interviews with McAfee product managers, and discussions with information security professionals working with data protection tools in enterprise situations. Grades were assigned as follows: A = Product met or exceeded expectations. B = Product met all requirements with some exceptions. C = Product met most requirements but was deficient in many. D = Product met some requirements but was deficient in most.
SANS Review of McAfee Endpoint Encryption for PC (v5.1.8) and for Files and Folders (v3.1.3)
McAfees Endpoint Encryption for PC (EEPC) and for Files and Folders (EEFF) allow for policybased application and device control that can maintain persistent file and folder encryption across a variety of statesincluding sensitive files being transferred onto USB devices. EE for removable media is integrated into McAfees central management platform, e Policy Orchestrator (ePO). McAfee plans to offer central management for third party, hardware-based Encrypted USBs and hard disk drives through ePO in the future. Although not reviewed in this paper, the suite also includes encryption, as well as data and device management tools for protecting mobile devices using the Windows Mobile and Symbian platforms, with support for additional platforms planned for the future. Key features reviewed in the EEEF and EEPC products include disabling system ports, defining what applications are trusted/untrusted (and what the applications are allowed to do on each system), and maintaining persistent encryption as data moves from the system via e-mail, removable media or other transmission method. Other features of note include: Complete encapsulation of the operating system on a users system, replacing all login and system access functions. A central management console that keeps a running directory of users, systems, policies and other objects. Support for multiple two-factor authentication types like smart cards and hardware tokens. EEEF extends this level of protection to files and folders on systems, allowing extremely granular policies to be established and maintained for different file types, system types and specific users.
The EEPC products were reviewed by first installing the Endpoint Encryption Manager, EE Server, and Object Directory on a Windows 2003 Server and then creating install packages with a variety of password, audit, and file/folder policies enabled. For both products, the review process consisted of the following: Selecting a Password Only token option after installation of the management components. Then selecting the default Program Files list and creating a variety of user and machine groups. Creating user-based policies that restrict several applications and logging attempts to use those applications. Creating machine groups and adding user groups to them. For EEFF, this included creation of several classes of encryption keys and policies including automatic encryption for Word documents and data copied to USB drives, user and group policies, etc. Generating and copying install packages to a USB for deployment to PCs. After installation, policies were tested for each individual machine and found to work as specified without exception. All encrypted data remained encrypted while moving from the systems to devices. The user experience was easy, and users could not decrypt data that they had no rights to view.
Report Card: McAfee End Point Encryption for PC 5.1.8 and Files/Folders 3.1.3
Feature
Installation, Setup and Deployment
Priority Comments 1
Deployment of the EE products was straightforward. There are several components that need to be installedthe EE Manager, Object Directory, and communications components. These are simple to install and manage. Users, Machines, and Machine Groups are all then easily created and modified. Finally, an installation package for clients is created, which can then be installed from removable media or via ePO, SMS or other software distribution tools. EE products support Windows 2000, XP, Vista (32/64 bit), and Windows Server 2003. Mac OSX and Linux support are on the current McAfee DLP product roadmap, but not available at the time of this review. The level of user transparency for the EE line is magnificent. Encryption and decryption of disk, files and folders had minimal impact on performance. Enforcement of policies and policy updates is performed seamlessly in the background without any user interaction required. As an option, a system tray icon can be made visible, allowing the user to perform some simple actions at the administrators discretion. LDAP, Active Directory, and other user identity repositories are supported. The product was specifically tested with Active Directory and integrated with no issues. All user management is performed at the repository level, and rules then propagate to the EE Management Server. Administration and creation of agents are handled through a single console called the Endpoint Encryption Manager. Within this console, packages were generated with specific user and machine policies, token-based and other types of authentication configured, and deployment options set. Multiple administrator accounts were created, each with a variety of roles and permissions that were assigned according to business unit, machine groups, and so on. FIPS 140-1/140-2 algorithms are supported, including AES and RC5 with strong key lengths (256-bit and up).
Grade A
Platform Support
Identity Management
2 1
Keys are not stored in plaintext on the server side and can be generated on the client and A server. Authentication is required to access keys, and all key transfer communication is encrypted. This was observed by watching the traffic with a sniffer while managing and updating keys with clients. Password and token recovery and resets were simple to perform, and recovery administrators can be created that dont have any additional privileges (great for Help Desk and Support teams that dont need full access). The software was robust, maintaining the encrypted state even after sudden power loss. One interesting feature is a challenge-response password reset option for users who forget passwords, which also allows users with lost tokens or smart cards to temporarily become password-only users at the local machine.
Recovery Capabilities
The EE products do not provide any sort of master key. Only the keys used to encrypt A data can decrypt the data. This provides an additional level of protection against any one administrator having the ability to access all encrypted data with a single key. Separation of duties was achieved by assigning specific roles for different administrators: encryption administrators or user and machine administrators. In this way, certain administrators can be responsible for key management and encryption control, while others control user, group and machine administration. All boot and logon events are logged centrally, and audit trails can be exported in a number of formats.
Report Card: McAfee Host DLP 3.0 and Network DLP 8.5
Feature
Installation and Initial Configuration Integration with Directory Services and MTA (Mail Transfer Agent) Data Discovery, Retention, and Archived Search
Priority Comments 2
Installation of NDLP appliances was simple and intuitiveas close to plug and play as possible. Installation of HDLP was also simple. Documentation is excellent. Configuration of out-of-the-box policies is easy. Integration with Microsoft Active Directory and Exchange servers was seamless and fast due to readily accessible configuration options within the NDLP and ePO consoles.
Grade A
NDLP supports three scan modes: Registration (fingerprinting a repositorys files), Discover (finding previously-fingerprinted files), and Inventory (generating a full listing of files, whether they are fingerprinted or not). Both CIFS and NFS network shares were reviewed using simple authentication via directory credentials. Scheduling scans and tying scans to existing rules and policies was simple. Performing searches based on violations and content types was also easy and flexible. HDLP discovery crawls each endpoint looking for sensitive content (regular expressions, dictionaries, content form registered document) and/or previously tagged files. Detected content files can be quarantined or encrypted using Endpoint Encryption products. Rules and policies based on the tags were easily created and monitored for violations. Events are then easily monitored within the ePO console, which archives and indexes event data with full search capabilities suitable for forensics, compliance or incident drill down.
Within NDLP, standard policies (known as Electronic Risk Modules) are installed by A default and have a wide variety of flexible rules assigned to them. Compliance-specific policies are also available, and custom policies can be created easily by cloning an existing policy. NDLP rules are flexible and use standard Boolean and Regex-like syntax. Rules can also be tuned rapidly as dictated by logged events to refine and eliminate false positive and false negative behavior on the fly. Rule exceptions are also simple to add. For HDLP, classification rules are used to define sensitive categories according to regular expression, dictionaries, and registered documents. Tagging rules are used to tag files copied from sensitive location, or files generated by sensitive applications. Protection rules are then created to determine particular actions taken when data is transferred or transmitted. These rules are robust and use flexible syntax for tying data to specific applications, file servers, network shares, printers and unique content patterns. Finally, device rules are used to specify external devices like USB drives with a large variety of unique identifier data. Loading HDLP rules and policies into ePO was simple.
The NDLP and HDLP products capably detected every attempt at sensitive data removal, modification, or transmission. Sensitive data in motion and use was successfully detected and logged in a variety of situations, including data sent in e-mail traffic, sent as e-mail attachments, processed within applications on hosts, and transferred to USB drives and CDs (CD-R). Attempts to capture screenshots and numerous other file manipulations were all successfully detected and logged.
10
Report Card: McAfee Host DLP 3.0 and Network DLP 8.5 (CONTINUED)
Feature
Incident Workflow and Management
Priority Comments 1
Grade
The NDLP console is a robust, built-in case creation and management system that Aallows multiple incidents to be assigned for data at rest, in use and in motion. The only downside is that ePO does not directly manage the cases. It is only a minor inconvenience to launch the NDLP management console from within ePO and manage cases from all products there. Full case management integration is on McAfees roadmap for next release. All events and systems could be managed from within ePO 4.0. Some of the NDLP functions within ePO launch a separate NDLP management console, but this is a minimal issue. Numerous roles can be assigned, including administrator, reviewer, agent administrator, auditor, and so on. Roles can be assigned to any user within the organization, and audit trails for user actions within the console are maintained. A variety of reports that offer many options and chart types are available within the ePO console and NDLP manager. The NDLP appliances are purpose-built, locked-down devices that have only specific ports and services running. The McAfee host-based agents are also protected from user tampering and disabling. Although a wide variety of reports for compliance are available in the product, they are primarily focused on U.S.-based compliance. International regulatory compliance features are on the roadmap for next release, including content analysis and pattern matching in multiple languages, international compliance templates and reports, and additional languages for the user interface.
A-
2 2
A A
Compliance
11
SANS Review: NDLP, HDLP, and Endpoint Encryption Integration Data Protection
With their latest developments and acquisitions in encryption, host and network DLP, McAfee has begun the integration to allow users to monitor and manage their critical data at use, data at rest, and data in motion within one framework. In this review, several critical first stages of this integration were in place, while others are on the product roadmap for next release. One of the primary areas of focus for McAfee is consolidating management consoles into its ePO product, which would allow a simple, well-known interface to be leveraged for all policy and rule creation, package creation, event and incident management and reporting. Today, McAfees integrated deployment, auditing and reporting for data discovery, monitoring, prevention, endpoint protection, device control and encryption can all be handled from within ePO. McAfee aims to provide automated correlation, central policy configuration and management from ePO in its next release. Current integration of the Endpoint Encryption products with Host DLP is strong, allowing encryption capabilities to be integrated with HDLP policies for use in the following ways: Data protection on USB and removable media: After defining named encryption keys in the EEFF product and adding them in the HDLP console, these keys can be used to encrypt data via HDLP Removable Storage Protection rules. Network Share rules enforcement: Using HDLP File Access Protection rules, EEFFencrypted files can maintain an encrypted state even when copied to network shares where the EEFF product is not running. Automatic encryption on discovered data: Endpoint discovery rules can be created within HDLP and assigned Encrypt and Monitor actions on sensitive data discovered. When sensitive data is discovered on a host, the files and/or data can be quarantined and automatically encrypted.
12
In this report card on integration, the Priority column has been removed, as the priority level of integration actions was too subjective.
Comments
All HDLP, NDLP and Encryption violation alerts can now be centrally monitored from within ePO. Numerous other reports in the ePO allow for collection and aggregation of alerts into single reports, providing a single pane of glass for all data incident information. Top-level tabs in the ePO Dashboards area provide immediate visibility into violations involving data at rest, in use and in motion. Violations can be broken down into several categories (e.g., severity and types of event). The Host DLP product is fully integrated with ePO at this time. The HDLP Policy Manager is available from within the System tab in ePO and can be used to create, modify, manage and monitor policies for host DLP agents. Full HDLP reporting is in place within ePO, as well. Today, both McAfees EEPC and EEFF are deployed and audited leveraging the ePO framework. However, client configuration for EEPC and EEFF is not yet integrated into ePO for centralized control, so it must be done outside ePO. The next software release migrates the EE key escrow into ePO and will provide for full client configuration within ePO. NDLP integrates into ePO to lesser extent than HDLP. ePO can now consolidate NDLP reports into the Dashboards tab, and the NDLP management console can be launched directly from within ePO. Multiple levels of NDLP reporting detail are available in ePO without having to launch the console. Additional integration of NDLP into ePO is planned for the next release cycle. Although not fully integrated, an important feature has been added into NDLP 8.5 that relates to HDLP and EE capabilities. Known as Discover Remediation, this feature allows an administrator to leverage NDLP Discover to search for sensitive data at rest within the network environment (a critical automation point because no IT person knows how or where to find critical data outside the database). When critical data types are discovered, administrators can take actions based on context and situation. For example, upon discovery of sensitive data on a file share, an administrator using the NDLP Discover management interface could elect to move, copy, encrypt, and/or delete the data based on system recommendations. This capability is not fully automatic and still involves the administrator, which is actually by design, as most enterprises do not currently want fully automated remediation actions involving sensitive data. Policy and rule configuration is currently done from different management consoles for HDLP, NDLP and EE, although integration is planned for the next release. However, this may or may not be a big issue for organizations, because many still maintain a separation of duties and have distinct groups assigned to manage policy creation, rule/control development, and enforcement.
Grade
A
Workflow
Although not yet integrated into ePO, incidents involving data at rest, in use or in motion can now be investigated from within the NDLP Management console. All three event types can be added to cases, which can then be assigned to individual users/owners and have notes added to thema strong feature for forensics, audit and follow-up. Extensive details from each incident are maintained with the cases in a chain of custody fashion, and the McAfee Capture capabilities provide updates on data movement and disposition over time. In addition, the easy-to-use workflow system allows multiple administrators and role-specific users to monitor and manage different aspects of each incident and case until its resolved. McAfee plans additional case and incident workflow integration within ePO in next release.
13
14
15
16