High Assurance Internet Protocol Encryptor: Difference between revisions

Revision as of 18:47, 20 April 2016

Revision as of 16:03, 2 February 2017

Line 21:

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 [[Network packet|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/vine-manager-software ViaSat's VINE website]</ref><ref>[http://www.gdc4s.com/gem-x.html General Dynamics's GEM website]</ref> the current devices offer no management functionality through open protocols or standards.

[http://www.telegrid.com TELEGRID Technologies]<ref>[http://www.telegrid.com TELEGRID Technologies]</ref> produces a non proprietary Encryptor Management System for multiple [[Inline Network Encryptor|INE]], [[HAIPE]] and Mobile IP encryptors including the KIV-7M, GD KG-175D, ViaSat KG-250 and Harris SecNet54. The Encryptor Management System is known as the Secure Multi-web Remoting Tool (SMRT).<ref>[http://www.telegrid.com/TELEGRID_SMRT_Flyer.pdf TELEGRID SMRT Multiple HAIPE Remote Manager]</ref> The SMRT provides an encryptor management interface as well as a common crypto [[Management information base|MIB]] for remote management via [[SNMP]]. It also provides secure remote access to the management interfaces of the underlying encryptors.

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 L-3 Common HAIPE Manager.

Line 38 ⟶ 36:

==References==

{{Reflist}}

[https://www.rockwellcollins.com/Data/Products/Communications_and_Networks/Communication_Radios/AN-ARC-210_Gen_V_Programmable_Digital_Communication_System.aspx Rockwell Collins ARC-210]

==External links==