To protect against data mining, the F5 BIG-IP appliance providing content filtering must prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-266140	SRG-NET-000318-ALG-000014	F5BI-AP-300006	SV-266140r1024838_rule	2024-09-20	1

Description
Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to prevent attacks launched against organizational information from unauthorized data mining may result in the compromise of information. Injection attacks allow an attacker to inject code into a program or query or inject malware onto a computer to execute remote commands that can read or modify a database or change data on a website. Web applications frequently access databases to store, retrieve, and update information. An attacker can construct inputs that the database will execute. This is most commonly referred to as a code injection attack. This type of attack includes XPath and LDAP injections. Compliance requires the ALG to have the capability to prevent code injections. Examples include a Web Application Firewalls (WAFs) or database application gateways. Satisfies: SRG-NET-000318-ALG-000014, SRG-NET-000319-ALG-000015

Description

Data mining is the analysis of large quantities of data to discover patterns and is used in intelligence gathering. Failure to prevent attacks launched against organizational information from unauthorized data mining may result in the compromise of information. Injection attacks allow an attacker to inject code into a program or query or inject malware onto a computer to execute remote commands that can read or modify a database or change data on a website. Web applications frequently access databases to store, retrieve, and update information. An attacker can construct inputs that the database will execute. This is most commonly referred to as a code injection attack. This type of attack includes XPath and LDAP injections. Compliance requires the ALG to have the capability to prevent code injections. Examples include a Web Application Firewalls (WAFs) or database application gateways. Satisfies: SRG-NET-000318-ALG-000014, SRG-NET-000319-ALG-000015

ℹ️ Check
If the ALG does not perform content filtering as part of the traffic management functions, this is not applicable. From the BIG-IP GUI: 1. Security. 2. Application Security. 3. Security Policies. 4. Policies List. 5. Click the name of the policy. 6. Verify "Enforcement Mode" is set to "Blocking". 7. Select "Attack Signatures". 8. Click the filter at the top left of the signatures window. 9. Select "XPath Injection" in the "Attack Type" field and click "Apply". 10. Verify "Block" is checked for all signatures and "Status" is set to "Enforced". 11. Click the filter at the top left of the signatures window. 12. Select "LDAP Injection" in the "Attack Type" field and click "Apply". 13. Verify "Block" is checked for all signatures and "Status" is set to "Enforced". If the BIG-IP appliance is not configured to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields, this is a finding.

ℹ️ Check

If the ALG does not perform content filtering as part of the traffic management functions, this is not applicable. From the BIG-IP GUI: 1. Security. 2. Application Security. 3. Security Policies. 4. Policies List. 5. Click the name of the policy. 6. Verify "Enforcement Mode" is set to "Blocking". 7. Select "Attack Signatures". 8. Click the filter at the top left of the signatures window. 9. Select "XPath Injection" in the "Attack Type" field and click "Apply". 10. Verify "Block" is checked for all signatures and "Status" is set to "Enforced". 11. Click the filter at the top left of the signatures window. 12. Select "LDAP Injection" in the "Attack Type" field and click "Apply". 13. Verify "Block" is checked for all signatures and "Status" is set to "Enforced". If the BIG-IP appliance is not configured to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields, this is a finding.

✔️ Fix
From the BIG-IP GUI: 1. Security. 2. Application Security. 3. Security Policies. 4. Policies List. 5. Click the name of the policy. 6. Set "Enforcement Mode" to "Blocking". 7. Select "Attack Signatures". 8. Click the filter at the top left of the signatures window. 9. Select "XPath Injection" in the "Attack Type" field and click "Apply". 10. Select all signatures in the filtered list and click "Enforce". 11. Click "Enforce" again. 12. Click the filter at the top left of the signatures window. 13. Select "LDAP Injection" in the "Attack Type" field and click "Apply". 14. Select all signatures in the filtered list and click "Enforce". 15. Click "Enforce" again. 16. Click "Apply Policy".

✔️ Fix

From the BIG-IP GUI: 1. Security. 2. Application Security. 3. Security Policies. 4. Policies List. 5. Click the name of the policy. 6. Set "Enforcement Mode" to "Blocking". 7. Select "Attack Signatures". 8. Click the filter at the top left of the signatures window. 9. Select "XPath Injection" in the "Attack Type" field and click "Apply". 10. Select all signatures in the filtered list and click "Enforce". 11. Click "Enforce" again. 12. Click the filter at the top left of the signatures window. 13. Select "LDAP Injection" in the "Attack Type" field and click "Apply". 14. Select all signatures in the filtered list and click "Enforce". 15. Click "Enforce" again. 16. Click "Apply Policy".