Integration with IPS or NGFW as inline devices using SSL forward proxy
Security devices such as Intrusion Prevention System (IPS) and Next Generation Firewall (NGFW) protect servers from network attacks. These devices can inspect live traffic and are typically deployed in layer 2 inline mode. The SSL forward proxy appliance provides security of users and the enterprise network when accessing resources on the internet.
An SSL forward proxy appliance can be integrated with one or more inline devices to prevent threats and provide advanced security protection. The inline devices can be any security device, such as IPS and NGFW.
Some use cases where you can benefit by using the SSL forward proxy appliance and inline device integration are:
Inspecting encrypted traffic:Most IPS and NGFW appliances bypass encrypted traffic, which can leave servers vulnerable to attacks. An SSL forward proxy appliance can decrypt traffic and send it to the inline devices for inspection. This integration enhances the customer’s network security.
Offloading inline devices from TLS/SSL processing:TLS/SSL processing is expensive, which can result in high CPU utilization in IPS or NGFW appliances if they also decrypt the traffic. An SSL forward proxy appliance helps in offloading TLS/SSL processing from inline devices. As a result, inline devices can inspect a higher volume of traffic.
Loading balancing inline devices:If you have configured multiple inline devices to manage heavy traffic, an SSL forward proxy appliance can load balance and distribute traffic evenly to these devices.
Smart selection of traffic:Instead of sending all the traffic to the inline device for inspection, the appliance does a smart selection of traffic. For example, it skips sending text files for inspection to the inline devices.
SSL forward proxy integration with inline devices
The following diagram shows how an SSL forward proxy is integrated with inline security devices.
When you integrate inline devices with the SSL forward proxy appliance, the components interact as follows:
A client sends a request to an SSL forward proxy appliance.
The appliance sends the data to the inline device for content inspection based on the policy evaluation. For HTTPS traffic, the appliance decrypts the data and sends it in plain text to the inline device for content inspection.
Note
If there are two or more inline devices, the appliance load balances the devices and sends the traffic.
- 添加a content switching or an HTTP/HTTPS load balancing virtual server.
- The inline device inspects the data for threats and decides whether to drop, reset, or send the data back to the appliance.
- If there are security threats, the device modifies the data and sends it to the appliance.
- For HTTPS traffic, the appliance re-encrypts the data and forwards the request to the back-end server.
- The back-end server sends the response to the appliance.
- The appliance again decrypts the data and sends it to the inline device for inspection.
- The inline device inspects the data. If there are security threats, the device modifies the data and sends it to the appliance.
- The appliance re-encrypts the data and sends the response to the client.
Configuring inline device integration
You can configure an SSL forward proxy appliance with an inline device in three different ways as follows:
Scenario 1: Using a single inline device
To integrate a security device (IPS or NGFW) in inline mode, you must enable content inspection and MAC-based forwarding (MBF) in global mode on the SSL forward proxy appliance. Then, add a content inspection profile, a TCP service, a content inspection action for inline devices to reset, block, or drop the traffic based on inspection. Also add a content inspection policy that the appliance uses to decide the subset of traffic to send to the inline devices. Finally, configure the proxy virtual server with layer 2 connection enabled on the server and bind the content inspection policy to this proxy virtual server.
Perform the following steps:
- Enable MAC-based forwarding (MPF) mode.
- Enable the content inspection feature.
- 添加a content inspection profile for the service. The content inspection profile contains the inline device settings that integrate the SSL forward proxy appliance with an inline device.
(Optional) Add a TCP monitor.
Note:
Transparent devices do not have an IP address. Therefore, to perform health checks, you must explicitly bind a monitor.
- 添加一个服务。服务代表内联井斜ce.
- (Optional) Bind the service to the TCP monitor.
- 添加a content inspection action for the service.
- 添加a content inspection policy and specify the action.
- 添加an HTTP or HTTPS proxy (content switching) virtual server.
- Bind the content inspection policy to the virtual server.
Configure using the CLI
Type the following commands at the command prompt. Examples are given after most commands.
- Enable MBF.
enable ns mode mbf
- Enable the feature.
enable ns feature contentInspection
- 添加a content inspection profile.
add contentInspection profile
Example:
add contentInspection profile ipsprof -type InlineInspection -ingressinterface “1/2” -egressInterface “1/3”
- 添加一个服务。Specify a dummy IP address that is not owned by any of the devices, including the inline devices. Set
use source IP address(USIP) to YES. Setuseproxyportto NO. By default, health monitoring is ON, bind the service to a health monitor, and also set the TRANSPARENT option in the monitor ON.
add service
Example:
add service ips_service 198.51.100.2 TCP * -healthMonitor YES -usip YES -useproxyport NO -contentInspectionProfileName ipsprof
添加a health monitor. By default the health monitor is turned on and you also have the option to disable it, if necessary. At the command prompt, type:
add lb monitorTCP -destIP -destPort 80 -transparent
Example:
add lb monitor ips_tcp TCP -destIP 192.168.10.2 -destPort 80 -transparent YES
- Bind the service to the health monitor
健康状况监控器配置后,必须垃圾箱d the service to the health monitor. At the command prompt, type:
bind service
Example:
bind service ips_svc -monitorName ips_tcp
- 添加a content inspection action.
add contentInspection action
Example:
add contentInspection action ips_action -type INLINEINSPECTION -serverName ips_service
- 添加a content inspection policy.
add contentInspection policy
Example:
add contentInspection policy ips_pol -rule "HTTP.REQ.METHOD.NE(\"CONNECT\")" -action ips_action
- 添加a proxy virtual server.
add cs vserver
Note:
Load balancing virtual servers of type HTTP/SSL are also supported.
Example:
add cs vserver transparentcs PROXY * * -cltTimeout 180 -Listenpolicy exp1 -authn401 on -authnVsName swg-auth-vs-trans-http -l2Conn ON
- Bind the policy to the virtual server.
bind cs vserver
Example:
bind cs vserver explicitcs -policyName ips_pol -priority 1 -gotoPriorityExpression END -type REQUEST
Configure using the GUI
Navigate toSystem > Settings. InModes and Features, clickConfigure Modes.
Navigate toSystem > Settings. InModes and Features, clickConfigure Advanced Features.
Navigate toSecure Web Gateway > Content Inspection > Content Inspection Profiles. Click添加.
Navigate to负载平衡服务> >添加and add a service. InAdvanced Settings, clickProfiles. In theCI Profile Namelist, select the content inspection profile created earlier. InService Settings, setUse Source IP Addressto YES andUse Proxy Portto No. InBasic Settings, setHealth Monitoringto NO. Turn on health monitoring only if you bind this service to a TCP monitor. If you bind a monitor to a service, then set the TRANSPARENT option in the monitor to ON.
Navigate toSecure Web Gateway > Proxy Virtual Servers> Add. Specify a name, IP address, and port. InAdvanced Settings, selectPolicies. Click the “+” sign.
InChoose PolicyselectContent Inspection. ClickContinue.
Click添加. Specify a name. InAction, click添加.
Specify a name. InType, selectINLINEINSPECTION. InServer Name, select the TCP service created earlier.
ClickCreate. Specify the rule and clickCreate.
ClickBind.
ClickDone.
Scenario 2: Load balance multiple inline devices with dedicated interfaces
If you are using two or more inline devices, you can load balance the devices using different content inspection services with dedicated interfaces. In this case, the SSL forward proxy appliance load balances the subset of traffic sent to each device through a dedicated interface. The subset is decided based on the policies configured. For example, TXT or image files might not be sent for inspection to the inline devices.
The basic configuration remains the same as in scenario 1. However, you must create a content inspection profile for each inline device and specify the ingress and egress interface in each profile. Add a service for each inline device. Add a load balancing virtual server and specify it in the content inspection action. Perform the following extra steps:
- 添加content inspection profiles for each service.
- 添加a service for each device.
- 添加a load balancing virtual server.
- Specify the load balancing virtual server in the content inspection action.
Configure using the CLI
Type the following commands at the command prompt. Examples are given after each command.
- Enable MBF.
enable ns mode mbf
- Enable the feature.
enable ns feature contentInspection
- 添加profile 1 for service 1.
add contentInspection profile
Example:
add contentInspection profile ipsprof1 -type InlineInspection -ingressInterface "1/2" -egressInterface "1/3"
- 添加profile 2 for service 2.
add contentInspection profile
Example:
add contentInspection profile ipsprof2 -type InlineInspection -ingressInterface "1/4" -egressInterface "1/5"
- 添加service 1. Specify a dummy IP address that is not owned by any of the devices, including the inline devices. Set
use source IP address(USIP) to YES. Setuseproxyportto NO. Turn on health monitoring with TCP monitor with TRANSPARENT option set ON.
add service
Example:
add service ips_service1 192.168.10.2 TCP * -healthMonitor NO -usip YES -useproxyport NO -contentInspectionProfileName ipsprof1
- 添加service 2. Specify a dummy IP address that is not owned by any of the devices, including the inline devices. Set
use source IP address(USIP) to YES. Setuseproxyportto NO. Turn on health monitoring with TRANSPARENT option set ON.
add service
Example:
add service ips_service2 192.168.10.3 TCP * -healthMonitor NO -usip YES -useproxyport NO -contentInspectionProfileName ipsprof2
- 添加a load balancing virtual server.
add lb vserver
Example:
add lb vserver lb_inline_vserver TCP 192.0.2.100 *
- Bind the services to the load balancing virtual server.
bind lb vserver bind lb vserver
Example:
bind lb vserver lb_inline_vserver ips_service1bind lb vserver lb_inline_vserver ips_service2
- Specify the load balancing virtual server in the content inspection action.
add contentInspection action
Example:
add contentInspection action ips_action -type INLINEINSPECTION -serverName lb_inline_vserver
- 添加a content inspection policy. Specify the content inspection action in the policy.
add contentInspection policy
Example:
add contentInspection policy ips_pol -rule "HTTP.REQ.METHOD.NE(\"CONNECT\")" -action ips_action
- 添加a proxy virtual server.
add cs vserver
Example:
add cs vserver transparentcs PROXY * * -l2Conn ON
- Bind the content inspection policy to the virtual server.
bind cs vserver
Example:
bind cs vserver explicitcs -policyName ips_pol -priority 1 -gotoPriorityExpression END -type REQUEST
Configuration using the GUI
Navigate toSystem > Settings. InModes and Features, clickConfigure Modes.
Navigate toSystem > Settings. InModes and Features, clickConfigure Advanced Features.
Navigate toSecure Web Gateway > Content Inspection > Content Inspection Profiles. Click添加.
Specify the ingress and egress interfaces.
Create two profiles. Specify a different ingress and egress interface in the second profile.
Navigate to负载平衡服务> >添加and add a service. InAdvanced Settings, clickProfiles. In theCI Profile Namelist, select the content inspection profile created earlier. InService Settings, setUse Source IP Addressto YES andUse Proxy Portto No. InBasic Settings, setHealth Monitoringto NO. Turn on health monitoring only if you bind this service to a TCP monitor. If you bind a monitor to a service, then set the TRANSPARENT option in the monitor to ON.
Create two services. Specify dummy IP addresses that are not owned by any of the devices, including the inline devices.
Navigate toLoad Balancing > Virtual Servers > Add. Create a TCP load balancing virtual server.
ClickOK.
Click inside the负载均衡虚拟服务器服务绑定section. InService Binding, click the arrow in选择服务. Select the two services created earlier, and clickSelect. ClickBind.
Navigate toSecure Web Gateway > Proxy Virtual Servers> Add. Specify a name, IP address, and port. InAdvanced Settings, selectPolicies. Click the “+” sign.
InChoose PolicyselectContent Inspection. ClickContinue.
Click添加. Specify a name. InAction, click添加.
Specify a name. InType, selectINLINEINSPECTION. InServer Name, select the load balancing virtual server created earlier.
ClickCreate. Specify the rule and clickCreate.
ClickBind.
ClickDone.
Scenario 3: Load balance multiple inline devices with shared interfaces
If you are using two or more inline devices, you can load balance the devices using different content inspection services with shared interfaces. In this case, the SSL forward proxy appliance load balances the subset of traffic sent to each device through a shared interface. The subset is decided based on the policies configured. For example, TXT or image files might not be sent for inspection to the inline devices.
The basic configuration remains the same as in scenario 2. For this scenario, bind the interfaces to different VLANs to segregate the traffic for each inline device. Specify the VLANs in the content inspection profiles. Perform the following extra steps:
Bind the shared interfaces to different VLANs.
Specify the ingress and egress VLANs in the content inspection profiles.
Configuration using the CLI
Type the following commands at the command prompt. Examples are given after each command.
- Enable MBF.
enable ns mode mbf
- Enable the feature.
enable ns feature contentInspection
Bind the shared interfaces to different VLANs.
bind vlan-ifnum -tagged
Example:
bind vlan 100 –ifnum 1/2 tagged bind vlan 200 –ifnum 1/3 tagged bind vlan 300 –ifnum 1/2 tagged bind vlan 400 –ifnum 1/3 tagged - 添加profile 1 for service 1. Specify the ingress and egress VLANs in the profile.
add contentInspection profile
Example:
add contentInspection profile ipsprof1 -type InlineInspection -egressInterface “1/3” -ingressinterface “1/2” –egressVlan 100 -ingressVlan 300
- 添加profile 2 for service 2. Specify the ingress and egress VLANs in the profile.
add contentInspection profile
Example:
add contentInspection profile ipsprof2 -type InlineInspection -egressInterface “1/3” -ingressinterface “1/2” –egressVlan 200 -ingressVlan 400
- 添加service 1.
add service
Example:
add service ips_service1 192.168.10.2 TCP * -healthMonitor NO -usip YES -useproxyport NO -contentInspectionProfileName ipsprof1
- 添加service 2.
add service
Example:
add service ips_service2 192.168.10.3 TCP * -healthMonitor NO -usip YES -useproxyport NO -contentInspectionProfileName ipsprof2
- 添加a load balancing virtual server.
add lb vserver
Example:
add lb vserver lb_inline_vserver TCP 192.0.2.100 *
- Bind the services to the load balancing virtual server.
bind lb vserver bind lb vserver
Example:
bind lb vserver lb_inline_vserver ips_service1bind lb vserver lb_inline_vserver ips_service2
- Specify the load balancing virtual server in the content inspection action.
add contentInspection action
Example:
add contentInspection action ips_action -type INLINEINSPECTION -serverName lb_inline_vserver
- 添加a content inspection policy. Specify the content inspection action in the policy.
add contentInspection policy
Example:
add contentInspection policy ips_pol -rule "HTTP.REQ.METHOD.NE(\"CONNECT\")" -action ips_action
- 添加a proxy virtual server.
add cs vserver
Example:
add cs vserver transparentcs PROXY * * -l2Conn ON
- Bind the content inspection policy to the virtual server.
bind cs vserver
Example:
bind cs vserver explicitcs -policyName ips_pol -priority 1 -gotoPriorityExpression END -type REQUEST
Configuration using the GUI
Navigate toSystem > Settings. InModes and Features, clickConfigure Modes.
Navigate toSystem > Settings. InModes and Features, clickConfigure Advanced Features.
Navigate toSystem > Network > VLANs > Add. Add four VLANs and tag them to the interfaces.
Navigate toSecure Web Gateway > Content Inspection > Content Inspection Profiles. Click添加.
Specify the ingress and egress VLANs.
Create another profiles. Specify a different ingress and egress VLAN in the second profile.
Navigate to负载平衡服务> >添加and add a service. InAdvanced Settings, clickProfiles. In theCI Profile Namelist, select the content inspection profile created earlier. InService Settings, setUse Source IP Addressto YES andUse Proxy Portto No. InBasic Settings, setHealth Monitoringto NO.
Create two services. Specify dummy IP addresses that are not owned by any of the devices, including the inline devices. Specify profile 1 in service 1, and profile 2 in service 2.
Navigate toLoad Balancing > Virtual Servers > Add. Create a TCP load balancing virtual server.
- ClickOK.
Click inside the负载均衡虚拟服务器服务绑定section. InService Binding, click the arrow in选择服务. Select the two services created earlier, and clickSelect. ClickBind.
Navigate toSecure Web Gateway > Proxy Virtual Servers> Add. Specify a name, IP address, and port. InAdvanced Settings, selectPolicies. Click the “+” sign.
InChoose PolicyselectContent Inspection. ClickContinue.
Click添加. Specify a name. InAction, click添加.
Specify a name. InType, selectINLINEINSPECTION. InServer Name, select the load balancing virtual server created earlier.
ClickCreate. Specify the rule and clickCreate.
- ClickBind.
- ClickDone.
