FAQ-001086 - Lightning Component Security Implementation / Component Styling Security

Approved alternatives for styling Lightning namespace components include: 1. **Using Static Resources**: Save third-party CSS files in static resources and reference them using the `<ltng:require>` tag in your component markup. This ensures compliance with security policies and maintains style isolation. 2. **Avoid Certain CSS Directives**: Refrain from using `position:absolute` or `position:fixed` unless the component isn't exposed outside its namespace or is restricted to specific pages owned by the namespace.

The FAQ content is accurate and well-structured, addressing proper security practices for styling Lightning components. Minor improvements made include: (1) Changed 'is not exposed' to 'isn't exposed' for more conversational tone per brand guidelines, maintaining the same meaning and technical accuracy. The selected security rules are directly relevant: LoadCSSLinkHref relates to the FAQ's discussion of referencing CSS files and external stylesheets in Lightning components - this rule detects potentially insecure CSS loading patterns that the FAQ's recommended static resources approach helps avoid. LoadCSSApexStylesheet is relevant because it also addresses CSS loading security in the Apex/Lightning context, complementing the static resources recommendation in the FAQ. AvoidUnescapedHtmlInAura relates to the broader security context of Lightning component development and safe styling practices that the FAQ addresses, as unsafe styling can be a vector for XSS attacks that this rule helps prevent.