McAfee Endpoint Encryption for PC version 5.2.6 with McAfee Endpoint Encryption Manager version 5.2.6 is a Personal Computer (PC) security system that prevents the data stored on a PC’s internal or external storage media; including floppy disks, external hard drives, memory sticks, etc., from being read or used by an unauthorized person. In simple terms, the McAfee Endpoint Encryption Client takes control of a user’s storage media away from the operating system. The McAfee Endpoint Encryption Client encrypts data written to the storage media, and decrypts data read from it. If the storage media is read directly, one would find only encrypted data, even in the Windows swap file and temporary file areas. The McAfee Endpoint Encryption Manager provides the functionality to securely deploy, configure and manage the McAfee Endpoint Encryption Client.
","evaluation_configuration":null,"security_evaluation_summary":"The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) process and procedures. The evaluation demonstrated that the McAfee Endpoint Encryption for PC version 5.2.6 with McAfee Endpoint Encryption Manager version 5.2.6. meets the security requirements contained in the Security Target.
\r\nThe criteria against which the McAfee Endpoint Encryption for PC with McAfee Endpoint Encryption Manager Common Criteria Security Target, Version 1.23 was judged is described in the Common Criteria for Information Technology Security Evaluation, Version 3.1. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1. The COACT, Inc. CAFE Lab determined that the evaluation assurance level (EAL) for the McAfee Endpoint Encryption for PC with McAfee Endpoint Encryption Manager Common Criteria Security Target, Version 1.23 is EAL 4 + ALC_FLR.3. The TOE, configured as specified in the installation guide, satisfies all of the security functional requirements stated in the Security Target.
\r\nA team of Validators on behalf of the CCEVS Validation Body monitored the evaluation carried out by the COACT, Inc. CAFE Lab. The evaluation was completed in August 1, 2011. Results of the evaluation and associated validation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report.
","environmental_strengths":"The TOE’s Security Functions are:
\r\nA) User Access Control – The McAfee Endpoint Encryption Client replaces the master boot record on the bootable hard disk of the PC on which it is installed. So, when such a PC boots, the first code that gets loaded from the hard disk is the McAfee Endpoint Encryption Client and the user is presented with the McAfee Endpoint Encryption Client logon screen. At that point the user will be required to provide a valid user identifier and a valid, authenticated password before being granted access to the PC’s data.
\r\nB) Admin User Access Control – The TOE Manager supports identity-based access control to protect its assets from unauthorized access. Users require valid credentials in the form of a user name, login credentials and a token (either a physical token, in the case of the CAC and PIV smartcards, or a logical token, in the form of the password-only token).
\r\nC) User Authentication – When a user boots up a PC protected by McAfee Endpoint Encryption for PC, they boot into the “McAfee Endpoint Encryption Client OS”, which is effectively what the TOE Client bootcode is, providing a trusted, secure and controlled environment in which the user may present his credentials (such as a user identity and a password, or a user identity and smartcard and PIN) to the McAfee Endpoint Encryption Client for authentication.
\r\nD) TOE Manager User Authentication –When a management user logs onto a TOE Manager, the user must present his credentials (such as a user identity and a password, or a user identity and smartcard and PIN) to the McAfee Endpoint Encryption Manager for authentication. When the user logs on, the credentials that he supplies are authenticated.
\r\nE) Management of TOE by User – It is possible for a user to change his password as part of the logon process or from the McAfee Endpoint Encryption Client screen saver, as long as they present their existing password for authentication as part of the process. This makes use of the password authentication mechanism
\r\nF) Hard Disk Encryption - The McAfee Endpoint Encryption Client operating system starts the crypt driver in memory once the user has entered the correct authentication information. From this point on the machine will look and behave as if the McAfee Endpoint Encryption Client was not installed, with all disk access going through the McAfee Endpoint Encryption Client, such that data read from storage media is decrypted and data written to storage media is encrypted, using the hard disk encryption key of the TOE Client.
\r\nG) Hard Disk Encryption Key Management – The TOE Client generates its hard disk encryption key using a pseudo-random number generator based on DSS with a key size of 256 bits. The TSF destroys hard disk encryption keys by zeroing them when they are no longer in use, specifically when the TOE is uninstalled. The hard disk encryption key is stored encrypted (using AES and a key length of 256 bits) under a key derived from the user’s password. If the password changes, the hard disk encryption key is decrypted using the existing one and then encrypted for storage using the new password. The hard disk encryption key itself does not change in such circumstances. The hard disk encryption key is decrypted as required when needed to access data on the TOE Client PC storage media. This can only occur once a user has successfully logged on to the TOE Client.
\r\nH) Administrative Access Control – Management of TOE Clients is via the administration secure management interface. Any administrator wishing to manage a TOE Client must first establish a secure management session with that TOE Client. A proprietary protocol is used to establish a session key shared between the TOE Client and the TOE Manager. This is then used to encrypt a known value to authenticate the TOE Manager to the TOE Client and vice versa. This protocol incorporating the one-time session key and challenge-response mechanism provides a single-use authentication mechanism.
\r\nI) Secure Management – The user may change his own password, however the bulk of the management of the TOE functionality must be performed by an administrator.
\r\nJ) TOE Client Audit - The TOE Client maintains an audit log. This contains a list of events that have occurred on the TOE Client, and each entry consists of a timestamp, type of event, user ID of the user logged on at the time and the result of the event. The audit functions are always active while the TOE Client is operational. The audit log can only hold 3000 entries. When it is full, each new entry added results in the oldest entry in the log becoming overwritten. The audit log can only be viewed or cleared by authorized administrators, and he can choose to view the entries ordered on a number of factors, specifically: date and time, the event code, the object (machine or user) or the description of the audited event.
\r\nK) TOE Manager Audit - The TOE Manager maintains an audit log. This contains a list of events that have occurred on the TOE Manager, and each entry consists of a timestamp, type of event, user ID of the user logged on at the time and the result of the event. The size (capacity) of the TOE Manager audit log is only limited by the available hard disk space. If the audit log becomes full, no new entries are added. The audit log can only be viewed or cleared by authorized administrators, and he can choose to view the entries ordered on a number of factors, specifically: date and time, the event code, the object (machine or user) or the description of the audited event.
\r\nL) Self-Protection of the TOE – The TOE Client has a number of related functions that help to maintain its integrity under certain circumstances, such as hardware failure, or communications link failure. The TSF runs a suite of tests during initial start-up, and in the case of the random number generator test, continuously to demonstrate the correct operation of the security assumptions provided by the abstract machine that underlies the TSF. The TSF preserves a secure state when communications with the TOE Manager are unexpectedly terminated or when there is a power failure to the TOE Client. After a user account has been disabled or the user has forgotten their logon password when they try to logon, the TSF enters a maintenance mode where the ability to recover the normal functionality of the TOE Client is provided either online via a secure administration session, or offline using the offline recovery procedure.
\r\nM) McAfee Endpoint Encryption Manager – This function gives an authorized administrator access to a GUI that allows him to configure and manage the TOE. It also provides a user interface through which an authorized administrator may view or selectively review audit data from the TOE.
\r\n","features":[]}