The Juniper Networks SRX Series Gateway IDPS must protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing anomaly-based detection.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
---|---|---|---|---|---|---|
medium | V-214627 | SRG-NET-000362-IDPS-00197 | JUSX-IP-000018 | SV-214627r997697_rule | 2024-06-10 | 2 |
Description |
---|
If the network does not provide safeguards against DoS attack, network resources will be unavailable to users. Installation of IDPS components (i.e., sensors) 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. Detection components that use pattern recognition pre-processors can detect attacks when signatures for the attack do not exist or are not installed. These attacks include zero-day attacks which are new attacks for which vendors have not yet developed signatures. This requirement applies to the communications traffic functionality of the IDPS as it pertains to handling communications traffic, rather than to the IDPS device itself. The Juniper SRX must be configured with screens using the Firewall STIG, but must also be configured for anomaly-based protection using various locally developed anomaly-based attack objects. |
ℹ️ Check |
---|
Verify that the anomaly-based attack object was created. [edit] show idp security policies If anomaly-based attack objects are not created, bound to a zone, and active, this is a finding. |
✔️ Fix |
---|
Create a protocol anomaly-based attack object: Specify a name for the attack. [edit] security idp custom-attack anomaly1 Specify common properties for the attack. [edit security idp custom-attack anomaly1] set severity info set time-binding scope peer count 2 Specify the attack type and test condition. [edit] security idp custom-attack anomaly1set attack-type anomaly test OPTIONS_UNSUPPORTED Specify other properties for the anomaly attack. [edit] security idp custom-attack anomaly1] set attack-type anomaly service TCP u set attack-type anomaly direction any attack-type anomaly shellcode spark |