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 •
6
1
Introduction
This document provides administrative guidance for the
ASURRE-S
tor
®
2.5” Solid State enc
rypting hard drive, hereafter
denoted TOE
or
ASURRE-S
tor
®
SSD. The document describes how to identify the product, install it in a typical host
system, and describes the steps necessary to begin the initial secure configuration of the TOE. The document is
intended for use by the Administrator or Crypto Officer responsible for configuring the product prior to field
deployment.
The reader may notice that the document refers to a value called the BEV. The BEV is a term that originated in the FDE
Collaborative Protection Profile and stands for Border Encryption Value. The BEV performs the same function in the
ASURRE-S
tor
®
SSD as a KEK (Key Encryption Key) and is used to decrypt the media DEK (Data Encryption Key). The
document uses the terms BEV and KEK interchangeably.
2
Product Description
The Mercury Systems
ASURRE-S
tor
®
SSD
is a secure solid state hard drive. A hard drive is a storage device used in
computers as the primary booting device to load the Operating System or as a device to store large amounts of data. In
the simplest of terms, the
ASURRE-S
tor
®
SSD is a highly secure version of an industry standard 2.5” SATA hard drive.
Unlike most other secure solid state drive products, the Mercury Systems
ASURRE-S
tor
®
SSD does not depend on a
TPM module, TCG, or OPAL to implement security. Instead the
ASURRE-S
tor
®
SSD implements security using
hardware-based AES-256 XTS encryption and key management techniques that are compatible with the industry
standard ATA specification. These techniques provide superior and flexible solutions for mission critical defense
applications and have no requirements for unencrypted shadow MBR sectors or 3
rd
party Opal software.
The
ASURRE-S
tor
®
SSD was evaluated against the Common Criteria 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.
3
Product Configuration and Deployment
The Mercury Systems
ASURRE-S
tor
®
SSD is shipped with the optional MDU configuration utility. While the MDU
provides an easier-to-use method of performing some of the required administrative configuration functions, the MDU
is a utility provided by Mercury that is not part of the evaluated configuration and this should be taken into account by
users of the system. The use of this utility was not evaluated. Therefore, the interfaces used as part of the evaluation
are the direct SATA interfaces.
The programmer's guide and security configuration programmer's guide describe the administrative interface that is
used in the evaluated configuration that was tested. The configuration instructions for activities mandated by the ST
are provided in this document; locations of the instructions are given by reference to the programmer's guides, and for
convenience some references using the MDU visual interface are given as well.
4
Deployed TOE usage scenario
:
The TOE usage scenario is a re-occurring mission model. The TOE supports two CC compliant modes of operation:
1.
ATA password with Self-generated Permanent key (Mode 1)
2.
ATA Password with KEK and BLACK key (Mode 6)
Mode 1: ATA password with Self-generated Permanent key
This scenario begins with the Crypto Officer (CO) configuring the TOE in a secure location using MDU or a similar
custom utility program. The CO configures the TOE to operate in Mode 1. The TOE uses a hardware based NDRNG and
a DRBG algorithm to self-generate a random DEK. The DEK consists of a 256-bit AES key and a different 256-bit XTS key.
The CO enters a password of up to 64 characters. The TOE conditions the password with PBKDF (Password Based Key
Derivation Function SP 800-132) to create a derived 256-bit key (BEV/KEK) that the TOE uses to AES key wrap (AES-KW-
