Assurance Continuity - Seagate Secure® TCG SSC Self-Encrypting Drives
Date of Maintenance Completion: 2022.06.10CC 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 + Errata 20190201
Original Evaluated TOE: 2021.12.02 - 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 Administrative Guide
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.
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. The new firmware versions added are shown in bold and italics in the validated firmware versions column.
There were no changes to the Development Environment.
Section 2.3. “Assurance Impact Determination” of the IAR specifies that there are a 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 TSF interface, no hardware changes, no SFR changes, no new security features, no changes to assumptions and objectives, and no new non-security features. The only changes that required updates to assurance evidence were the 1) update to the vulnerability assessment (AVA) and the 2) Security Target (ST) update to add the new firmware releases. Changes were also made to the KMD and EAR to add the new firmware releases and update any documentation references to the new version(s).
The IAR shows the there is one security relevant bug fix to allow commands to retrieve drive state information in the case where the security files have been corrupted. This change does not affect the underlying security architecture. All other fixes are not security relevant.
The only change to the TOE Environment was a minor maintenance action which required retesting but nothing more.
Seagate Technology, LLC