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

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.

SQL injection attacks are the most prevalent attacks against web applications and databases. These attacks inject SQL commands that can read, modify, or compromise the meaning of the original SQL query. An attacker can spoof identity; expose, tamper, destroy, or make existing data unavailable; or gain unauthorized privileges on the database server.

Compliance requires the ALG to have the capability to prevent SQL code injections. Examples include a Web Application Firewalls (WAFs) or database application gateways.

Satisfies: SRG-NET-000318-ALG-000152, SRG-NET-000319-ALG-000020

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 "SQL-Injection" in the "Attack Type" field and click "Apply". 10. Verify "Block" is checked for all signatures and "Status" is set to "Enforced".

If the BIG-IP appliance is not configured to prevent SQL injection attacks launched against data storage objects, including, at a minimum, databases, database records, and database fields, this is a finding.

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 "SQL-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 "Apply Policy".