FAQ-000361 - Code Quality vs Security Vulnerabilities / Unused and Obsolete Code Management

To handle security issues in unused helper methods, you should refactor the code to ensure they don't bypass security measures. If the methods handle both standard and custom fields, split them into separate classes, with one explicitly marked as "with sharing" to enforce sharing rules. Also, implement CRUD/FLS checks where necessary, even for helper methods. If the methods are no longer needed, it's best to remove them to eliminate potential vulnerabilities.

The FAQ content is accurate and well-structured, with no outdated content detected. The answer appropriately covers the key security concerns: sharing rule enforcement through 'with sharing' keyword and CRUD/FLS checks. Minor improvement made to clarify the sharing keyword syntax by adding quotes around "with sharing" for better readability. The FAQ relates to two specific security rules: ApexSharingViolations applies because the FAQ discusses enforcing sharing rules through the 'with sharing' keyword and addresses sharing rule bypasses in helper methods. The FAQ specifically mentions splitting classes and marking one as "with sharing" to enforce sharing rules, which directly addresses sharing violations. ApexCRUDViolation applies because the FAQ explicitly discusses implementing "CRUD/FLS checks where necessary, even for helper methods," which directly relates to preventing CRUD (Create, Read, Update, Delete) and FLS (Field Level Security) violations in Apex code.