UNCLASSIFIED / NON CLASSIFIÉ
566-EWA
COMMON CRITERIA CERTIFICATION REPORT
Dell EMC™ Data Domain® v7.2
26 September 2022
2
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
FOREWORD
This certification report is an UNCLASSIFIED publication, issued under the authority of the Chief, Communications Security
Establishment (CSE).
The Information Technology (IT) product identified in this certification report, and its associated certificate, has been
evaluated at an approved testing laboratory established under the Canadian Centre for Cyber Security (a branch of CSE).
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 Common
Criteria Program, and the conclusions of the testing laboratory 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 Canadian Centre for Cyber Security, 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 Canadian Centre for Cyber Security, or any other organization that recognizes or gives effect to this report,
and its associated certificate, is either expressed or implied.
If your organization has identified a requirement for this certification report based on business needs and would like more
detailed information, please contact:
Canadian Centre for Cyber Security
Contact Centre and Information Services
contact@cyber.gc.ca | 1-833-CYBER-88 (1-833-292-3788)
3
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
OVERVIEW
The Canadian Common Criteria Program provides a third-party evaluation service for determining the trustworthiness of
Information Technology (IT) security products. Evaluations are performed by a commercial Common Criteria Testing
Laboratory (CCTL) under the oversight of the Certification Body, which is managed by the Canadian Centre for Cyber
Security.
A CCTL 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, the General Requirements
for the Competence of Testing and Calibration Laboratories.
By awarding a Common Criteria certificate, the 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, 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 CCTL.
The certification report, certificate of product evaluation and security target are posted to the Common Criteria portal (the
official website of the International Common Criteria Program).
4
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
TABLE OF CONTENTS
EXECUTIVE SUMMARY .................................................................................................................................... 6
1 Identification of Target of Evaluation ........................................................................................................... 7
1.1 Common Criteria Conformance.......................................................................................................................... 7
1.2 TOE Description................................................................................................................................................. 7
1.3 TOE Architecture ............................................................................................................................................... 8
2 Security Policy......................................................................................................................................... 9
2.1 Cryptographic Functionality ............................................................................................................................... 9
3 Assumptions and Clarification of Scope ......................................................................................................10
3.1 Usage and Environmental Assumptions.............................................................................................................10
3.2 Clarification of Scope .......................................................................................................................................10
4 Evaluated Configuration............................................................................................................................11
4.1 Documentation.................................................................................................................................................11
5 Evaluation Analysis Activities....................................................................................................................12
5.1 Development....................................................................................................................................................12
5.2 Guidance Documents........................................................................................................................................12
5.3 Life-Cycle Support ............................................................................................................................................12
6 Testing Activities ....................................................................................................................................13
6.1 Assessment of Developer tests.........................................................................................................................13
6.2 Conduct of Testing...........................................................................................................................................13
6.3 Independent Testing.........................................................................................................................................13
6.3.1 Independent Testing Results .........................................................................................................................13
6.4 Vulnerability Analysis .......................................................................................................................................14
6.4.1 Vulnerability Analysis Results........................................................................................................................14
7 Results of the Evaluation ..........................................................................................................................15
7.1 Recommendations/Comments..........................................................................................................................15
8 Supporting Content..................................................................................................................................16
8.1 List of Abbreviations.........................................................................................................................................16
5
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
8.2 References.......................................................................................................................................................16
LIST OF FIGURES
TOE Architecture..................................................................................................................................................8
LIST OF TABLES
Table 1: TOE Identification ................................................................................................................................................7
Table 2: Cryptographic Implementation.............................................................................................................................9
6
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
EXECUTIVE SUMMARY
Dell EMC™ Data Domain® v7.2 (hereafter referred to as the Target of Evaluation, or TOE), from Dell EMC™ , was the subject
of this Common Criteria evaluation. A description of the TOE can be found in Section 1.2. The results of this evaluation
demonstrate that the TOE meets the requirements of the conformance claim listed in Section 1.1 for the evaluated security
functionality.
EWA-Canada is the CCTL that conducted the evaluation. This evaluation was completed on 26 September 2022 and was
carried out in accordance with the rules of the Canadian Common Criteria Program.
The scope of the evaluation is defined by the Security Target, which identifies assumptions made during the evaluation, the
intended environment for the 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.
The Canadian Centre for Cyber Security, as the Certification Body, declares that this evaluation meets all the conditions of
the Arrangement on the Recognition of Common Criteria Certificates and that the product is listed on the Certified Products
list (CPL) for the Canadian Common Criteria Program and the Common Criteria portal (the official website of the
International Common Criteria Program).
7
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
1 IDENTIFICATION OF TARGET OF EVALUATION
The Target of Evaluation (TOE) is identified as follows:
Table 1: TOE Identification
TOE Name and Version Dell EMC™ Data Domain® v7.2
Developer Dell EMC™
1.1 COMMON CRITERIA CONFORMANCE
The evaluation was conducted using the Common Methodology for Information Technology Security Evaluation, Version 3.1
Revision 5, for conformance to the Common Criteria for Information Technology Security Evaluation, Version 3.1 Revision 5.
The TOE claims the following conformance:
EAL 2+ (ALC_FLR.2)
1.2 TOE DESCRIPTION
The TOE is a series of disk-based inline deduplication appliances and gateways that optimize disaster recovery (DR) in the
enterprise environment. Data Domain deduplication technology integrates into existing Information Technology (IT) storage
infrastructures. It eliminates redundant data from each backup image and stores only unique data, thus reducing the amount
of physical storage required for backup.
8
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
1.3 TOE ARCHITECTURE
A diagram of the TOE architecture is as follows:
TOE Architecture
9
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
2 SECURITY POLICY
The TOE implements and enforces policies pertaining to the following security functionality:
 Security Audit
 Cryptographic Support
 User Data Protection
 Identification and Authentication
 Security Management
 Protection of the TSF
 Trusted Path
Complete details of the security functional requirements (SFRs) can be found in the Security Target (ST) referenced in
section 8.2.
2.1 CRYPTOGRAPHIC FUNCTIONALITY
The following cryptographic implementation is used by the TOE and has been evaluated by the CMVP:
Table 2: Cryptographic Implementation
Cryptographic Module/Algorithm Certificate Number
EMC Data Domain Crypto-C Micro Edition #2757
10
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
3 ASSUMPTIONS AND CLARIFICATION 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:
 Those responsible for the TOE must establish and implement procedures to ensure that logical networks are
protected in an appropriate manner
 Those responsible for the TOE must ensure that those parts of the TOE critical to security policy are protected from
any physical attack.
 Those responsible for the TOE must ensure that the TOE is delivered, installed, managed, and operated in a manner
which is consistent with IT security. There are an appropriate number of authorized administrators trained to
maintain the TOE, including its security policies and practices. Authorized administrators are non-hostile and follow
all administrator guidance.
3.2 CLARIFICATION OF SCOPE
Use of the following interfaces is not included in this evaluation and are disabled on the TOE by default:
 USB Port – All instances of the TOE are equipped with a Universal Serial Bus (USB) port that may be used by an
authorized administrator for DDOS system maintenance and updates. This port may also be used for connecting a
USB keyboard during configuration.
 FTP/FTPS – Authorized users can view system logs and alerts by accessing the TOE via File Transfer Protocol/File
Transfer Protocol Secure (FTP/FTPS).
 Telnet – Use of Telnet protocol is not permitted in the evaluated configuration of the TOE.
11
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
4 EVALUATED CONFIGURATION
The evaluated configuration for the TOE comprises:
TOE Software/Firmware DDOS (Data Domain Operating System) version 7.2.0.95-692608
TOE Hardware DD6900, DD9400, and DD9900
Environmental Support  DD Boost Backup Server with NetBackup 8.1 & DD BOOST 3.5.0.2 plugin
 Windows Authentication Server
4.1 DOCUMENTATION
The following documents are provided to the consumer to assist in the configuration and installation of the TOE:
a) Dell EMC DD OS, Version 7.2, Administration Guide, June 2021
b) Dell EMC DD OS, Version 7.x, DD OS USB Installation Guide, May 2020
c) Dell EMC DD OS, version 7.2, Command Reference Guide, December 2020
d) Dell EMC PowerProtect DD6900 System, Installation Guide, December 2020
e) Dell EMC PowerProtect DD9400 System, Installation Guide, December 2020
f) Dell EMC PowerProtect DD9900 System, Installation Guide, December 2020
g) Dell EMC Data Domain Boost for OpenStorage, Version 3.5, Administration Guide, December 2018
h) Dell EMC DDBoost for Partner Integration, Administration Guide, Version 7.2.0.50, June 2021
i) Dell EMC™ Data Domain® 7.2 Common Criteria Guidance Supplement, 29 July 2022, v1.9
12
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
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 documentation provided by the vendor; they determined that the design completely and
accurately describes the TOE security functionality (TSF) interfaces and how the TSF implements the security functional
requirements. The evaluators determined that the initialization process is secure, that the security functions are protected
against tamper and bypass, and that security domains are maintained.
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 the procedures required to
maintain the integrity of the TOE during distribution to the consumer.
13
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
6 TESTING ACTIVITIES
Testing consists of the following three steps: assessing developer tests, performing independent tests, and performing a
vulnerability analysis.
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 Evaluation Test Report (ETR). 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 TESTING
During this evaluation, the evaluator developed independent functional & penetration 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 developer's tests
b. Cryptographic Implementation Verification: The evaluator verified that the cryptographic implementation claimed
was present in the TOE
c. Authentication Input Validation: The evaluator verified that authentication input via the web interfaces is validated
by the TOE
d. Data Synchronization: The evaluator verified data remains synchronized during data transfer interruption
e. Audit Log Protection: The evaluator verified that log files cannot be modified by any user of the TOE
f. Active Directory Authentication: The evaluator verified that users are properly authenticated by the TOE using Active
Directory
6.3.1 INDEPENDENT TESTING RESULTS
The developer’s tests and the independent tests yielded the expected results, providing assurance that the TOE behaves as
specified in its ST and functional specification.
14
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
6.4 VULNERABILITY ANALYSIS
The vulnerability analysis focused on 4 flaw hypotheses.
 Public Vulnerability based (Type 1)
 Technical community sources (Type 2)
 Evaluation team generated (Type 3)
 Tool Generated (Type 4)
The evaluators conducted an independent review of all evaluation evidence, public domain vulnerability databases and
technical community sources (Type 1 & 2). Additionally, the evaluators used automated vulnerability scanning tools to
discover potential network, platform, and application layer vulnerabilities (Type 4). Based upon this review, the evaluators
formulated flaw hypotheses (Type 3), which they used in their vulnerability analysis.
Type 1 & 2 searches were conducted on 20 April 2022 and included the following search terms:
data domain Apache Tomcat 9.0.62 log4j 2.17.1 openssl 1.0.2zd
dd os 7.2.0.90 JRE 1.8u321 Dell BSafe
Apache 2.4.53 Java SE 8 Update 321 Openssh 8.6
Vulnerability searches were conducted using the following sources:
National Vulnerability Database:
https://nvd.nist.gov/vuln/search
Apache HTTP:
https://httpd.apache.org/security/vulnerabilities_24.html
Apache Tomcat:
https://tomcat.apache.org/security-9.html
OpenSSL:
https://www.openssl.org/news/vulnerabilities-1.0.2.html
OpenSSH:
https://www.openssh.com/security.html
EMC support:
https://support.emc.com/
6.4.1 VULNERABILITY ANALYSIS RESULTS
The vulnerability analysis did not uncover any security relevant residual exploitable vulnerabilities in the intended operating
environment.
15
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
7 RESULTS OF THE EVALUATION
The Information Technology (IT) product identified in this certification report, and its associated certificate, has been
evaluated at an approved testing laboratory established under the Canadian Centre for Cyber Security. This certification
report, and its associated certificate, apply only to the specific version and release of the product in its evaluated
configuration.
This evaluation has provided the basis for the conformance claim documented in Table 1. The overall verdict for this
evaluation is PASS. These results are supported by evidence in the ETR.
7.1 RECOMMENDATIONS/COMMENTS
It is recommended that all guidance outlined in Section 4.1 be followed to configure the TOE in the evaluated configuration.
16
TLP:WHITE
UNCLASSIFIED / NON CLASSIFIÉ
8 SUPPORTING CONTENT
8.1 LIST OF ABBREVIATIONS
Term Definition
CAVP Cryptographic Algorithm Validation Program
CCTL Common Criteria Testing Laboratory
CMVP Cryptographic Module Validation Program
CSE Communications Security Establishment
EAL Evaluation Assurance Level
ETR Evaluation Technical Report
IT Information Technology
ITS Information Technology Security
PP Protection Profile
SFR Security Functional Requirement
ST Security Target
TOE Target of Evaluation
TSF TOE Security Function
8.2 REFERENCES
Reference
Common Criteria for Information Technology Security Evaluation, Version 3.1 Revision 5, April 2017.
Common Methodology for Information Technology Security Evaluation, CEM, Version 3.1 Revision 5, April 2017.
Security Target Dell EMC™ Data Domain® v7.2, 26 September 2022 v1.17
Evaluation Technical Report Dell EMC™ Data Domain® v7.2, 26 September 2022 v1.2