FAQ-001080 - Lightning Component Security Configuration / Component Exposure and Targets

When exposing a Lightning component, it's important to follow these recommendations: - Only expose components when absolutely necessary and ensure proper security measures are in place. - Use secure alternatives like the `pubsub` module for communication instead of exposing the Lightning Message Channel (LMC) with `isExposed: true`. - If exposure is required, ensure that no sensitive data is being communicated and validate all inputs. - Follow secure coding practices, such as enforcing CRUD/FLS permissions and adhering to namespace isolation guidelines.

The FAQ content is accurate and well-structured. The main improvement made was to clarify the recommendation about Lightning Message Channel (LMC) exposure by adding the abbreviation '(LMC)' for better clarity and slightly improving the flow of the sentence structure. No other changes were needed as the content appropriately covers security best practices for component exposure. The AvoidLmcIsExposedTrue rule was selected because it directly relates to the FAQ's discussion of Lightning Message Channel exposure with `isExposed: true`. The FAQ specifically mentions 'exposing the Lightning Message Channel (LMC) with `isExposed: true`' as something to avoid, which aligns perfectly with this rule's purpose of flagging Lightning Message Channels configured with `isExposed: true` as a security concern.