UNCLASSIFIED
COMMON CRITERIA
CERTIFICATION REPORT
McAfee Endpoint Security 10.1.0 with ePolicy Orchestrator 5.3.1
3 June 2016
UNCLASSIFIED
FOREWORD
This certification report is an UNCLASSIFIED publication, issued under the authority of the Chief,
Communications Security Establishment (CSE). Suggestions for amendments should be forwarded through
departmental communications security channels to your Client Services Representative at CSE.
The Information Technology (IT) product identified in this certification report, and its associated certificate, has
been evaluated at an approved evaluation facility – established under the Canadian Common Criteria Scheme –
using the Common Methodology for Information Technology Security Evaluation, Version 3.1 Revision 4, for
conformance to the Common Criteria for Information Technology Security Evaluation, Version 3.1 Revision 4.
This certification report, and its associated certificate, applies only to the identified version and release of the
product in its evaluated configuration. The evaluation has been conducted in accordance with the provisions of
the Canadian CC Scheme, and the conclusions of the evaluation facility in the evaluation report are consistent
with the evidence adduced. This report, and its associated certificate, are not an endorsement of the IT product
by the Communications Security Establishment, or any other organization that recognizes or gives effect to this
report, and its associated certificate, and no warranty for the IT product by the Communications Security
Establishment, or any other organization that recognizes or gives effect to this report, and its associated
certificate, is either expressed or implied.
If your department has identified a requirement for this certification report based on business needs and would
like more detailed information, please contact:
ITS Client Services
Telephone: (613) 991-7654
E-mail: itsclientservices@cse-cst.gc.ca
UNCLASSIFIED
OVERVIEW
The Canadian Common Criteria Scheme provides a third-party evaluation service for determining the
trustworthiness of Information Technology (IT) security products. Evaluations are performed by a commercial
Common Criteria Evaluation Facility (CCEF) under the oversight of the Certification Body, which is managed by
the Communications Security Establishment.
A CCEF is a commercial facility that has been approved by the Certification Body to perform Common Criteria
evaluations; a significant requirement for such approval is accreditation to the requirements of ISO/IEC
17025:2005, the General Requirements for the Competence of Testing and Calibration Laboratories.
Accreditation is performed under the Program for the Accreditation of Laboratories - Canada (PALCAN),
administered by the Standards Council of Canada.
The CCEF that carried out this evaluation is CGI IT Security Evaluation & Test Facility.
By awarding a Common Criteria certificate, the CCS Certification Body asserts that the product complies with the
security requirements specified in the associated security target. A security target is a requirements specification
document that defines the scope of the evaluation activities. The consumer of certified IT products should
review the security target, in addition to this certification report, in order to gain an understanding of any
assumptions made during the evaluation, the IT product's intended environment, the evaluated security
functionality, and the testing and analysis conducted by the CCEF.
The certification report, certificate of product evaluation and security target are posted to the Certified Products
list (CPL) for the Canadian CC Scheme, and to the Common Criteria portal (the official website of the
International Common Criteria Project).
UNCLASSIFIED
TABLE OF CONTENTS
Executive Summary........................................................................................................................................1
1 Identification of Target of Evaluation......................................................................................................2
1.1 Common Criteria Conformance..................................................................................................................2
1.2 TOE description ..........................................................................................................................................2
1.3 TOE architecture.........................................................................................................................................2
2 Security policy .......................................................................................................................................3
2.1 Cryptographic functionality........................................................................................................................3
3 Assumptions and Clarifications of Scope.................................................................................................4
3.1 Usage and Environmental assumptions .....................................................................................................4
4 Evaluated Configuration.........................................................................................................................5
4.1 Documentation...........................................................................................................................................6
5 Evaluation Analysis Activities .................................................................................................................7
5.1 Development..............................................................................................................................................7
5.2 Guidance Documents .................................................................................................................................7
5.3 Life-cycle Support.......................................................................................................................................7
6 Testing Activities....................................................................................................................................8
6.1 Assessment of Developer Tests..................................................................................................................8
6.2 Conduct of Testing......................................................................................................................................8
6.3 Independent Functional Testing.................................................................................................................8
6.4 Independent Penetration Testing ..............................................................................................................9
7 Results of the Evaluation......................................................................................................................10
8 Supporting Content..............................................................................................................................11
8.1 List of Abbreviations................................................................................................................................ 11
8.2 References............................................................................................................................................... 12
UNCLASSIFIED
LIST OF FIGURES
Figure 1 TOE Architecture ....................................................................................................................................2
LIST OF TABLES
Table 1 TOE Identification.......................................................................................................................................2
Table 2 Cryptographic Module(s)............................................................................................................................3
UNCLASSIFIED
03 June 2016 1
EXECUTIVE SUMMARY
McAfee Endpoint Security 10.1.0 with ePolicy Orchestrator 5.3.1(hereafter referred to as the Target of
Evaluation (TOE)), from Intel Corporation, was the subject of this Common Criteria evaluation. The results of this
evaluation demonstrate that TOE meets the requirements of the conformance claim listed in Table 1 for the
evaluated security functionality.
The TOE is a security management solution that runs on Windows-based computers (clients) to identify and stop
threats automatically. These threats include malware, suspicious communications, unsafe websites, and
downloaded files. The TOE intercepts threats, monitors overall system health, and reports detection and status
information.
The management capabilities for the TOE are provided by ePolicy Orchestrator (ePO) which manages TOE
software residing on client (managed) systems. A centralized but distributed architecture allows the TOE
software to be centrally managed and yet decrease network traffic required to manage clients. ePO provides the
management interface and functionality for the administrators of the TOE. It also provides centralized audit
collection and review functionality.
CGI IT Security Evaluation & Test Facility is the CCEF that conducted the evaluation. This evaluation was
completed on 03 June 2016 and was carried out in accordance with the rules of the Canadian Common Criteria
Scheme.
The scope of the evaluation is defined by the security target, which identifies assumptions made during the
evaluation, the intended environment for TOE, and the security functional/assurance requirements. Consumers
are advised to verify that their operating environment is consistent with that specified in the security target, and
to give due consideration to the comments, observations and recommendations in this certification report.
Communications Security Establishment, as the Certification Body, declares that the TOE evaluation meets all
the conditions of the Arrangement on the Recognition of Common Criteria Certificates and that the product will
be listed on the Certified Products list (CPL) and the Common Criteria portal (the official website of the
International Common Criteria Project).
UNCLASSIFIED
03 June 2016 2
1 IDENTIFICATION OF TARGET OF EVALUATION
The Target of Evaluation (TOE) is identified as follows:
Table 1 TOE Identification
TOE Name and Version McAfee Endpoint Security 10.1.0 with ePolicy Orchestrator 5.3.1
Developer Intel Corporation
Conformance Claim EAL 2+ (ALC_FLR.2)
1.1 COMMON CRITERIA CONFORMANCE
The evaluation was conducted using the Common Methodology for Information Technology Security Evaluation,
Version 3.1 Revision 4, for conformance to the Common Criteria for Information Technology Security Evaluation,
Version 3.1 Revision 4.
1.2 TOE DESCRIPTION
The TOE is a security management solution that runs on Windows-based computers (clients) to identify and stop
threats automatically. These threats include malware, suspicious communications, unsafe websites, and
downloaded files. The TOE intercepts threats, monitors overall system health, and reports detection and status
information.
The management capabilities for the TOE are provided by ePolicy Orchestrator (ePO) which manages TOE
software residing on client (managed) systems. A centralized but distributed architecture allows the TOE
software to be centrally managed and yet decrease network traffic required to manage clients. ePO provides the
management interface and functionality for the administrators of the TOE. It also provides centralized audit
collection and review functionality.
1.3 TOE ARCHITECTURE
A diagram of the TOE architecture is as follows:
Figure 1 TOE Architecture
UNCLASSIFIED
03 June 2016 3
2 SECURITY POLICY
The TOE implements policies pertaining to the following security functional classes:
• Client Threat Prevention
• Client Communications Protection
• Client Web Protection
• Identification and Authentication
• Management
• Audit
• Protected Data Transfer
Complete details of the security functional requirements (SFRs) can be found in the Security Target (ST).
2.1 CRYPTOGRAPHIC FUNCTIONALITY
The following cryptographic modules were evaluated by the CMVP and implemented in the TOE:
Table 2 Cryptographic Module(s)
Cryptographic Module Certificate Number
OpenSSL FIPS Object Module (v2.0.8) #1747
RSA BSAFE(R) Crypto-C Micro Edition #2097
UNCLASSIFIED
03 June 2016 4
3 ASSUMPTIONS AND CLARIFICATIONS OF SCOPE
Consumers of the TOE should consider assumptions about usage and environmental settings as requirements
for the product’s installation and its operating environment. This will ensure the proper and secure operation of
the TOE.
3.1 USAGE AND ENVIRONMENTAL ASSUMPTIONS
The following assumptions are made regarding the use and deployment of the TOE:
• The TOE has access to all the IT System data it needs to perform its functions.
• The TOE is appropriately scalable to the number of IT Systems the TOE manages.
• The TOE will be managed in a manner that allows it to appropriately address changes in the IT System
the TOE manages.
• Managed systems will securely download reputation values for URLs and domains and safety ratings for
websites in real-time through the McAfee GTI service.
• The processing resources of the TOE will be located within controlled access facilities, which will prevent
unauthorized physical access.
• There will be one or more competent individuals assigned to manage the TOE and the security of the
information it contains.
• The authorized administrators are not careless, willfully negligent, or hostile, and will follow and abide
by the instructions provided by the TOE documentation.
• The TOE hardware and software critical to security policy enforcement will be protected from
unauthorized physical modification.
• The external database will utilize SSL communication with the ePO server to protect system data.
• Management sessions will utilize HTTPS communication between the authorized administrator’s web
browser and the ePO web server to protect management session data.
• Administrators will implement secure mechanisms for receiving and validating updated signature files
from McAfee, and for distributing the updates to the central management systems.
UNCLASSIFIED
03 June 2016 5
4 EVALUATED CONFIGURATION
The evaluated configuration for the TOE comprises:
McAfee Endpoint Security 10.1.0 with ePolicy Orchestrator 5.3.1, with these extensions installed:
• Endpoint Security Platform 10.1.0 Extension, including:
• Threat Prevention Extension 10.1.0
• Firewall Extension 10.1.0
• Web Control Extension 10.1.0
Running on a server with Windows Server 2008 R2 SP1 (Enterprise, Standard, Datacenter)
McAfee Endpoint Security Client 10.1.0, including:
• Threat Prevention Client 10.1.0
• Firewall Client 10.1.0
• Web Control Client 10.1.0
Running on a GPC/Server with the following supported operating systems;
• Windows 8.1
• Windows 8
• Windows 7 SP1
• Windows Server 2012 (R2, R2 Update 1)
• Windows Server 2008 (SP2, R2)
UNCLASSIFIED
03 June 2016 6
McAfee Agent Version 5.0.2
Running on a GPC/Server with the following supported operating systems;
• Windows 8.1
• Windows 8
• Windows 7 SP1
• Windows Server 2012 (R2, R2 Update 1)
• Windows Server 2008 (SP2, R2)
With support from one of the following Database Management Servers in the environment:
• Microsoft SQL Server 2008 R2 Enterprise with Service Pack 1
• Microsoft SQL Server 2008 R2 Express with Service Pack 1
• Microsoft SQL Server 2008 R2 Standard with Service Pack 1
• Microsoft SQL Server 2008 R2 Workgroup with Service Pack 1
4.1 DOCUMENTATION
The following documents are provided to the consumer to assist in the configuration and installation of the TOE:
a. Operational User Guidance and Preparative Procedures Supplement: McAfee Endpoint Security 10.1.0
with ePolicy Orchestrator 5.3.1, version 1.2, 19 April 2016
b. Product Guide: McAfee ePolicy Orchestrator 5.3.0 Software
c. Installation Guide: McAfee ePolicy Orchestrator 5.3.0 Software
d. Product Guide: McAfee Agent 5.0.1 For use with McAfee ePolicy Orchestrator
e. Installation Guide: McAfee Endpoint Security 10.1.0 For use with ePolicy Orchestrator software and the
McAfee Security Center
f. Product Guide: McAfee Endpoint Security 10.1
UNCLASSIFIED
03 June 2016 7
5 EVALUATION ANALYSIS ACTIVITIES
The evaluation analysis activities involved a structured evaluation of the TOE. Documentation and process
dealing with Development, Guidance Documents, and Life-Cycle Support were evaluated.
5.1 DEVELOPMENT
The evaluators analyzed the TOE functional specification and design documentation; they determined that the
design completely and accurately describes the TOE security functionality (TSF) interfaces, the TSF subsystems
and how the TSF implements the security functional requirements (SFRs). The evaluators analyzed the TOE
security architectural description and determined that the initialization process is secure, that the security
functions are protected against tamper and bypass, and that security domains are maintained. The evaluators
also independently verified that the correspondence mappings between the design documents are correct.
5.2 GUIDANCE DOCUMENTS
The evaluators examined the TOE preparative user guidance and operational user guidance and determined that
it sufficiently and unambiguously describes how to securely transform the TOE into its evaluated configuration
and how to use and administer the product. The evaluators examined and tested the preparative and
operational guidance, and determined that they are complete and sufficiently detailed to result in a secure
configuration.
Section 4.1 provides details on the guidance documents.
5.3 LIFE-CYCLE SUPPORT
An analysis of the TOE configuration management system and associated documentation was performed. The
evaluators found that the TOE configuration items were clearly marked.
The evaluators examined the delivery documentation and determined that it described all of the procedures
required to maintain the integrity of the TOE during distribution to the consumer.
The evaluators reviewed the flaw remediation procedures used by developer for the TOE. During a site visit, the
evaluators also examined the evidence generated by adherence to the procedures. The evaluators concluded
that the procedures are adequate to track and correct security flaws, and distribute the flaw information and
corrections to consumers of the TOE.
UNCLASSIFIED
03 June 2016 8
6 TESTING ACTIVITIES
Testing consists of the following three steps: assessing developer tests, performing independent functional tests,
and performing penetration tests.
6.1 ASSESSMENT OF DEVELOPER TESTS
The evaluators verified that the developer has met their testing responsibilities by examining their test evidence,
and reviewing their test results, as documented in the ETR.
The evaluators analyzed the developer’s test coverage analysis and found it to be complete and accurate. The
correspondence between the tests identified in the developer’s test documentation and the functional
specification was complete.
6.2 CONDUCT OF TESTING
The TOE was subjected to a comprehensive suite of formally documented, independent functional and
penetration tests. The detailed testing activities, including configurations, procedures, test cases, expected
results and observed results are documented in a separate Test Results document.
6.3 INDEPENDENT FUNCTIONAL TESTING
During this evaluation, the evaluator developed independent functional tests by examining design and guidance
documentation.
All testing was planned and documented to a sufficient level of detail to allow repeatability of the testing
procedures and results. The following testing activities were performed:
a. Repeat of Developer's Tests: The evaluator repeated a subset of the developers tests;
b. Management of TSF Data: The evaluator verified that the TSF Data Access Permissions for ePO TOE Data
claimed in the ST is accurately specified.
6.3.1 FUNCTIONAL TEST RESULTS
The developer’s tests and the independent functional tests yielded the expected results, providing assurance
that the TOE behaves as specified in its ST and functional specification.
UNCLASSIFIED
03 June 2016 9
6.4 INDEPENDENT PENETRATION TESTING
Subsequent to the independent review of public domain vulnerability databases and all evaluation deliverables,
limited independent evaluator penetration testing was conducted. The penetration tests focused on:
a. Use of automated vulnerability scanning tools to discover potential network, platform and application
layer vulnerabilities such as Heartbleed, Shellshock, FREAK, POODLE, and GHOST; and
b. Session management: The evaluator attempted to access closed admin sessions using the Back/Forward
browser buttons.
6.4.1 PENETRATION TEST RESULTS
The independent penetration testing did not uncover any exploitable vulnerabilities in the intended operating
environment.
UNCLASSIFIED
03 June 2016 10
7 RESULTS OF THE EVALUATION
This evaluation has provided the basis for the conformance claim documented in Table 1. The overall verdict for
the evaluation is PASS. These results are supported by evidence in the ETR.
The IT product identified in this report has been evaluated at an approved evaluation facility established under
the Canadian Common Criteria Evaluation and Certification Scheme using the Common Methodology for IT
Security Evaluation, Version 3.1 Revision 4, for conformance to the Common Criteria for IT Security Evaluation,
Version 3.1 Revision 4. These evaluation results apply only to the specific version and release of the product in
its evaluated configuration and in conjunction with the complete certification report.
The evaluation has been conducted in accordance with the provisions of the Canadian Common Criteria
Evaluation and Certification Scheme and the conclusions of the evaluation facility in the evaluation report are
consistent with the evidence adduced. This is not an endorsement of the IT product by CSE or by any other
organization that recognizes or gives effect to this certificate, and no warranty of the IT product by CSE or by any
other organization that recognizes or gives effect to this certificate, is expressed or implied.
UNCLASSIFIED
03 June 2016 11
8 SUPPORTING CONTENT
8.1 LIST OF ABBREVIATIONS
Term Definition
CAVP Cryptographic Algorithm Validation Program
CCEF Common Criteria Evaluation Facility
CCS Canadian Common Criteria Evaluation and Certification Scheme
CM Configuration Management
CMVP Cryptographic Module Validation Program
CSE Communications Security Establishment
EAL Evaluation Assurance Level
ETR Evaluation Technical Report
GC Government of Canada
IT Information Technology
ITS Information Technology Security
ITSET Information Technology Security Evaluation and Testing
PALCAN Program for the Accreditation of Laboratories – Canada
PP Protection Profile
SFR Security Functional Requirement
ST Security Target
TOE Target of Evaluation
TSF TOE Security Function
UNCLASSIFIED
03 June 2016 12
8.2 REFERENCES
Reference
CCS Publication #4, Technical Oversight, Version 1.8, October 2010.
Common Criteria for Information Technology Security Evaluation, Version 3.1 Revision 4, September 2012.
Common Methodology for Information Technology Security Evaluation, CEM, Version 3.1 Revision 4,
September 2012.
Security Target: McAfee Endpoint Security 10.1.0 with ePolicy Orchestrator 5.3.1, v1.6, 4 May 2016
McAfee Endpoint Security 10.1.0 with ePolicy Orchestrator 5.3.1 Common Criteria EAL 2+ Evaluation Technical
Report, v1.0, 3 June 2016