WhitePaper GovDef TRANSEC
WhitePaper GovDef TRANSEC
SECURITY
(TRANSEC)
Introduction
What is TRANSEC?
TRANSEC requires all network control channels and Management & Control
(M&C) data to be encrypted, and that any and all traffic engineering information
be obfuscated from an adversary. For example, TRANSEC requires a
communications channel to appear completely full to an adversary even if little
or no actual data is flowing. This is contrasted with communications security
(COMSEC); the actual communication (e.g. voice, video or data stream) is
encrypted, but certain header information is sent in the clear. While the
encryption is virtually impenetrable, the information in the IP header including
the source address, destination address and, most importantly, the Type of
Service (ToS) field are in the clear. With the IP header of an encrypted packet in
the clear, an adversary can determine how much of the traffic stream is voice,
video or data. More significantly, an adversary could determine when high-
priority flash-override traffic has been initiated and from which location.
Solution
The only solution for this vulnerability is to completely encrypt all Layer 2
information as well as any control information disseminated to the remotes. The
encryption methodology must be secure enough to thwart an adversary long
enough that the data becomes old and unusable. We have implemented
Federal Information Processing Standard (FIPS) 140-2 certified 256-bit keyed
Advanced Encryption Standard (AES) for all Layer 2 and control information. The
encryption of the Layer 2 frames has a side benefit of re-encrypting the data
payload. Therefore, the transmitted IP header itself is AES-encrypted.
Additionally, the ST Engineering iDirect TRANSEC TDMA slot is a fixed size, again
to obfuscate any traffic characteristics. This Layer 2 encryption solution solves all
existing control channel vulnerabilities. Our Layer 2 encryption method goes a
step beyond to feature over-the-air (OTA) key updates and a unique Layer 2
frame format, including an Initialization Vector that ensures randomization of
repetitive data streams. The net result is that adversaries are precluded from
detecting any repetitive pattern, which can aid in deciphering encryption
algorithms.
Challenge
Another vulnerability of a TDMA VSAT system is the concept of Hub and Remote
validation. In traditional SCPC architectures, a link remains active for very long
periods of time when it is established. Because these connections are fixed, and
there is a significant level of coordination between personnel commissioning the
SCPC, a high degree of confidence exists that an adversary is not trying to assume
the identity of a trusted entity. In TDMA networks, remotes are routinely coming
into and dropping out of the network. This is especially true of networks with
mobile or itinerant terminals where terminals are located in moving vehicles,
aircraft or maritime vessels. This type of dynamic environment gives an adversary
a greater opportunity to obtain a VSAT remote through licit or illicit channels, spoof
the device ID and insert a rogue remote into a secure network. Equally feasible is
an adversary acquiring a VSAT hub terminal and coaxing a blue force remote into
the adversary’s network.
Solution
To mitigate this risk, we have implemented X.509 digital certificates on TRANSEC
remotes. An X.509 certificate utilizes RSA public key cryptosystem. With this
cryptosystem, two related keys are generated: one private key and one public
key. The functionality of these keys is so that anything encrypted with the public
key can only be decrypted with the private key, and anything encrypted with
the private key can only be decrypted with the public key. In the ST Engineering
iDirect system, X.509 certificates can be generated via the NMS server.
Certificates are placed on all TRANSEC line cards and acquisition passphrases, a single, dynamic passphrase can
Protocol Processors as well as on the remotes. The hub be utilized across global networks.
system keeps the public keys of each remote configured to
operate on the hub, and the remotes have the public keys Additional Security Measures
of each hub device. During network acquisition, the remote
encrypts its X.509 certificate with its private key, and the FIPS 140-2
hub verifies by decrypting the certificate with the remote’s The FIPS 140-2 is a U.S. government security standard for
public key and vice versa. This process ensures a remote is accrediting cryptographic modules. The standard is
not only authorized to operate in the network, but that the published by the National Institute of Standards and
hub is a trusted entity. Technology (NIST).
With the release of our 9-Series Satellite Routers and Defense Line Cards, we have expanded our existing FIPS 140-2 certification from
Level 2 to Level 3 from our previous line of products. As part of the effort, we developed a TRANSEC module designed to meet the
stringent FIPS 140-2 Level 3 requirements as defined by NIST. Through hardware and software development, the embedded, and yet
independent, TRANSEC module on the 9-Series and DLCs operates through a separate and trusted path from all other interfaces on
the product. The module also features a strong physical security measure for tamper prevention and the capability to zeroize the
security keys or critical security parameters (CSPs) stored on the module itself. If required, the revocation or zeroization of the keys
can be accomplished either OTA by the hub operator or locally on the remote by authorized personnel.
One-Way Networks
We have further enhanced our TRANSEC capabilities by securing one-way broadcast transmissions. Based on their encapsulation
method, LEGS, the ST Engineering iDirect platform can provide the same level of security for one-way networks to that of two-way
networks as described earlier. The 900 and 9350, with its dual-demodulator support, are capable of dual-domain TRANSEC; the
ability to establish two independent chains of trust (sets of X.509s) between two different CAs.An example use case of this feature
would be one demodulator on a two-way TRANSEC network while the second demodulator receives a separate one-way
TRANSEC-secured broadcast. Elliptical Curve Cryptography (ECC) is used for key generation along with X.509 certificates for
authentication in each security domain.