18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6: Configuring Application Defenses<br />

Creating Web or Secure Web Application Defenses<br />

In the Type field, you can specify whether this defense will be used to protect a<br />

server, client, or both, as follows.<br />

• Combined—[Web only] This option allows you to create an Application<br />

Defense that can protect both a Web client (outbound) and a Web server<br />

(inbound) behind the <strong>Sidewinder</strong> <strong>G2</strong>. When you select this option, all <strong>of</strong> the<br />

configuration options for this defense will appear. However, some <strong>of</strong> the<br />

options that you configure will only apply to the client or server. (For<br />

example, HTTP Request properties do not apply to the client. Therefore, if<br />

you select Combined, HTTP Request properties that you configure will only<br />

apply to the server.)<br />

• Client—This option allows you to create an Application Defense that<br />

protects a client behind the <strong>Sidewinder</strong> <strong>G2</strong>. Options that do not apply for<br />

client protection (such as HTTP Requests) will not be available for<br />

configuration.<br />

• Server—This option allows you to create an Application Defense that<br />

protects a server behind the <strong>Sidewinder</strong> <strong>G2</strong>. Options that do not apply for<br />

server protection (such as Content Control options other than SOAP) will<br />

not be available for configuration.<br />

To enable enforcement <strong>of</strong> HTTP proxy standards in a manner that allows traffic<br />

from systems that do not adhere to strict RFC standards for the HTTP proxy,<br />

select the Relax Protocol Enforcements option. Enabling relaxed mode allows<br />

the following RFC infractions:<br />

• Media types in Content-Type: headers in a relaxed form, where the subtype<br />

is not required<br />

• Empty headers<br />

• Duplicated responses from the server where the response is the same but<br />

the version is different<br />

• Query strings containing arbitrary data<br />

Caution: Each listed infraction introduces an element <strong>of</strong> risk into your security<br />

policy, particularly if enabled on server-side rules. Use this mode only when<br />

necessary, and implement on a rule-by-rule basis.<br />

Select this option if the above infractions are acceptable or required in your<br />

network. When you enable this option, you will also need to specify whether<br />

the protocol enforcements will be relaxed when receiving HTTP traffic from<br />

clients, servers, or both by selecting one <strong>of</strong> the following options from the dropdown<br />

list:<br />

• Client—Select this option to relax protocol enforcements only when<br />

receiving HTTP traffic from clients.<br />

• Server—Select this option to relax protocol enforcements only when<br />

receiving HTTP traffic from servers.<br />

• Client and Server—Select this option to relax protocol enforcements when<br />

receiving HTTP traffic from both clients and servers.<br />

157

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!