SV-74509r1_rule
V-60079
SRG-NET-000318-ALG-000152
F5BI-AS-000161
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 prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.
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 prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.
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 prevent SQL 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 the Virtual Server(s).
Verify the "Enforcement Mode" is Blocking.
Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
Verify "Signature Staging" is Enabled.
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 "Assigned Signature Sets" listed above have the "Block" button checked.
If the BIG-IP ASM module is not configured to prevent SQL injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, and database fields, this is a finding.
V-60079
False
F5BI-AS-000161
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 prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields.
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 prevent SQL 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 the Virtual Server(s).
Verify the "Enforcement Mode" is Blocking.
Click "Attack Signatures Configurations" for "Signature Staging" under the "Configuration" section.
Verify "Signature Staging" is Enabled.
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 "Assigned Signature Sets" listed above have the "Block" button checked.
If the BIG-IP ASM module is not configured to prevent SQL injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, and database fields, this is a finding.
M
2841