HP UX IPSec Software Configuring a Windows End-to-End Tunnel Policy, Configuring a Tunnel Rule

Page 33

Configuring a Windows End-to-End Tunnel Policy

The only IPsec tunnel topology supported between an HP-UX system and a Windows system is an end-to-end tunnel.5The procedure for configuring an end-to-end tunnel policy on Windows system is the same as procedure for configuring a host policy, except that you must configure two, non-mirrored rules: one rule for outbound packets and one rule for inbound packets, as described in the sections that follow.

NOTE: Do not configure any other rules in the policy with the HP-UX system address as the destination address. This prevents the Microsoft system from applying the tunnel transform over a host-to-host (transport) transform. In end-to-end tunnel topologies, HP-UX IPSec does not support transport transforms over a tunnel transform.

Outbound Tunnel Rule Requirements

The outbound tunnel rule must have the following parameters:

•Filter List: One filter, with the following parameters:

—Address:

◦Source address: the HP-UX system's address.

◦Destination address: this must be a specific IP address and must be the Windows system's address.

◦Mirrored: no (the Mirrored box is cleared).

—Protocol Type: none (wildcard). The Windows documentation states that the filters in tunnel rules must not specify protocols or ports to ensure that IP Security can correctly process IP fragments.

•Tunnel Setting

—Tunnel endpoint: the HP-UX system's address. This is the address of the tunnel endpoint closest to the destination. Since this is an end-to-end tunnel, it is the same as the destination address in the address filter.

Inbound Tunnel Rule Requirements

The inbound tunnel rule must have the following parameters:

•Filter List: One filter, with the following parameters:

—Address:

◦Source address: the Windows system's address.

◦Destination address: this must be a specific IP address and must be the HP-UX system's address.

◦Mirrored: no (the Mirrored box is cleared).

—Protocol Type: none (wildcard).

•Tunnel Setting

—Tunnel endpoint: the Windows system's address. This is the address of the tunnel endpoint closest to the destination. Since this is an end-to-end tunnel, it is the same as the destination address in the address filter

Configuring a Tunnel Rule

Use the following procedure to configure an outbound or inbound tunnel rule.

5.You can also configure an IPsec topology where packets exchanged between an HP-UX system and a Windows system are tunneled through an IPsec gateway device, but neither HP-UX nor Windows systems can be configured as IPsec gateways. The only topology in which an HP-UX system can act as an IPsec gateway is when the HP-UX system is a Home Agent for Mobile IPv6 clients. The HP-UX IPSec Administrator's Guide describes how to configure a host-to-gateway IPsec topology using HP-UX and a Cisco router.

Configuring a Windows End-to-End Tunnel Policy 33

Page 32 Page 34
Image 33
Page 32 Page 34
Contents HP Part Number J4256-90025 Published June Edition Page Table of Contents Glossary List of Figures Page List of Tables Page Typographic Conventions About This DocumentPage Testing Environment Known Problem with Windows 2000 SP1 and SP2Introduction Protocol Implementation Differences Rules Windows IP Security Configuration OverviewTunnel Settings Configuring a Windows Host-to-Host PolicyCreating a Policy IP Security Policy Wizard Adding a RuleRules Tab Creating an IP Filter List Creating the IP Filter List and Filters for the RuleClick OK to return to the Filter Properties dialog box Protocol Tab for Filter Properties Selecting the Filter List for a Rule Configuring Filter Actions for the RuleSecurity Methods for Filter Action Encryption and Integrity Click Apply Selecting the Filter Action Modifying IKE Parameters for the Policy Configuring the Connection Type for the RuleGeneral Policy Properties Dialog Box Master key perfect forward secrecy PFS IKE Security Algorithms Dialog Box Starting the IP Security ServiceAssigning the IP Security Policy Ipsec Services Properties Dialog BoxVerifying the Configuration Windows ConfigurationExample HP-UX Configuration Configuring a Tunnel Rule Configuring a Windows End-to-End Tunnel PolicyOutbound Tunnel Rule Requirements Inbound Tunnel Rule RequirementsOutbound Rule Outbound Rule Filter Inbound Rule Filter HP-UX Configuration Troubleshooting Tips Using IKE Logging on HP-UX SystemsUsing IKE Logging on Windows Systems Disable IKE logging. On Windows XP systems, set Additional Windows Troubleshooting ToolsIPsec Parameters on Windows and HP-UX Comparing HP-UX and Windows IPsec Configuration ParametersValues page 42 for Mirrored FiltersIKE Parameter Selection Filter SelectionIKE SA Key Master Key Lifetime Values HP-UX IKE SA Lifetime ValuesPerfect Forward Secrecy PFS Maximum Quick ModesIPsec SA Key Session Key Lifetime Values Windows IKE SA Lifetime ValuesWindows IPsec SA Lifetime Values Related Publications Page Glossary Transform
Related manuals
Manual 318 pages 32.64 Kb Manual 8 pages 43.6 Kb

UX IPSec Software specifications

HP-UX IPSec Software is an integral component of the HP-UX operating system, providing robust and secure communication capabilities for enterprise environments. As organizations increasingly rely on secure networking solutions, HP-UX IPSec stands out with its comprehensive set of features and technologies designed to safeguard sensitive data.

One of the core characteristics of HP-UX IPSec Software is its implementation of the Internet Protocol Security (IPSec) framework. This technology secures Internet Protocol (IP) communications through authentication and encryption, ensuring the integrity and confidentiality of data transmissions. By leveraging IPSec, HP-UX provides a secure method for connecting remote users and secure sites over untrusted networks, such as the internet.

A notable feature of the HP-UX IPSec Software is its support for both transport and tunnel modes. The transport mode encrypts only the payload of the IP packet, whereas the tunnel mode encapsulates the entire IP packet within a new packet, allowing for secure communications between entire networks. This flexibility enables organizations to tailor their security strategies based on specific use cases and requirements.

HP-UX IPSec also emphasizes interoperability and compliance with industry standards. The software supports various encryption algorithms and authentication methods, including those defined by the Internet Engineering Task Force (IETF). This commitment to open standards ensures that HP-UX can seamlessly integrate with a diverse range of networking infrastructures and security solutions.

In addition to its security features, HP-UX IPSec Software offers administration tools that simplify the configuration and management of IPSec policies. The software includes a user-friendly command-line interface, allowing system administrators to specify security associations and policies efficiently. Moreover, comprehensive logging and monitoring capabilities help organizations keep track of their security posture and detect potential vulnerabilities.

Another essential characteristic of HP-UX IPSec Software is its scalability. Designed to accommodate the needs of both small and large enterprises, it can handle increased loads and adapt to changing security demands without compromising performance.

In conclusion, HP-UX IPSec Software stands as a vital solution for organizations seeking to protect their data transmissions over IP networks. With its core technologies, such as transport and tunnel modes, adherence to industry standards, user-friendly administration tools, and scalability, it provides a formidable layer of security in an increasingly interconnected world. This makes it a preferred choice for enterprises aiming to enhance their network security frameworks.
Top Page Image Contents