Mercury Systems
ASURRE
-Stor
®
SSD
Administrative Guidance
Copyright 2020 Mercury Systems. May only be reproduced in its original form (without revision)
Rev. 1.5.1 February 2020 © 2020 Mercury Systems. All rights reserved
Mercury Systems, Inc. • (602) 437-1520 •
11
13
Scope of evaluation
The
ASURRE-S
tor
®
SSD was evaluated to the security functional requirements specified in the
document “
Security
Target for Mercury Systems ASURRE-Stor
®
Solid State Self-
Encrypting Drives”
.
The TOE does not depend on a TPM (Trusted Platform Module) or OPAL (a security specification) to provide security.
Instead the TOE supports 6 FIPS 140-2 approved modes, of which, two modes satisfy the requirements of the
Collaborative Protection Profile for Full Drive Encryption - Encryption Engine, v2.0 dated January 2, 2019 and the
Collaborative Protection Profile for Full Drive Encryption
–
Authorization Acquisition, v2.0 dated January 2, 2019.
To provide consistency to the FIPS Security Policy documentation, the CC documentation for the
ASURRE-S
tor
®
SSD
uses the same numbering for the key management modes as the FIPS 140-2 Security Policy. Using the FIPS mode
numbering scheme, the TOE supports CC compliant modes of Mode 1 and Mode 6. No other key management modes
were evaluated during the course of the CC-Evaluation.
Mode #
Mode name
Key Chain
1
•
Self-generated random
Permanent key with ATA
Password
•
•
•
•
During configuration:
•
The TOE self-generates a random 256-bit AES key and different 256-bit XTS key for use as the media
DEK. A password is filled and is conditioned by PBKDF(SP 800-132) to create an intermediate
derived key that is used to AES key wrap (AES-KW-256,
SP 800‐38F
) the DEK. The wrapped DEK is
saved in NVRAM.
•
•
During normal operation:
•
On each power cycle, the password must fill. The TOE conditions the password with PBKDF to
create an intermediate derived key (BEV/KEK) that is then used to un-wrap (AES-KW-256,
SP 800‐
38F) the DEK previously saved in NVRAM.
6
•
ATA password with KEK
•
and BLACK key
•
•
Pre-configuration:
The CO creates two keys, a 256-bit BEV(KEK) and a 512-bit DEK. The DEK consists of a 256-bit AES
key and a different 256-bit XTS key. The CO creates a password of up to 64 characters. The CO
conditions the password using PBKDF (SP 800-132) to create a derived 256-bit key used to AES key
wrap (AES-KW-256,
SP 800‐38F)
the DEK to create the BLACK key.
•
During Configuration:
The CO fills the BEV(KEK) and password into the TOE. The TOE conditions the password with PBKDF
(SP 800-132) creating a derived 256-bit key used to AES key wrap (AES-KW-256,
SP 800‐38F)
the
BEV(KEK). The TOE saves the wrapped BEV(KEK) in NVRAM.
•
•
During normal operation:
•
On each power cycle, the user enters the password and BLACK key. The password is conditioned
with PBKDF creating a derived 256-bit key used to un-wrap the BEV/KEK previously saved in
NVRAM. The un-wrapped BEV/KEK is used to un-wrap the BLACK key to re-create the DEK.
Table 5: CC Compliant modes
14
Operating Environment
The
ASURRE-S
tor
®
SSD is compliant and compatible with the industry standard SATA specification and conforms to the
ATA7 specification and command set. The
ASURRE-S
tor
®
SSD will function correctly in all products that include a
standard SATA interface and are compliant to the SATA and ATA7 specification.
