a. Select the IPsec template, and then click the Modify button. The IPsec Template wizard starts.
b. On the IPsec Protocols page, make the appropriate changes, and then click the Next button.
c. On the Identity Authentication page, make the appropriate changes, and then click the Next button.
The IPsec Template wizard closes.
10. On the Specify IPsec/Firewall Template page, click the Next button.
11. On the Rule Summary page, click the Finish button.
Use the following steps to delete a rule:
1. Select the rule, and then click the Delete Rule button.
2. On the Conrm window, click the Yes button.
Federal Information Processing Standard (FIPS) supports only the AES-128 and AES-256 ciphers. To congure
the Kerberos setting when FIPS mode is enabled on the device, you must specify the AES-128 and AES-256
protocols. If you specify the DES-CBC-MD5 cipher for the Kerberos setting, the conguration fails.
HP Jetdirect IPsec supports the Kerberos authentication method. The Kerberos authentication method supports
the AES128-SHA1 and AES256-SHA1 encryption protocols. These encryption protocols incorporate an iteration
count that increases the complexity of the encryption keys. The default iteration count in HP Jetdirect is 4,096,
which complies with current standards. The iteration count in HP Jetdirect and the iteration count on the
Kerberos domain controller must match. To change the iteration count on the Kerberos domain controller, create
the following Registry entry and provide the appropriate value. This Registry entry aects all of the Kerberos
clients of the domain controller.
HKLM\SYSTEM\CurrentControlSet\Services\Kdc\IterationCount (DWORD)
The HP Web Jetadmin administrator can create an IPsec rule with Kerberos pre-authentication by using one of
the following methods:
●
Use HP Web Jetadmin to congure the settings for the IPsec rule, which includes the Kerberos server admin
credentials and organization unit (OU) path. HP Web Jetadmin uses these settings to create an account on
the Key Distribution Center (KDC) server.
●
Log in to the KDC server and manually create an account. Then access the HP Embedded Web Server (EWS)
on the device, and congure the settings for the IPsec rule.
The HP Web Jetadmin administrator must not congure the settings for an IPsec rule by using HP Web Jetadmin
and then later update those settings by using the device EWS, or vice versa. The following are examples of the
conicts that can occur:
●
The HP Web Jetadmin administrator uses HP Web Jetadmin to create an IPsec rule that has an encryption
type of DES. Then the HP Web Jetadmin administrator uses the device EWS to change the encryption type
to AES-128. If the HP Web Jetadmin administrator then uses HP Web Jetadmin to perform a refresh and
reapply the rule to the device, the IPsec policy fails because the encryption type for the Kerberos server
account is still DES. To ensure that the encryption type is updated on the Kerberos server, the
HP Web Jetadmin administrator must use HP Web Jetadmin to change the encryption type.
●
The HP Web Jetadmin administrator uses HP Web Jetadmin to create an IPsec rule. Then the
HP Web Jetadmin administrator uses the device EWS to change the settings for the rule. When the
HP Web Jetadmin administrator views the rule in HP Web Jetadmin, the changes that were made by using
the EWS are not displayed. In this case, HP Web Jetadmin does not display an error message and the IPsec
policy might not be applied correctly.
ENWW Device Conguration Options for Security 427
Comentarios a estos manuales