The existing FAQ content is accurate and well-structured, so no substantive changes are needed. The content directly relates to two key security rules: ApexSharingViolations addresses the 'without sharing' classes mentioned in point 1, as this rule detects when sharing rules are bypassed without proper controls. ApexCRUDViolation relates to points 2 and 3 about validating access restrictions and permissions, as this rule identifies when CRUD (Create, Read, Update, Delete) permissions are not properly enforced in Apex code. Both rules are fundamental to the custom access control logic evaluation described in the FAQ. The answer maintains appropriate detail level for an FAQ format while covering the essential security review aspects.