High Assurance Internet Protocol Encryptor: Difference between revisions

Revision as of 21:12, 18 August 2013

Revision as of 22:31, 9 September 2013

Line 11:

Examples of HAIPE devices include

* L-3 Communications' <ref name=L3>[http://www.l-3com.com/HAIPE L-3 HAIPE]</ref> [http://www.l-3com.com/HAIPE HAIPE]

** KG-245X 10Gbit/s (HAIPE IS v3.0.2),

** KG-245A fully tactical 1 Gbit/s (HAIPE IS v3.1.2 and Foreign Interoperable)

** KG-240A fully ruggedized 100 Mbit/s (HAIPE IS v3.1.2 and Foreign Interoperable)

** KOV-26 <ref name=L3>[http://www.l-3com.com/Talon L-3 Talon]</ref> [http://www.l-3com.com/Talon Talon]

* [http://www.viasat.com/government-communications/information-assurance ViaSat's AltaSec Products]<ref name="AltaSec KG-250">[http://www.viasat.com/government-communications/information-assurance/altasec-kg-250 ViaSat AltaSec KG-250]</ref>

** [http://www.viasat.com/government-communications/information-assurance/altasec-kg-250 KG-250],<ref name="AltaSec KG-250"/> and

** KG-255 [1 Gbit/s]<ref name=Viasat255datasheet>[http://www.viasat.com/files/assets/KG-255_datasheet_014.pdf ViaSat KG-255 Datasheet]</ref>

* [[General Dynamics]]' <ref name=ge>[http://www.gdc4s.com/content/detail.cfm?item=f3f0ef4c-cced-46b2-937e-69c42fd1fe3b TACLANE Encryptor (KG-175)]</ref> [[TACLANE]] KG-175.

*Cassidian's ECTOCRYP Transparent Cryptography <ref name="ECTOCRYP Transparent Cryptography">[http://www.cassidian.co.uk] ECTOCRYP Transparent Cryptography</ref><ref>[http://www.cassidian.co.uk/ectocryp ]{{dead link|date=September 2013}}</ref>

Three of these devices are compliant to the HAIPE IS v3.0.2 specification while the remaining devices use the HAIPE IS version 1.3.5, which has a couple of notable limitations: no support for [[routing protocols]] or open [[network management]]. A HAIPE is an IP encryption device, looking up the destination IP address of a packet in its internal Security Association Database (SAD) and picking the encrypted tunnel based on the appropriate entry. For new communications, HAIPEs use the internal Security Policy Database (SPD) to set up new tunnels with the appropriate algorithms and settings. By not supporting routing protocols the HAIPEs must be preprogrammed with [[static routing|static routes]] and cannot adjust to changing network topology. While manufacturers support centralized management of their devices through proprietary software,<ref>[http://www.viasat.com/government-communications/information-assurance/viasat-ine-manager-software-vine ViaSat's VINE website]</ref><ref>[http://www.gdc4s.com/content/detail.cfm?item=45b9abed-a178-486e-908b-28f858754155 General Dynamics's GEM website]</ref> the current devices offer no management functionality through open protocols or standards. Recently [http://www.telegrid.com TELEGRID Technologies] <ref>[http://www.telegrid.com TELEGRID Technologies]</ref> has produced a non proprietary manager [http://www.telegrid.com/TELEGRID_SMRT_Flyer.pdf SMRT] for multiple HAIPE encryptors including the KG-175D, KG-250 and SecNet 54 in addition to the KIV-7M LEF encryptor.<ref>[http://www.telegrid.com/TELEGRID_SMRT_Flyer.pdf SMRT MULTIPLE HAIPE REMOTE MANAGER]</ref> Both of these limitations are due to be addressed in HAIPE IS version 3.0 due to be accredited in late 2008, but that date has slipped multiple times.{{Citation needed|date=April 2008}} Both the HAIPE IS v3 management and HAIPE device implementations are required to be compliant to the HAIPE IS version 3.0 common MIBs. Assurance of cross vendor interoperability may require additional effort. An example of a management application that supports HAIPE IS v3 is the <ref name=L3>[http://www.l-3com.com/HAIPE Common HAIPE Manager]</ref> [http://www.l-3com.com/HAIPE Common HAIPE Manager].

A couple of new HAIPE devices will combine the functionality of a router and encryptor when HAIPE IS version 3.0 is approved. General Dynamics has completed its TACLANE version (KG-175R), which house both a red and a black Cisco router, and both ViaSat and L-3 Communications are coming out with a line of network encryptors at version 3.0 and above. Cisco has dropped its plans for producing its own HAIPE device.{{Citation needed|date=March 2008}}

There is a UK HAIPE variant that implements UKEO algorithms in place of US Suite A. Cassidian has entered the HAIPE market in the UK with its Ectocryp range [.<ref>http://www.eadsdsuk.com/ectocryp/].</ref> Ectocryp Blue is HAIPE version 3.0 compliant and provides a number of the HAIPE extensions as well as support for network [[quality of service]] (QoS). Harris has also entered the UK HAIPE market with the BID/2370 End Cryptographic Unit (ECU).<ref name=bid2370>[http://www.rfcomm.harris.com/products/embeddable-security/chimp.pdf Harris UK BID/2370 ECU]</ref>

In addition to site encryptors HAIPE is also being inserted into client devices that provide both wired and wireless capabilities. Examples of these include L-3 Communication's KOV-26 [http://www.l-3com.com/cs-east/ia/talon/ie_ia_talon.shtml Talon] and [http://www.l-3com.com/cs-east/ia/smeped/ie_ia_smeped.shtml Guardian] SME-PED, and [[Harris Corporation]]'s <ref name=harris>[http://www.rfcomm.harris.com/products/embeddable-security/ Harris KIV-54]</ref> KIV-54 and PRC-117G <ref name =PRC-117G>[http://www.rfcomm.harris.com/117G/ Harris PRC-117G]</ref> radio .

Line 33:

* [[NSA encryption systems]]

== References ==

{{Reflist|30em}}

[http://www.cnss.gov/Assets/pdf/CNSSP-19.pdf CNSS Policy #19 governing the use of HAIPE]

==External Footnoteslinks==

[http://www.cnss.gov/Assets/pdf/CNSSP-19.pdf CNSS Policy #19 governing the use of HAIPE]

{{Reflist|30em}}

[[Category:Cryptographic protocols]]