You are configuring security policy for your organization and need to implement traffic control based on user identity. Your security team wants to…

To enforce identity-based access control in Check Point R82, administrators must utilize Access Role objects. Once user identity information is acquired via an Identity Source (such as the Identity Collector), the next logical step is to create an Access Role object that maps to the specific users or Active Directory groups (e.g., the Finance department). This Access Role is then placed in the Source column of an Access Control Policy rule, specifying the destination server and the "Accept" action. A subsequent rule can be created to drop access for other users. This method ensures that the firewall dynamically applies access control based on authenticated user identity rather than static IP addresses.

- Option B: Network objects represent static IP addresses or subnets, not user identities. Identity Awareness requires the use of Access Roles.

- Option C: Ordered Layers are for policy structuring, and Threat Prevention signatures do not enforce basic user-based access control to specific servers.

- Option D: HTTPS Inspection decrypts SSL/TLS traffic for content inspection; it is not the mechanism for identifying users or enforcing identity-based access rules.

- Option E: SmartLog is a logging and monitoring tool, not a configuration interface for creating or enforcing access control policies.

- Check Point R82 Identity Awareness Administration Guide, Section: "Configuring Identity Awareness" -> "Access Roles".

- Check Point R82 Security Management Administration Guide, Section: "Creating an Access Control Policy".