SV-74515r1_rule
V-60085
SRG-NET-000319-ALG-000153
F5BI-AS-000167
CAT II
10
If the BIG-IP ASM module is used to support content filtering as part of the traffic management functionality of the BIG-IP Core, configure the BIG-IP ASM module to detect code injection attacks launched against application objects, including, at a minimum, application URLs and application code.
If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
Verify the BIG-IP ASM module is configured to detect code injection attacks launched against application objects, including, at a minimum, application URLs and application code.
Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
Select Virtual Servers(s) from the list to verify the configuration of an ASM policy to detect code injection attacks.
Navigate to the Security >> Policies tab.
Set "Policy Settings" to "Advanced".
Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
Navigate to the BIG-IP System manager >> Security >> Application Security >> Security Policies.
Select the Security Policy that has been assigned to the Virtual Server(s).
Verify "Enforcement Mode" is Transparent or Blocking.
Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
Review the list under "Assigned Signature Sets" for the following signatures:
Generic Detection Signatures
Custom Systems Signature Set (based on systems identified in the application make-up).
Verify the "Assignment Signature Sets" listed above have the "Alarm" button checked.
If the BIG-IP ASM module is not configured to detect code injection attacks launched against application objects, including, at a minimum, application URLs and application code, this is a finding.
V-60085
False
F5BI-AS-000167
If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.
Verify the BIG-IP ASM module is configured to detect code injection attacks launched against application objects, including, at a minimum, application URLs and application code.
Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.
Select Virtual Servers(s) from the list to verify the configuration of an ASM policy to detect code injection attacks.
Navigate to the Security >> Policies tab.
Set "Policy Settings" to "Advanced".
Verify that "Application Security Policy" is Enabled and "Policy" is set to use an ASM policy for the virtual server.
Navigate to the BIG-IP System manager >> Security >> Application Security >> Security Policies.
Select the Security Policy that has been assigned to the Virtual Server(s).
Verify "Enforcement Mode" is Transparent or Blocking.
Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
Review the list under "Assigned Signature Sets" for the following signatures:
Generic Detection Signatures
Custom Systems Signature Set (based on systems identified in the application make-up).
Verify the "Assignment Signature Sets" listed above have the "Alarm" button checked.
If the BIG-IP ASM module is not configured to detect code injection attacks launched against application objects, including, at a minimum, application URLs and application code, this is a finding.
M
2841