User Guide
DDOC0099-000-AH
DTS1 CSfC
2 - 4
Overview
© 2020 Curtiss-Wright Defense Solutions
Revision 5.0
2.2
Protocols
The DTS1 supported protocols include Telnet, TFTP, CIFS, NFS, FTP, HTTP, DHCP, SNMP, and
iSCSI in addition to its RS-232 console port. The CIFS and NFS protocols are enabled by default,
all others are disabled. The unit also supports SSH, which is always enabled. The user can enable
the desired protocols to support their application. Refer to paragraph 12.3.27
for additional
information.
The FDEEEcPP20 and FDEAAcPP20 Protection Profiles did not consider, nor did they include
networking protocols as part of the security functional requirements, and as a result, did not
include any requirements for addressing those protocols.
Therefore, as per the FDEEEcPP20 and FDEAAcPP20, the protocols have not been examined as
part of the required assurance activities and consequently the evaluation can make no claims
about the DTS1’s networking protocols.
It is suggested that a customer using the product consider the impact of utilizing remote
administration via SSH across the network (rather than through the console) based upon their
specific use case. The customer should factor into their risk management decision the
environment in which the DTS1 operates (dedicated, segregated, private network versus residing
in a Demilitarized Zone [DMZ] accessible to the Internet), and the value of data to be protected.
2.3
CSfC Encryption
Commercial Solutions for Classified (CSfC) encryption is based on a National Security Agency (NSA)
specification. The CSfC program requires multi-layered security. Hardware data encryption is used for
the first security layer. The second security layer is software data encryption. Both encryption processes
are performed in the DTS1, one in the HW crypto module, the other by the Processor. The hardware
encryption key is retained in the DTS1 crypto module memory, the software encryption key is stored on
the RMC module.
2.3.1
Hardware Encryption Layer
CAUTION
DATA LOSS. If the Specific User Token Key is lost, the user account will be rendered unusable.
NOTE
Refer to paragraph 5.3
for information regarding the actual
commands and procedures used to create and log into the hardware encryption layer.
2.3.1.1
Account Creation
Before use, an account must be created (Figure 2.6) on the DTS1 Hardware Encryption (HWE)
layer. To start the account creation, the user logs into the DTS1 via the Command Line Interface
(CLI). Once logged in, additional commands are entered to create an account on the DTS1 HWE
layer. The HWE layer contains a Pre-Shared Key (PSK) which is generated at initial equipment
power-on at the manufacturer and provided separately by Curtiss-Wright. The PSK cannot be read
out of the DTS1. When the account is created, a user token key is internally generated by the
HWE layer. The layer then keywraps the user token key using the PSK and supplies it to the end
user through the CLI. The keywrapped user token key is validated on a third-party system by
comparing the DTS1-generated HMAC and the third-party-generated HMAC. If both match, the
user token is unwrapped using the PSK. The unwrapped user token key is then used in
subsequent logins as the specific-user token.