Content deleted Content added
No edit summary |
No edit summary |
||
Line 17:
Cassidian's Ectocryp Blue compliant to Version 3 and above is capable of protecting [[TOP SECRET]] and below, including National Caveats such as UK Eyes Only. http://www.cassidian.co.uk/ectocryp-blue
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 TELEGRID Technologies <ref>[http://www.telegrid.com TELEGRID Technologies]</ref> has produced a non propritary manager 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}}
| |||