Assurance Continuity - Seagate Secure TCG SSC Self-Encrypting Drives
Date of Maintenance Completion: 2020.12.21CC Certificate Validation Report Assurance Activity
Product Type: Encrypted Storage
Conformance Claim: Protection Profile Compliant
PP Identifier: collaborative Protection Profile for Full Drive Encryption - Encryption Engine Version 2.0
Original Evaluated TOE: 2018.04.11 - Seagate Secure TCG SSC Self-Encrypting Drives
Please note: The above files are for the Original Evaluated TOE. Consequently, they do not refer to this maintained version, although they apply to the maintained version.
Security Target * Assurance Continuity Maintenance Report
Please note: This serves as an addendum to the VR for the Original Evaluated TOE.
* This is the Security Target (ST) associated with this latest Maintenance Release. To view previous STs for this TOE, click here.
Readers are reminded that the certification of this product (TOE) is the result of maintenance, rather than an actual re-evaluation of the product. Maintenance only considers the affect of TOE changes on the assurance baseline (i.e. the original evaluated TOE); maintenance is not intended to provide assurance in regard to the resistance of the TOE to new vulnerabilities or attack methods discovered since the date of the initial certificate. Such assurance can only be gained through re-evaluation.
Using a security impact analysis of the changes made to the TOE, which was provided by the developer, the CCEVS has determined that the impact of changes on the TOE are considered minor and that independent evaluator analysis was not necessary. A summary of the results can be found in the Maintenance Report, which is written in relation to the product's original validation report and Security Target. Readers are therefore reminded to read the Security Target, Validation Report, and the Assurance Maintenance Report to fully understand the meaning of what a maintained certificate represents.
Assurance Continuity Maintenance Report:
· The IAR specifies
· There are a relatively small number of changes to the validated TOE, and none of the changes impact the secure operation of the TOE. The assurance impact of these changes is minor. There are no changes to the development environment.
· Code change did not have any impact on the developer evidence of the validated TOE.
· The changes to the ST and other documents were limited to document version with the addition of the new firmware version.
Changes to TOE:
These code changes did not impact the crypto software and, therefore, did not require update to the CAVP certificates. There were no changes to the EAR except to add the new hardware firmware versions.
The products, models, and firmware versions are shown in the table below.
Code changes to the firmware were made to the validated TOE to support the new firmware versions. These changes were bug fix and performance improvements; in this case most of the changes were fixes for incorrect error/sense data reporting, log page errors, and drive hangs, and for performance optimization.
Seagate Security Certification Contracts
+1 (952) 402-2356