"<xml_rule_name>"

Enter a name that can be referenced by other parts of the configuration. You will use the name to select the rule in an XML protection policy. The maximum length is 63 characters.

action {alert | alert_deny | block-period | redirect | send_403_forbidden | deny_no_log}

Select one of the following actions that FortiWeb performs when a request violates the rule:

• alert—Accept the request and generate an alert email and/or log message.

• alert_deny—Block the request (or reset the connection) and generate an alert email and/or log message.

  You can customize the web page that FortiWeb returns to the client with the HTTP status code. For details, see system replacemsg.

• block-period—Block subsequent requests from the client for a number of seconds. Also configure waf xml-validation.

• redirect—Redirect the request to the URL that you specify in the protection profile and generate an alert email and/or log message. Also configure redirect-url "<redirect_fqdn>" and rdt-reason {enable | disable}.

• send_403_forbidden—Reply to the client with an HTTP 403 Access Forbidden error message and generate an alert email and/or log message.

• deny_no_log—Deny a request. Do not generate a log message.

Caution:FortiWeb ignores this setting when monitor-mode {enable | disable} is enabled.

Note: Logging and/or alert email will occur only if enabled and configured. For details, see log disk and log alertMail.

block-period <period_int>

Enter the amount of time (in seconds) that you want to block subsequent requests from a client after FortiWeb detects a rule violation. This setting is available only when waf xml-validation is block-period.

The valid range is 1–3,600.

expansion-entity-check {enable | disable}

Enable to trigger the waf xml-validation if an HTTP request contains an XML recursive entity expansion.

To enable this option, you must first enable waf xml-validation.

external-entity-check {enable | disable}

Enable to trigger the waf xml-validation if an HTTP request contains an external entity in XML.

To enable this option, you must first enable waf xml-validation.

host "<host_name_str>"

Enter the name of a protected host that the Host: field of an HTTP request must match in order for the rule to apply. For details, see server-policy allow-hosts.

host-status {enable | disable}

Enable to compare the XML rule to the Host: field in the HTTP header. If enabled, also configure waf xml-validation.

request-file "<file_str>"

Depending on your selection for waf xml-validation, enter either:

• plain—The literal URL, such as /index.php, that the HTTP request must contain in order to match the rule. The URL must begin with a slash ( / ).
• regular—A regular expression, such as ^/*.php, matching the URLs to which the rule should apply. The pattern does not require a slash ( / ), but it must match URLs that begin with a slash, such as /index.cfm.

Do not include the domain name, such as www.example.com, which is configured separately in waf xml-validation.

request-type {plain | regular}

Select whether waf xml-validation must contain either:

• Simple String—The field is a string that the request URL must match exactly.
• Regular Expression—The field is a regular expression that defines a set of matching URLs.

schema-file "<schema_file_name>"

Select an XML schema file.

To display a list of existing XML schema files, enter:

set schema-file ?

Note, if you select an XML schema file that references other XML schema files, the other XML schema files must also be uploaded to FortiWeb.

severity {High Low | Medium | Info}

When rule violations are recorded in the attack log, each log message contains a Severity Level field. Select which severity level FortiWeb will use when it logs a violation of the rule:

• Low
• Medium
• High
• Info

trigger "<trigger_policy_name>"

Enter the name of the trigger, if any, to apply when the rule is violated. The maximum length is 63 characters. For details, see log trigger-policy.

To display a list of existing triggers, enter:

set trigger ?

xml-attributes-check {enable | disable}

Enable to configure waf xml-validation and waf xml-validation.

xml-limit-attr-num <limit_int>

Enter the maximum number of attributes for each element. The valid range is 1–256.

To configure this option, you must first enable waf xml-validation.

xml-limit-attrname-len <limit_int>

Enter the maximum attribute name length (in bytes) of each element. The valid range is 1–1,024.

To configure this option, you must first enable waf xml-validation.

xml-limit-attrvalue-len <limit_int>

Enter the maximum attribute value length (in bytes) of each element. The valid range is 1–2,048.

To configure this option, you must first enable waf xml-validation.

xml-limit-cdata-len <limit_int>

Enter the maximum Character Data (CDATA) length (in bytes) in XML. The valid range is 1–4,096.

To configure this option, you must first enable waf xml-validation.

xml-limit-check {enable | disable}

Enable to configure XML limits.

xml-limit-element-depth <limit_int>

Enter the maximum element depth in XML. The valid range is 1–256.

To configure this option, you must first enable waf xml-validation.

xml-limit-element-name-len <limit_int>

Enter the maximum element name length (in bytes) in XML. The valid range is 1–1,024.

To configure this option, you must first enable waf xml-validation.

"<xml_policy_name>"

Enter the name of an XML protection policy. You will use the name to select the policy in other parts of the configuration. The maximum length is 63 characters.

<entry_index>

Enter the index number of an entry to create or modify a rule for the policy. The valid range is 1–9,999,999,999,999,999,999.

"<xml_rule_1>"

Enter the sequence number of an XML protection rule to add to the XML protection policy. The maximum length is 63 characters.

soap-attachment {allow | disallow}

Specify whether the SOAP message can carry attachments.

Available only when the data-format {xml | soap} is SOAP.

ws-i-basic-profile-assertion {WSI1001 | WSI1002 | WSI1003 | WSI1004 | WSI1006 | WSI1007 | WSI1032 | WSI1033 | WSI1109 | WSI1110 | WSI1111 | WSI1201 | WSI1202 | WSI1204 | WSI1208 | WSI1301 | WSI1307 | WSI1308 | WSI1309 | WSI1318 | WSI1601 | WSI1701}

Select WSI rules that SOAP messages will adhere to.

Available only when the data-format {xml | soap} is SOAP.