The DataPower Gateway providing content filtering must protect against known types of Denial of Service (DoS) attacks by employing signatures.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-65275	WSDP-AG-000101	SV-79765r1_rule		Medium

Description
If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users. Installation of content filtering gateways and application layer firewalls at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks and monitoring for anomalies in traffic volume, type, or protocol usage. Detection components that use signatures can detect known attacks by using known attack signatures. Signatures are usually obtained from and updated by the ALG component vendor. This requirement applies to the communications traffic functionality of the ALG as it pertains to handling communications traffic, rather than to the ALG device itself.

Description

If the network does not provide safeguards against DoS attacks, network resources will be unavailable to users. Installation of content filtering gateways and application layer firewalls at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks and monitoring for anomalies in traffic volume, type, or protocol usage. Detection components that use signatures can detect known attacks by using known attack signatures. Signatures are usually obtained from and updated by the ALG component vendor. This requirement applies to the communications traffic functionality of the ALG as it pertains to handling communications traffic, rather than to the ALG device itself.

STIG	Date
IBM DataPower ALG Security Technical Implementation Guide	2016-01-21

Details

Check Text ( C-65903r1_chk )
XML DoS Single message attacks: Jumbo Payload, Recursion, Mega Tags, Coercive parsing, Public key; Multiple message: XML flood, Resource hijack. WebGUI Services >> XML Firewall >> Edit XML Firewall XML, Threat Protection tab. AAA DoS Protection against DoS flooding attacks. WebGUI Objects >> XML Processing >> AAA Policy, Main tab. PKCS #7 Document DoS signature-limit protection. WebGUI Objects >> XML Processing >> Processing Action, select Crypto Binary action type. Service level monitor (SLM) policy. WebGUI Objects >> Monitoring >> SLM Policy. If these items are not configured, this is a finding.

Check Text ( C-65903r1_chk )

XML DoS
Single message attacks: Jumbo Payload, Recursion, Mega Tags, Coercive parsing, Public key; Multiple message: XML flood, Resource hijack. WebGUI Services >> XML Firewall >> Edit XML Firewall XML, Threat Protection tab.

AAA DoS
Protection against DoS flooding attacks. WebGUI Objects >> XML Processing >> AAA Policy, Main tab.

PKCS #7
Document DoS signature-limit protection. WebGUI Objects >> XML Processing >> Processing Action, select Crypto Binary action type.

Service level monitor (SLM) policy. WebGUI Objects >> Monitoring >> SLM Policy.

If these items are not configured, this is a finding.

Fix Text (F-71215r1_fix)
XML DoS Single message attacks: Jumbo Payload, Recursion, Mega Tags, Coercive parsing, Public key; Multiple message: XML flood, Resource hijack. WebGUI Services >> XML Firewall >> Edit XML Firewall XML, Threat Protection tab. AAA DoS Protection against DoS flooding attacks. WebGUI Objects >> XML Processing >> AAA Policy, Main tab. PKCS #7 Document DoS signature-limit protection. WebGUI Objects >> XML Processing >> Processing Action, select Crypto Binary action type. Service level monitor (SLM) policy. WebGUI Objects >> Monitoring >> SLM Policy.

Fix Text (F-71215r1_fix)