EncrypTight acts as a transparent overlay that
integrates easily into any existing network
architecture, providing encryption rules and keys
to EncrypTight Enforcement Points.
EncrypTight consists of a suite of tools that performs various tasks of
appliance and policy management, including Policy Manager (PM),
Key Management System (KMS), and EncrypTight Enforcement Points
ET0010A
ET0100A
ET1000A
(ETEPs).
Customer
Support
Information
Order toll-free in the U.S.: Call 877-877-BBOX (outside U.S. call 724-746-5500)
FREE technical support 24 hours a day, 7 days a week: Call 724-746-5500 or fax 724-746-0746
Mailing address: Black Box Corporation, 1000 Park Drive, Lawrence, PA 15055-1018
Web site: w ww.blackbox.com • E-mail : info@blackbox.com
Next Steps............................................................................................................................................ 58
Editing a Policy................................................................................................................................... 209
The EncrypTight User Guide provides detailed information on how to install, configure, and troubleshoot
EncrypTight components: ETEMS, Policy Manager (ETPM), and Key Management System (ETKMS). It
also contains information about configuring EncrypTight Enforcement Points (ETEPs) using ETEMS.
Intended Audience
This document is intended for network managers and security administrators who are familiar with setting
up and maintaining network equipment. Some knowledge of network security issues and encryption
technologies is assumed.
Assumptions
This document assumes that its readers have an understanding of the following:
● EncrypTight encryption appliance features, installation and operation
● Basic principles of network security issues
● Basic principles of encryption technologies and terminology
● Basic principles of TCP/IP networking, including IP addressing, switching and routing
● Personal computer (PC) operation, common PC terminology, use of terminal emulation software and
FTP operations
● Basic knowledge of the Linux operating system
Conventions used in this document
Bold Indicates one of the following:
• a menu item or button
• the name of a command or parameter
ItalicsIndicates a new term
Monospaced Indicates machine text, such as terminal output and filenames
Monospaced bold
EncrypTight User Guide13
Indicates a command to be issued by the user
Preface
Contacting Black Box Technical Support
Contact our FREE technical support, 24 hours a day, 7 days a week:
Phone724-746-5500
Fax724-746-0746
e-mailinfo@blackbox.com
Web sitewww.blackbox.com
14EncrypTight User Guide
Part IEncrypTight Installation and
Maintenance
16EncrypTight User Guide
1EncrypTight Overview
EncrypTight™ Policy and Key Manager is an innovative approach to network-wide encryption.
EncrypTight acts as a transparent overlay that integrates easily into any existing network architecture,
providing encryption rules and keys to EncrypTight encryption appliances.
EncrypTight consists of a suite of tools that perform various tasks of appliance and policy management:
● EncrypTight Element Management System (ETEMS) is the network management component of the
EncrypTight software. Use ETEMS to configure and manage your encryption appliances.
● EncrypTight Policy Manager (ETPM) is the policy generation and management tool. Use ETPM to
create polices for hub and spoke, mesh, point-to-point, and multicast networks that require common
keys to secure traffic between multiple nodes.
● EncrypTight Key Management System (ETKMS) is the key generation and distribution tool that is
used with ETPM-generated policies. ETKMS can be run on a local machine for small deployments or
on a dedicated server for larger scale networks.
● EncrypTight Enforcement Points (ETEPs) are the encryption appliances that enforce the security
policies. EncrypTight appliances are also referred to as PEPs.
The type of policies that you create, and the tools that you use to create them, are dependent on your
network topology. EncrypTight supports two types of policies for the following topologies:
● Distributed key policies are appropriate for securing a variety of networks, including mesh, hub and
spoke, point-to-point (Layer 3/4 only), and multicast networks.
● Negotiated policies are appropriate in Layer 2 point-to-point networks where keys are negotiated with
a peer rather than distributed from a central key server.
This section includes the following topics:
● Distributed Key Topologies
● Point-to-Point Negotiated Topology
● Security within EncrypTight
Distributed Key Topologies
EncrypTight centralizes the creation and distribution of encryption keys and policies. It separates the
functions of policy management, key generation and distribution, and policy enforcement. By doing so,
EncrypTight User Guide17
EncrypTight Overview
multiple Policy Enforcement Points (PEPs) can use common keys, while a centralized platform assumes
the function of renewing keys at pre-determined intervals.
In this system, you use ETEMS to configure the PEPs, Policy Manager (ETPM) to create and manage
policies, and Key Management System (ETKMS) to generate keys and distribute keys and policies to the
appropriate PEPs. The PEPs encrypt traffic according to the policies and keys that they receive.
Figure 1EncrypTight components
Using EncrypTight, you can create distributed key policies for the network topologies shown in Table 1.
Table 1 Network topologies
TopologyDescription
Layer 3 IP topologies
Hub and Spoke In a hub and spoke network, a hub network communicates with the
Multicast In multicast transmission, one or more networks send unidirectional
Point-to-point In a point-to-point network, one network sends and receives data to
Mesh In a mesh network, any network can send or receive data from any
Layer 2 Ethernet topologies
Mesh For Ethernet, you can create policies for mesh networks. Note that if
spoke networks and the spoke networks communicate only with the
hub network.
streams to a multicast network address. The multicast routers detect
the multicast transmission, determine which nodes have joined the
multicast network as destination networks, and duplicate the packet as
needed to reach all multicast destination networks.
and from one other network.
other network.
the network uses VLAN ID tags, you can also create policies for virtual
point-to-point connections.
18EncrypTight User Guide
Distributed Key Topologies
Regardless of topology, PEPs are typically located at the point in the network where traffic is being sent
to an untrusted network or coming from an untrusted network. As an example, Figure 2 shows a hub and
spoke network secured with EncrypTight.
Figure 2PEPs in a Hub and Spoke network
PEP A encrypts data traffic from Network A that goes to Networks B or C. PEP A also decrypts data that
originates from Networks B and C. PEP B encrypts data from Network B that goes to Network A and
decrypts data that comes from Network A. PEP C encrypts data from Network C that goes to Network A
and decrypts data that comes from Network A.
Related topics:
● “EncrypTight Element Management System” on page 20
● “Policy Manager” on page 20
● “Key Management System” on page 20
● “Policy Enforcement Point” on page 21
EncrypTight Elements
EncrypTight consists of a suite of tools that perform various tasks of appliance and policy management:
● EncrypTight Element Management System is the element management component of the EncrypTight
software
● Policy Manager is the policy generation and management tool
● Key Management System is the key generation and distribution tool
● Policy Enforcement Points are the encryption appliances that enforce the security policies
The number of ETEPs that you can manage and the speed at which they run is controlled by licenses.
You must enter a license for EncrypTight before you can install licenses on the ETEPs.
EncrypTight User Guide19
EncrypTight Overview
EncrypTight Element Management System
The EncrypTight Element Management System (ETEMS) is the device management component of the
EncrypTight software, allowing you to provision and manage multiple encryption appliances from a
central location. It provides capabilities for appliance configuration, software updates, and maintenance
and troubleshooting for your EncrypTight encryption appliances.
Policy Manager
The Policy Manager (ETPM) is the policy component of the EncrypTight software. You use ETPM to
create and manage policies, and monitor the status of the PEPs and ETKMSs.
Each deployment of EncrypTight uses a single ETPM. The ETPM sends metapolicies to one or more
ETKMSs. A metapolicy is a file that describes the policies created in ETPM and for each policy it
specifies:
● The PEPs each ETKMS controls
● The networks each PEP protects
● The action that is performed (encrypt, send in the clear, or drop)
● The kind of traffic the policy affects
Key Management System
Distribution functions are provided by the EncrypTight Key Management System (ETKMS). All
ETKMSs receive policies from a single ETPM. Based on the metapolicies received from the ETPM, the
ETKMS generates keys for each of the PEPs within its network. The ETKMS distributes the keys and
policies associated with its networks to the appropriate PEPs.
Depending on the size and configuration of your network, you can use a single ETKMS or multiple
ETKMSs distributed throughout the network. When multiple ETKMSs are used, each ETKMS controls
different sets of PEPs. All ETKMSs include the policy information and keys for the entire network. When
policies are deployed or keys are renewed, each PEP receives its information from its designated
ETKMS.
The EncrypTight system supports two types of ETKMSs: external ETKMSs and local ETKMSs.
● External ETKMSs are dedicated computers running the ETKMS software. By running on a dedicated
computer, external ETKMSs inherently provide more security and reliability, and can be used to help
protect significantly larger networks. Each ETKMS can support several hundred PEPs.
● Local ETKMSs run as a separate process on the same management workstation as the EncrypTight
software. Local ETKMSs are intended for use with small to medium networks with no more than 10
PEPs. A local ETKMS is included with the EncrypTight software.
Figure 3 shows a single ETKMS distributing the keys for PEPs A, B, C, and D.
20EncrypTight User Guide
Distributed Key Topologies
Figure 3Single ETKMS for multiple sites
Figure 4 illustrates an EncrypTight deployment using multiple ETKMSs. With large, complex networks
that have hundreds of PEPs, you might want to use multiple ETKMSs. Each ETKMS distributes keys for
the PEPs it controls. For example: ETKMS 1 distributes the policies and keys to PEPs A, B, and C.
ETKMS 2 distributes the policies and keys to PEPs D and E. ETKMS 3 distributes the policies and keys
to PEPs F and G.
Figure 4Multiple ETKMSs in a network
Policy Enforcement Point
EncrypTight enforcement points (ETEPs) are encryption appliances that provide policy enforcement
functions, and are referred to generically as PEPs (policy enforcement points). According to the policies
distributed by the ETKMSs, the PEPs can encrypt and decrypt traffic, send traffic in the clear, or drop
traffic. Each PEP can be used in multiple policies simultaneously.
EncrypTight User Guide21
EncrypTight Overview
To securely transfer data between two PEPs over an untrusted network, both PEPs must share a key. One
PEP uses the shared key to encrypt the data for transmission over the untrusted network, while the second
PEP uses the same shared key to decrypt the data. Figure 5 illustrates the shared key concepts between
two PEPs.
Figure 5Shared keys
In this example, traffic moves between two trusted networks: Network A and Network B. PEP A and
PEP B work in unison to insure data security as the traffic passes through an unsecured network. PEP A
uses Shared Key 2 to encrypt all outbound traffic intended for Network B. PEP B uses the same shared
key to decrypt all traffic inbound from Network A. Traffic flowing in the opposite direction is secured in
the same manner using Shared Key 1.
EncrypTight Policy Enforcement Points (PEPs) can be configured for Layer 2 or Layer 3/4 operation.
Models include:
● ET0010A
● ET0010A
● ET1000A
Point-to-Point Negotiated Topology
You can protect simple, point-to-point Ethernet links using ETEMS. Two PEPs can be configured with
ETEMS to protect a Layer 2 Ethernet link, without any need for ETPM or ETKMS. The policies and key
are negotiated directly by the two PEPs, without requiring a centralized key generation and distribution
tool.
This option provides a simple, quick, and straightforward way to secure a single point-to-point Layer 2
Ethernet link. All you need to secure your traffic is ETEMS and two ETEP encryption appliances.
The ETEP can be managed in-line or out-of-band through a dedicated Ethernet management interface, as
shown in Figure 6.
22EncrypTight User Guide
Figure 6Layer 2 Point-to-Point Deployment
Security within EncrypTight
Use the Policy Manager (ETPM) and Key Management System (ETKMS) to create a Layer 3 point-topoint distributed key policy as one of several policies in a larger, more complex EncrypTight deployment.
The ETEP’s variable speed feature is controlled by the installation of a license. Note that you cannot
install a license on the ETEP until you first enter a license for EncrypTight. For more information about
licensing, see “Managing Licenses” on page 56.
Related topics:
● “Distributed Key Topologies” on page 17
● “EncrypTight Element Management System” on page 20
● “Policy Manager” on page 20
● “Key Management System” on page 20
● “Policy Enforcement Point” on page 21
● “Creating Layer 2 Point-to-Point Policies” on page 335
Security within EncrypTight
Because EncrypTight generates keys that provide security throughout a network, it is critical that the
EncrypTight components also be secured.
Security in the EncrypTight system has two general areas:
● “Secure Communications Between Devices” on page 24
● “Secure Key Storage within the ETKMS” on page 24
EncrypTight User Guide23
EncrypTight Overview
Secure Communications Between Devices
Each node in the distributed key system, the EncrypTight management station, the ETKMSs, and the
PEPs, communicate policy and status information with other nodes. Given the distributed nature of
networks, much of this communication occurs across public networks.
EncrypTight uses Transport Layer Security (TLS) to encrypt management traffic between EncrypTight
components. This protocol allows secure communication between the devices in the system while
providing information about the secure stream to EncrypTight. You can enhance that security by
authenticating the management communications between EncrypTight components using certificates. To
learn more about certificates and strict authentication, see “Using Enhanced Security Features” on
page 261.
Secure Key Storage within the ETKMS
Key generation and key storage on the ETKMS are critical to maintaining security in EncrypTight. The
ETKMS uses the following mechanisms to protect the keys:
● Generates keys using known secure algorithms
● Encrypts keys that are distributed and stored locally
● Limits access to keys to authorized administrators
● Prevents external probing to access or modify keys
● Optionally generates and stores keys in a hardware security module
24EncrypTight User Guide
2EncrypTight Deployment Planning
When deploying EncrypTight, you must plan the following:
● EncrypTight Component Connections
● Network Clock Synchronization
● IPv6 Address Support
● Certificate Support
● Network Addressing for IP Networks
EncrypTight Component Connections
EncrypTight can be managed in-line or out-of-band. When managing in-line, management traffic flows
through the data path. You must enable the Passing TLS traffic in the clear feature on all PEPs for
proper communication among EncrypTight components (ETEMS, ETPM, ETKMS, PEPs). When passing
TLS in the clear is enabled on Layer 2 PEPs, TLS and ARP packets are sent unencrypted.
If your network uses other routing protocols that need to pass in the clear, consider the following:
● At Layer 3, create policies to pass the routing protocols in the clear. The PEPs must also be
configured to pass non-IP traffic in the clear (this is the default setting on the Advanced tab in
ETEMS).
● At Layer 2, consider a separate out-of-band management network, or put the management traffic on a
separate VLAN and create a Layer 2 policy to pass packets with this VLAN tag in the clear.
Customer support can advise you on a solution that works best in your network.
● Use local site policies
Local site policies allow you to create locally configured policies using CLI commands, without
requiring an EncrypTight ETKMS for key distribution. Using the local-site CLI commands you can
create manual key encryption policies, bypass policies, and discard policies at either Layer 2 or Layer
3. Mesh policies can be created by adding policies that share the identical keys and SPIs to multiple
ETEPs.
The primary use for local site policies is to facilitate in-line management in Layer 2 encrypted
networks. These policies supplement existing encryption policies, adding the flexibility to encrypt or
pass in the clear specific Layer 3 routing protocols, or Layer 2 Ethertypes and VLAN IDs.
For information on creating and using local site policies, see the CLI User Guide.
This chapter discusses connections between each of the EncrypTight components, providing in-line and
out-of-band examples.
EncrypTight User Guide25
EncrypTight Deployment Planning
● “Management Station Connections” on page 26
The EncrypTight software includes ETEMS for appliance configuration, ETPM for policy
management, and a local ETKMS. The local ETKMS deploys keys and policies to all of the PEPs that
it manages and checks the PEPs’ status. The management station also uses other services such as
NTP, syslog, and SNMP.
● “ETPM to ETKMS Connections” on page 26
The ETPM passes metapolicies to the ETKMSs and checks the status of the PEPs through the
ETKMSs.
● “External ETKMS to ETKMS Connections” on page 29
When multiple ETKMSs are used in a system, the ETKMSs must be able to share keys. If you set up
a ETKMS to serve as a backup for another ETKMS, the backup ETKMS periodically checks the
status of the primary ETKMS in case of ETKMS failure.
● “ETKMS to PEP Connections” on page 31
Each ETKMS deploys keys and policies to all of the PEPs that it manages and checks the PEPs
status.
Management Station Connections
Keep the following items in mind when setting up your management connections:
● PEPs can be managed in-line or out-of-band. When managing the PEPs in-line, management traffic
flows through the data path. In distributed key deployments, enable the Pass TLS traffic in the clear
option on the PEPs to ensure proper communication between the PEP and other EncrypTight
components. This is configured on the Features tab of the ETEMS Appliance editor.
● The PEP management ports and management services such as NTP, syslog, and SNMP must be
directly addressable on the same network.
● EncrypTight to PEP connections when using a local ETKMS:
The EncrypTight software includes ETEMS, ETPM and local ETKMS. When you use a local
ETKMS, the ETKMS software runs as a separate process on the same workstation as the ETPM
software. In this scenario, ETPM communicates directly with the ETKMS without using a network
connection.
The communications between the local ETKMS and the PEPs require a connection between an
Ethernet port on the management workstation and the management port on each PEP. For these
connections, follow the same general guidelines as external ETKMSs, outlined in “ETKMS to PEP
Connections” on page 31. The only difference is that the connections originate from the management
workstation and not an external ETKMS.
ETPM to ETKMS Connections
The ETPM sends metapolicies to the ETKMSs and checks the status of the PEPs through the ETKMSs.
The communications between EncrypTight components depend on a connection between the Ethernet
ports on each device. External ETKMSs can be located on the same subnetwork with the ETPM, or the
ETPM and ETKMSs can be located on different subnetworks. If you use a local ETKMS, ETPM
communicates directly with the ETKMS without using a network connection.
26EncrypTight User Guide
This section describes the planning for the following connections:
NOTE
● “ETPM and ETKMS on the Same Subnetwork” on page 27
● “ETPM and ETKMS on Different Subnetworks” on page 27
ETPM and ETKMS on the Same Subnetwork
When the ETPM is located on the same subnetwork as the external ETKMS, the ETPM communicates
with the ETKMS over the internal protected network using Ethernet connections as shown in Figure 7.
Figure 7ETPM and ETKMS located in the same subnetwork
EncrypTight Component Connections
ETPM and ETKMS on Different Subnetworks
The ETPM and ETKMS interconnections on different subnetworks depends on the type of policy: Layer
3 IP policy or Layer 2 Ethernet policy.
ETPM and ETKMSin Layer 3 IP Policies
With larger IP networks, the ETPM and the external ETKMSs could be located on different subnetworks,
as shown in Figure 8. When managing the ETPM and ETKMS in-line, the communications path between
the devices must pass through one or more PEPs and potentially one or more firewalls. For in-line
management, in which management traffic can flow through the data path, be sure that the Enable passing TLS traffic in the clear feature is selected on all PEPs. Enable this feature from the ETEMS
Appliance editor. By default, the Layer 3 PEPs are configured to pass all TLS traffic (port 443) in the
clear.
The Enable passing TLS traffic in the clear feature passes all TLS traffic in the clear for all destination
addresses. For added security, disable passing TLS traffic in the clear and create a policy for all TLS
traffic (port 443) between EncrypTight components. For more information on creating policies, see
“Creating Distributed Key Policies” on page 181.
EncrypTight User Guide27
EncrypTight Deployment Planning
Figure 8In-line ETKMS management in an IP network
ETPM and ETKMS in Layer 2 Ethernet Policies
With Ethernet networks, you use Layer 2 PEPs. As with IP networks, when managing the ETPM and
external ETKMS in-line the communications path between the devices must pass through one or more
PEPs and potentially one or more firewalls. For in-line management with Layer 2 PEPs be sure that the
Enable passing TLS traffic in the clear feature is selected in the ETEMS Appliance editor.
If you need to pass additional traffic in the clear, such as routing protocols, you can route the
management communications using out-of-band connections or put your management traffic on a separate
VLAN.
If you choose to put the management traffic on a separate VLAN, you will need to create a Layer 2
policy to pass packets with this VLAN tag in the clear. To prevent an interruption in management traffic,
set the policy’s key renewal/lifetime to zero, so that the policy does not expire.
With out-of-band management, the management traffic between the ETPM and ETKMS is routed over a
separate network path through the ISP. When the communications path passes through any firewalls, be
sure to configure the firewall to pass TLS traffic. Figure 9 shows an out-of-band management scenario
with the ETPM connecting to an external ETKMS with Layer 2 PEPs encrypting Ethernet data.
Figure 9Out-of-band ETKMS management in an Ethernet network
28EncrypTight User Guide
External ETKMS to ETKMS Connections
ETKMSs must be able to communicate with each other in two situations:
● Backup ETKMSs are used for redundancy
● Multiple ETKMSs share policy information and keys to distribute to the PEPs that they control
This section addresses the connections between two or more external ETKMSs. If you also use a local
ETKMS, the basic principles discussed here still apply.
If the ETKMSs are on the same subnetwork, the ETKMS to ETKMS interconnection is straightforward.
ETKMSs communicate with each other using the Ethernet ports on each ETKMS. For large, dispersed
networks, multiple ETKMSs must be able to share keys with each other. The connections between
ETKMSs depend on the network type: IP network or Ethernet network.
This section includes the following topics:
● “Connections for Backup ETKMSs” on page 29
● “Connecting Multiple ETKMSs in an IP Network” on page 30
● “ETKMS to ETKMS Connections in Ethernet Networks” on page 30
EncrypTight Component Connections
Connections for Backup ETKMSs
In some EncrypTight configurations a pair of ETKMSs, a primary ETKMS and a secondary ETKMS, are
used to provide network redundancy. The ETPM distributes the policies to both the primary ETKMS and
backup ETKMS. Only the primary ETKMS distributes the keys and policies to the PEPs. If the backup
ETKMS detects a communication failure with the primary ETKMS due to a ETKMS failure or network
failure, the backup ETKMS assumes the generation and distribution of the keys and policies to the PEPs.
Once communication with the primary ETKMS is reestablished, the primary resumes the distribution of
the keys and policies to the PEPs.
Backup ETKMSs should be external ETKMSs. Using a local ETKMS as a backup ETKMS is not
recommended. If you use backup ETKMSs, the backup ETKMS must be able to check the status of the
primary ETKMS so that it can take over operations in the event of a communication failure. It is
recommended that you locate the backup ETKMS and the primary ETKMS together. The primary and
backup ETKMSs communicate using the Ethernet ports on each ETKMS.
Also keep in mind the following:
● Both the primary ETKMS and the backup ETKMS must be able to communicate with the same PEPs.
● Each ETKMS can only use one backup ETKMS. Similarly, each backup ETKMS can only serve as a
backup to one ETKMS.
● Backup ETKMSs must use the same type of IP address as the primary ETKMS. For example, if the
primary uses an IPv6 address, the backup ETKMS must use an IPv6 address.
● You do not explicitly add backup ETKMSs to the Appliance Manager in ETEMS and they are not
listed in that window. Instead, you specify a backup ETKMS when you add a primary ETKMS in
ETEMS, and only the primary ETKMS is listed in the Appliance Manager.
EncrypTight User Guide29
EncrypTight Deployment Planning
Connecting Multiple ETKMSs in an IP Network
Figure 10 shows two external ETKMSs located on different IP networks. Both ETKMSs are used as
primary ETKMSs in a large, dispersed network.
When the ETKMSs are managed in-line, the communications path between the devices must pass through
one or more PEPs and potentially one or more firewalls. By default, the Layer 3 PEPs pass all TLS
traffic (port 443) in the clear. Be sure that the Enable passing TLS traffic in the clear feature is enabled
for all PEPs which must pass TLS traffic. Enable this feature from the ETEMS Appliance editor.
Figure 10In-line management of ETKMSs located on different IP networks
ETKMS to ETKMS Connections in Ethernet Networks
For in-line management when the ETKMSs are on different Ethernet networks, make sure that the
Enable passing TLS traffic in the clear feature is enabled on the Layer 2 PEPs.
If you need to pass additional traffic in the clear, such as routing protocols, you can route the
management communications using out-of-band connections or put your management traffic on a separate
VLAN.
If you choose to put the management traffic on a separate VLAN, you will need to create a Layer 2
policy to pass the VLAN tag in the clear. To prevent an interruption in management traffic, set the
policy’s key renewal/lifetime to zero, which means “do not expire or update.”
With out-of-band management, the management traffic between the ETKMSs is routed over a separate
network path through the ISP. When the communications path passes through any firewalls, be sure to
configure the firewall to pass TLS traffic. Figure 11 shows an out-of-band management scenario with the
external ETKMS connecting to another external ETKMS, with Layer 2 PEPs encrypting Ethernet data.
30EncrypTight User Guide
Figure 11Out-of-band management of ETKMSs located on different Ethernet networks
ETKMS to PEP Connections
The communications between the ETKMSs and the PEPs require a connection between the Ethernet ports
on each ETKMS and the management port on each PEP. The ETKMS to PEP connections depend on the
network type: IP network or Ethernet network.
EncrypTight Component Connections
This section addresses connections between external ETKMSs and the PEPs. If you also use a local
ETKMS, the basic principles discussed here still apply. However, a local ETKMS runs on the same
workstation as the ETPM. Therefore the communications between the local ETKMS and the PEPs require
a connection between an Ethernet port on the management workstation and the management port on each
PEP.
This section includes the following topics:
● “ETKMS to PEP Connections in IP Networks” on page 31
● “ETKMS to PEP Connections in Ethernet Networks” on page 32
ETKMS to PEP Connections in IP Networks
Figure 12 shows one external ETKMS connecting to two PEPs. The connections between the ETKMS
and the first PEP co-located on the same network is a straightforward connection. The ETKMS’s Ethernet
port connects through the internal protected network to the PEP’s management port.
When managing in-line, the connection between the ETKMS and the second PEP located on a different
network must pass through the data ports on both PEPs to get to the management port on the second
PEP.
To successfully pass management traffic, be sure that the Enable passing TLS traffic in the clear
feature is enabled on all of the PEPs. By default, the Layer 3 PEPs pass all TLS traffic (port 443) in the
clear. This option is configured on the Features tab of the ETEMS Appliance editor.
EncrypTight User Guide31
Loading...
+ 322 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.