Assurance Continuity - Seagate Secure TCG SSC Self-Encrypting Drives
Date of Maintenance Completion: 2020.09.28CC 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 the 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:
In the updated ST, version 9, Table 2 shows the two new Product Names (Nytro® 2032 SSD and Nytro® 3032 SSD), with the 23 new models split between them, Balto ASIC, new firmware version 0001, and ‘Firmware implementations (for each model) as identified by CAVP’. This table shows only 4 firmware implementations, all Balto ASIC. Table 3 shows that the 23 new models are in the first column/group of models select 11 different firmware implementations. It appears that the other 7 firmware implementations are for the older models. The IAR is silent on the firmware implementations but does specify the new firmware version 0001. It should also be noted that the 4 firmware implementations for the 23 new models in the two new products are not new and are used in older models.
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 models and the new firmware version.
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 version. These changes included changes to comply with a customer request, to fix a bug for a hang condition, a logging reliability issue, and a drive hang condition. None of the changes were security relevant.
Seagate Security Certification Contracts
+1 (952) 402-2356