FAQ-001593 - SQL Injection and Input Validation / Dynamic SOQL Query Construction

To implement bind variables with completely dynamic SOQL queries, follow these steps: 1. **Validate Permissions**: Ensure the user has the necessary permissions for the object and fields being queried. 2. **Whitelist Validation**: Use a whitelist of acceptable object and field names to validate user input. 3. **Use Bind Variables**: Construct the query dynamically but include user-supplied values as bind variables. Here's an example: ```apex String userSuppliedName = 'My Account'; List<SObject> records = Database.query('SELECT Id, Name FROM Account WHERE Name = :userSuppliedName WITH USER_MODE'); ``` In this example, `:userSuppliedName` is a bind variable that safely incorporates user input into the query. The `WITH USER_MODE` clause automatically enforces CRUD permissions, field-level security, and sharing rules. Always validate object and field names against the schema to prevent unauthorized access.

The FAQ content is largely accurate and addresses SOQL injection prevention well, but contains an outdated example that doesn't follow modern Salesforce security best practices. The original example lacks the WITH USER_MODE clause, which is the current recommended approach for enforcing security in dynamic queries according to the security approaches guidelines. I updated the code example to include 'WITH USER_MODE' and added an explanation of its benefits. I selected ApexSOQLInjection because the FAQ directly addresses preventing SOQL injection through bind variables - the rule detects when user input might be concatenated into SOQL queries without proper sanitization, and this FAQ teaches the secure approach using bind variables. I selected ApexCRUDViolation because the FAQ mentions validating permissions and the updated example demonstrates WITH USER_MODE which addresses CRUD permission enforcement that this rule detects. I selected ApexSharingViolations because the updated example with WITH USER_MODE also enforces sharing rules, and this rule detects when queries might bypass sharing restrictions.