Identity Awareness

R75
Administration Guide

30 December 2010

© 2010 Check Point Software Technologies Ltd. All rights reserved. This product and related documentation are protected by copyright and distributed under licensing restricting their use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form or by any means without prior written authorization of Check Point. While every precaution has been taken in the preparation of this book, Check Point assumes no responsibility for errors or omissions. This publication and features described herein are subject to change without notice. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. TRADEMARKS: Refer to the Copyright page (http://www.checkpoint.com/copyright.html) for a list of our trademarks. Refer to the Third Party copyright notices (http://www.checkpoint.com/3rd_party_copyright.html) for a list of relevant copyrights and third-party licenses.

Important Information
Latest Documentation
The latest version of this document is at: http://supportcontent.checkpoint.com/documentation_download?ID=11662 For additional technical information, visit the Check Point Support Center (http://supportcenter.checkpoint.com).

Revision History
Date 30 December 2010 15 December 2010 Description Improved documentation, formatting and document layout First release of this document

Feedback
Check Point is engaged in a continuous effort to improve its documentation. Please help us by sending your comments (mailto:cp_techpub_feedback@checkpoint.com?subject=Feedback on Identity Awareness R75 Administration Guide).

.................................23 Enabling Identity Awareness on the Security Gateway ................................................................................................................15 Acquiring Identities with Identity Agents .......................................40 Identity Sources ..46 Performance ...........................................................................52 Server Certificates ........................................................................................................54 Advanced Identity Agents Configuration ....................................34 Configuring Identity Agents....................................................................................34 Identity Agent Deployment Methods ..........................................................................................................................................................................49 Adding a New Language.......36 Server Discovery and Trust.......................................................................................................................................................................................40 Enabling Identity Awareness on the Log Server ........................................................................................Contents Important Information ...................................................................31 Configuring Captive Portal in SmartDashboard ..............................................................................6 Introduction .......................28 Access Role Objects ............... 9 Identity Agents .........................................................................26 Using Identity Awareness in the Firewall Rule Base .................................................. 8 Captive Portal ........................... 6 AD Query ........................13 Acquiring Identities for Active Directory Users ...........29 Negate and Drop .........................................................................................................................................................................................................................................................................37 Configuring Identity Agents in SmartDashboard.............................20 Configuring Identity Awareness ......41 Choosing Identity Sources .............................................................41 Advanced AD Query Configuration ................................................32 User Access ........45 Multiple Gateway Environments .................34 Identity Agent Types ......................................................................................................47 Advanced Captive Portal Configuration .........................................................................................................................................38 Configuring Identity Awareness for a Log Server ....................................46 Non-English Language Support ........................................................................................................................................................................................................................................42 Permissions and Timeout .............................................18 Acquiring Identities in Application Control ............................31 Access Settings ........3 Getting Started With Identity Awareness ........................................56 ..............46 Troubleshooting ...................................................................................41 Specifying Domain Controllers per Security Gateway .................................................................................29 Source and Destination Fields .......................................................................................32 Customize Appearance..........31 Authentication Settings ...........................................23 Results of the Wizard .............................................................................................................11 Deployment ...........................................13 Acquiring Identities with the Captive Portal .26 Creating Access Roles ..........................31 Portal Network Location .........................................................................................................................................................................41 Configuring Identity Awareness for a Domain Forest (Subdomains) .....................................................................................................................................................................................................................................................................................................................49 Customizing Text Strings .............................................................................................................................................................................................................................................................................................................................................30 Negate and Block ................................33 Agent Deployment from the Portal ............................29 Using Identity Awareness in the Application Control Rule Base ................................56 Customizing Parameters ......................12 Identity Awareness Scenarios .......

.................................................................................................................................................................................................................................................61 Testing Identity Agents .62 Perimeter Security Gateway with Identity Awareness ......................................................................................................................................................................66 Distributed Enterprise with Branch Offices ....................................................................................................................................................................................84 Option Comparison..............................................................61 Testing Identity Sources .............................................63 Large Scale Enterprise Deployment .....................................................................................................................................................77 Custom Identity Agent msi ............................................................57 Deployment Options ...................77 Configuring Installation .58 Configuring Clusters in Bridge Mode .....................71 References .......................................64 Network Segregation ..............................................................................................................................................66 Wireless Campus.....73 SmartDashboard Configuration ...................................................83 Server Discovery and Trust Options ........................................62 Deployment Scenarios ..........................................................[Features] Section .............................................................................................................73 AD Configuration ..................................................................................................................................60 Configuring Cluster and Bridge Support ...............82 Server Discovery and Trust .......................................................................................................................................77 Using the cpmsi_tool........................................................56 Advanced Deployment ..........................................93 .....................................................................................................81 Sample INI File ............................................................................................................................................................71 How SSO Operates ............................................................................................................84 File Name Based Server Discovery ........75 Prepackaging Identity Agents ........79 Configuring Deployed Identity Agents ......................................................................................................................................................................................................................................................................[Properties] Section ................62 Data Center Protection ................................83 Introduction .......................................................................................................................................89 Prepackaging Identity Agents ....60 Configuring the Cluster ...85 AD Based Configuration ...........................................90 Index .......................................86 DNS Based Configuration ..72 SSO Configuration.........................58 Preparing Clusters with a Bridge ...60 Configuring the External Identity Awareness Gateway .....................59 Checking the Bridge Configuration.........................................................................69 Kerberos SSO Configuration ......................................................................................88 Remote Registry .....................61 Deploying a Test Environment ..........................................................71 Overview ........................................................................................................................................................68 Dedicated Identity Acquisition Gateway .....................exe.........................................................................77 Background ......................................[AddFiles] Section .....................................................................................................................................................................................................................................................57 Introduction ...............................Prepackaging Identity Agent Installation ...78 Configuring Installed Features .........................

firewalls use IP addresses to monitor traffic and are unaware of the user and machine identities behind those IP addresses. It is currently available on the Firewall blade and Application Control blade and will operate with other blades in the future. It is applicable for both Active Directory and non-Active Directory based networks as well as for employees and guest users. Identity Awareness is an easy to deploy and scalable solution. This lets you enforce access and audit data based on identity. Identity Awareness removes this notion of anonymity since it maps users and machine identities. this lets you create firewall rules with any of these properties. You can define a firewall rule for specific users when they send traffic from specific machines or a firewall rule for a specific user regardless of which machine they send traffic from. Identity Awareness lets you easily configure network access and auditing based on network location and:   The identity of a user The identity of a machine When Identity Awareness identifies a source or destination.Chapter 1 Getting Started With Identity Awareness In This Chapter Introduction Deployment Identity Awareness Scenarios 6 12 13 Introduction Traditionally. Page 6 . For example. it shows the IP address of the user or machine with a name.

Identity Awareness gets identities from these acquisition sources:    AD Query Captive Portal Identity Agent The table below shows how identity sources are different in terms of usage and deployment considerations. you use Access Role objects to define users. Getting Started With Identity Awareness Page 7 . Depending on those considerations. machines and network locations as one object. you can configure Identity Awareness to use one identity source or a combination of identity sources ("Choosing Identity Sources" on page 41). Identity Awareness also lets you see user activity in SmartView Tracker and SmartEvent based on user and machine name and not just IP addresses.Introduction In SmartDashboard.

1.  The technology is based on querying the Active Directory Security Event Logs and extracting the user and machine mapping to the network address from them. The Security Gateway registers to receive security event logs from the Active Directory domain controllers. The Security Gateway communicates directly with the Active Directory domain controllers and does not require a separate server. Getting Started With Identity Awareness Page 8 . reads emails through Exchange. clientless identity acquisition method. For example. It is based on Active Directory integration and it is completely transparent to the user. See Advanced Deployment (on page 57) for more information. The AD Query option operates when:  An identified asset (user or machine) tries to access an Intranet resource that creates an authentication request. a standard Microsoft protocol. No installation is necessary on the clients or on the Active Directory server.Firewall Rule Base Example The steps listed in the example align with the numbers in the image below. It is based on Windows Management Instrumentation (WMI). unlocks a screen. 2. How AD Query Operates . or accesses an Intranet portal. Identity aware gateways can share the identity information that they acquire with other identity aware gateways.Introduction Source AD Query Description Gets identity data seamlessly from Microsoft Active Directory (AD) Recommended Usage  Identity based auditing and logging Leveraging identity in Internet application control Basic identity enforcement in the internal network Identity based enforcement for non-AD users (non-Windows and guest users) For deployment of Identity Agents Leveraging identity for Data Center protection Protecting highly sensitive servers When accuracy in detecting identity is crucial Deployment Considerations  Easy configuration (requires AD administrator credentials) Preferred for desktop users Only detects AD users and machines     Captive Portal Sends unidentified users to a Web portal for authentication   Used for identity enforcement (not intended for logging purposes)  Identity Agent A lightweight endpoint  agent that authenticates securely with Single Sign-On  (SSO)   See Choosing Identity Sources (on page 41). In this way. AD Query AD Query is an easy to deploy. A user logs in to a desktop computer using his Active Directory credentials. when a user logs in. AD Query is selected as a way to acquire identities. shares a network drive. users that need to pass through several enforcement points are only identified once.

It is a simple method that authenticates users through a web interface before granting them access to Intranet resources. machine name and source IP address). Configure what is required in the Portal Settings. they might be able to access the resource. When users try to access a protected resource.Introduction 3. they get a web page that must fill out to continue. The Active Directory DC sends the security event log to the Security Gateway. 5. The Security Gateway extracts the user and IP information (user name@domain. Unidentified users cannot access that resource because of rules with access roles in the Firewall / Application Rule Base. When these criteria are true. Captive Portal The Captive Portal is a tool that acquires identities from unidentified users. Figure 1-1 Captive Portal Login The Captive Portal option operates when a user tries to access a web resource and all of these apply:   The Captive Portal is selected as a way to acquire identities. The user initiates a connection to the Internet. But if users are identified. Captive Portal acquires the identities of users. 4. For guest users. The Security Gateway confirms that the user has been identified and lets him access the Internet based on the policy. enter required credentials. From the Captive Portal users can:   Enter an existing user name and password if they have them. Getting Started With Identity Awareness Page 9 .

or RADIUS. 3. Check Point internal credentials. A user wants to access the Internal Data Center. 1. Getting Started With Identity Awareness Page 10 . 4. The credentials can be AD or other Check Point supported authentication methods.Firewall Rule Base The steps listed in the example align with the numbers in the image below. How Captive Portal Operates . 5. In this example they are verified with the AD server.Introduction  Click a link to download an Identity Awareness agent. such as LDAP. The user enters his regular office credentials. 2. The credentials are verified. Configure this in the Portal Settings. Identity Awareness does not recognize him and redirects the browser to the Captive Portal. The user can now go to the originally requested URL.

Custom . The Security Gateway enabled with Identity Awareness does not recognize him and sends him to the Captive Portal. users enter their credentials manually. Seamless connectivity .Example This is how a user downloads the Identity Agent from the Captive Portal: 1. 2. A user logs in to his PC with his credentials and wants to access the Internal Data Center. see the Prepackaging Identity Agents (on page 77).all necessary configuration is done by administrators and does not require user input. It contains a link that he can use to download the Identity Agent. The Full agent performs packet tagging and machine authentication.a customized installation package. You can let them save these credentials. The Security Gateway sends a page that shows the Captive Portal to the user. Identity Agents also gives you strong (Kerberos based) user and machine authentication. Users can download and install Identity Agents from the Captive Portal or you can distribute MSI files to computers with distribution software or any other method (such as telling them where to download the client from). 3.Introduction Identity Agents Identity Agents are dedicated client agents installed on users' computers that acquire and report identities to the Security Gateway. Cannot be configured with packet tagging or machine authentication.users stay automatically identified when they move between networks. it will automatically revert to installing the Light agent.does not require administrator permissions for installation.requires administrator permissions for installation.   There are 3 types of Identity Agents:  Full . Connectivity through roaming . Added security . Using Identity Agents gives you:    User and machine identity Minimal user intervention .   For more information. If installed by a user without administrator permissions.you can use the patented packet tagging technology to prevent IP Spoofing. Light . How You Download an Identity Agent . Getting Started With Identity Awareness Page 11 . as the client detects the movement and reconnects. If you do not want to use SSO.transparent authentication using Kerberos Single Sign-On (SSO) when users are logged in to the domain.

Getting Started With Identity Awareness Page 12 . You can also share identities between gateways managed in different Multi-Domain Servers.Deployment 4. It is frequently used in conjunction with Application Control. The user is authenticated and the Security Gateway sends the connection to its destination according to the Firewall Rule Base. Identity awareness supports ClusterXL HA and LS modes. you can deploy a gateway cluster in Active-Standby (HA) or Active-Active (LS) modes. 5. you can configure the gateways to share identity information.   In Bridge mode it can use an existing subnet with no change to the hosts' IP addresses. If you deploy Identity Awareness on more than one gateway. Identity Awareness can be enabled on an internal gateway in front of internal servers. The user downloads the Identity Agent from the Captive Portal and installs it on his PC. Identity Awareness can be deployed in Bridge mode or Route mode. In Route mode the gateway acts as a router with different subnets connected to its network interfaces. You can have one or more gateways acquire identities and share them with the other gateways. Deploy on branch office gateways and central gateways. To protect internal data centers. Deploy on several data center gateways. Deployment Identity Awareness is commonly enabled on the perimeter gateway of the organization. the user is automatically connected. For redundancy. such as data centers. The Identity Agent client connects to the Security Gateway. If SSO with Kerberos is configured. This can be in addition to on the perimeter gateway but does not require a perimeter gateway. Common scenarios include:    Deploy on your perimeter gateway and data center gateway. 6.

4. Active Directory users that log in and are authenticated will have seamless access to resources based on Firewall Rule Base rules. the IT administrator does these steps: 1.168. but that limits him to operating it only from his desk. To make this scenario work. selects AD Query as one of the Identity Sources and installs the policy. To enforce access options. The last scenario describes the use of Identity Awareness in an Application Control environment. Acquiring Identities for Active Directory Users Organizations that use Microsoft Active Directory as a central user repository for employee data can use AD Query to acquire identities. 2. Checks SmartView Tracker to make sure the system identifies John Adams in the logs. Let's examine a scenario to understand what AD Query does. Scenario: Laptop Access John Adams is an HR partner in the ACME organization. Enables Identity Awareness on a gateway.3. He received a laptop and wants to access the HR Web Server from anywhere in the organization.3. The first 3 scenarios describe different situations of acquiring identities in a Firewall Rule Base environment.Identity Awareness Scenarios Identity Awareness Scenarios This section describes scenarios in which you can use Identity Awareness to let users access network resources. make rules in the Firewall Rule Base that contain access role objects. ACME IT wants to limit access to HR servers to designated IP addresses to minimize malware infection and unauthorized access risks. Adds an access role object to the Firewall Rule Base that lets John Adams access the HR Web Server from any machine and from any location. machines and network locations as one object. 3. the gateway policy permits access only from John's desktop which is assigned a status IP address 192. An access role object defines users.217). The IT department gave the laptop a static IP address.217. Sees how the system tracks the actions of the access role in SmartView Tracker. Getting Started With Identity Awareness Page 13 . Thus. When you set the AD Query option to get identities.168. He wants to move around the organization and continue to have access to the HR Web Server. you are configuring clientless employee access for all Active Directory users. The current Rule Base contains a rule that lets John Adams access the HR Web Server from his laptop with a static IP (192.

Note .COM. This uses the identity acquired from AD Query.3. Getting Started With Identity Awareness Page 14 .ACME. If John Adams is not identified (the IT administrator does not see the log).217.Identity Awareness Scenarios User Identification in the Logs The SmartView Tracker log below shows how the system recognizes John Adams as the user behind IP 192. he should lock and unlock the computer. This log entry shows that the system maps the source IP to the user John Adams from CORP.AD Query maps the users based on AD activity. This can take some time and depends on user activity.168.

The IT administrator can then remove the static IP from John Adam's laptop and give it a dynamic IP. it is necessary for the administrator to change the current rule in the Rule Base. To do this. She wants to access the internal Finance Web server from her iPad. they are automatically sent to the Captive Portal. Her access to resources is based on rules in the Firewall Rule Base. Let's examine some scenarios to understand what the Captive Portal does and the configuration required for each scenario. Unmanaged. it is necessary to create an access role ("Creating Access Roles" on page 26) for John Adams that includes the specific user John Adams from any network and any machine. guest users such as partners or contractors. Acquiring Identities with the Captive Portal The Captive Portal lets you acquire identities from unidentified users such as:   Managed users connecting to the network from unknown devices such as Linux computers or iPhones. she can enter her AD credentials in the Captive Portal and then get the same access as on her office computer. However. Getting Started With Identity Awareness Page 15 . Because the iPad is not a member of the Active Directory domain. she cannot identify seamlessly with AD Query. The Security Gateway lets the user John Adams access the HR Web server from his laptop with a dynamic IP as the HR_Partner access role tells it that the user John Adams from any machine and any network is permitted access.Identity Awareness Scenarios Using Access Roles To let John Adams access the HR Web Server from any machine. If unidentified users try to connect to resources in the network that are restricted to identified users. Scenario: Recognized User from Unmanaged Device The CEO of ACME recently bought her own personal iPad. Then the IT administrator replaces the source object of the current rule with the HR_Partner access role object and installs the policy for the changes to be updated.

Select the Redirect http connections to an authentication (captive) portal. c) In the Machines tab make sure that Any machine is selected. Create a new rule in the Firewall Rule Base to let Jennifer McHanry access network destinations. She can successfully browse to the Finance server. From the Source of the rule. User Experience Jennifer McHanry does these steps: 1. make sure that Name and password login is selected. 4. Note: redirection will not occur if the source IP is already mapped to a user checkbox. Click OK. Browses to the Finance server from her iPad. The Action Properties window opens. a) Enter a Name for the Access Role. A Welcome to the network window opens. 3. 5. 2. 2. Select accept as the Action. Right-click the Action column and select Edit Properties. She enters her usual system credentials in the Captive Portal. 7. right-click to create an Access Role. select Specific users and choose Jennifer McHanry. b) In the Users tab. the IT administrator must: 1. Enable Identity Awareness on a gateway and select Captive Portal as one of the Identity Sources.Identity Awareness Scenarios Required SmartDashboard Configuration To make this scenario work. 6. Getting Started With Identity Awareness Page 16 . 3. d) Click OK. The Access Role is added to the rule. In the Portal Settings window in the User Access section. The Captive Portal opens because she is not identified and therefore cannot access the Finance Server.

the Captive Portal opens. and phone number in the portal. Required SmartDashboard Configuration To make this scenario work. This uses the identity acquired from Captive Portal. Afterwards they are given access to the Iinternet for a specified period of time. configure:    The data guests must enter. In the Portal Settings window in the User Access section. Amy. the IT administrator configures the Captive Portal to let unregistered guests log in to the portal to get network access. the CEO wants to let them access the Internet on their own laptops. While they visit. 4. 2. email address. When guests browse to the Internet. She makes a rule in the Firewall Rule Base to let unauthenticated guests access the Internet only. 3.Settings. Guests enter their name. company. Click Unregistered guest login .Identity Awareness Scenarios User Identification in the Logs The SmartView Tracker log below shows how the system recognizes Jennifer McHanry from her iPad. They then agree to the terms and conditions written in a network access agreement. In the Unregistered Guest Login Settings window. Getting Started With Identity Awareness Page 17 . Scenario: Guest Users from Unmanaged Device Guests frequently come to the ACME company. Enable Identity Awareness on a gateway and select Captive Portal as one of the Identity Sources. This log entry shows that the system maps the source "Jennifer_McHanry" to the user name. make sure that Unregistered guest login is selected. the IT administrator must: 1. For how long users can access the network resources. If a user agreement is required and its text.

right-click to create an Access Role. the IT administrator wants to leverage the use of Identity Agents so: Getting Started With Identity Awareness Page 18 . She can successfully browse to the Internet for a specified period of time. (iv) In the Machines tab select Any machine if guests will access the network from their own machines or Specific machines to choose a computer that they will use. (iv) Click OK. (ii) Enter a Name for the Access Role. select Specific users and choose Unauthenticated Guests. (ix) Click OK. (v) Click OK. Amy. right-click to create an Access Role. The Action Properties window opens. Acquiring Identities with Identity Agents Scenario: Identity Agent Deployment and User Group Access The ACME organization wants to make sure that only the Finance department can access the Finance Web server. Create two new rules in the Firewall Rule Base: a) If it is not already there. She enters her identifying data in the Captive Portal and reads through and accepts a network access agreement. (v) The Access Role is added to the rule. she does these steps: 1. The current Rule Base uses static IP addresses to define access for the Finance department. (i) From the Source of the rule. (iii) In the Users tab. b) Create a rule to let Unauthorized Guests access only the internet. The Access Role is added to the rule. (vii) Right-click the Action column and select Edit Properties. Note: redirection will not occur if the source IP is already mapped to a user checkbox. A Welcome to the network window opens. 2. (viii) Select the Redirect http connections to an authentication (captive) portal. create a rule that identified users can access the internet from the organization. User Identification in the Logs The SmartView Tracker log below shows how the system recognizes a guest. The Captive Portal opens because she is not identified and therefore cannot access the Internet. In this case. 3. the identity is "guest" because that is how the user is identified in the Captive Portal. (ii) Enter a Name for the Access Role. User Experience From the perspective of a guest at ACME. (iii) In the Users tab. select All identified users. This log entry shows that the system maps the source IP address with the user's identity. Browses to an internet site from her laptop. (i) From the Source of the rule.Identity Awareness Scenarios 5. (vi) Select accept as the Action.

select All identified users. In the Identity Agent Deployment from the Portal. Users that roam the organization will have continuous access to the Finance Web server. She needs to deploy the Full Identity Agent so she can set the IP spoofing protection. In the Portal Settings window in the Users Access section. select Name and password login. She needs to configure: Identity Agents as an identity source for Identity Awareness. g) The Access Role is added to the rule. Create a rule in the Firewall Rule Base that lets only Finance department users access the Finance Web server and install policy: a) From the Source of the rule. Required SmartDashboard Configuration To make this scenario work.Identity Awareness Scenarios      Finance users will automatically be authenticated one time with SSO when logging in (using Kerberos which is built-in into Microsoft Active Directory). f) Click OK. 2. 4.Full option.This configures Identity Agent for all users. Install policy. 5. Getting Started With Identity Awareness Page 19 .  After configuration and policy install. the IT administrator must: 1. c) In the Networks tab. select Specific users and add the Active Directory Finance user group. 7. Configure Kerberos SSO ("Kerberos SSO Configuration" on page 71). A rule in the Rule Base with an access role for Finance users. Note . from all managed machines and from all locations with IP spoofing protection enabled. select Require users to download and select Identity Agent . select All identified machines and select Enforce IP spoofing protection (requires Full Identity Agent). Enable Identity Awareness on a gateway and select Identity Agents and Captive Portal as Identity Sources. right-click to create an Access Role. Amy wants Finance users to download the Identity Agent from the Captive Portal. No configuration is necessary on the client for IP spoofing protection. Agent deployment for the Finance department group from the Captive Portal. Browses to the Finance Web server. 3. you can set Identity Agent download for a specific group ("Configuring Agent Deployment for User Groups" on page 37). users that browse to the Finance Web server will get the Captive Portal and can download the Identity Agent. User Experience A Finance department user does this: 1. Access to the Finance Web server will be more secure by preventing IP spoofing attempts. b) Enter a Name for the Access Role. 6. Click the Captive Portal Settings button. e) In the Machines tab. Alternatively. d) In the Users tab.

What's Next Other options that can be configured for Identity Agents:  A method that determines how Identity Agents connect to a Security Gateway enabled with Identity Awareness and trusts it. 3. See Server Discovery and Trust (on page 37) for more details on other server discovery methods that do not require user trust confirmation. A window opens asking the user to trust the server. End user interface protection so users cannot access the client settings.The trust window opens because the user connects to the Security Gateway with Identity Awareness using the File name based server discovery option. The user clicks the link to download the Identity Agent.    Acquiring Identities in Application Control Identity Awareness and Application Control can be used together to add user awareness. machine awareness. See Server Discovery and Trust (on page 37)for more details. The user automatically connects to the gateway. See User Access (on page 33). 2.Identity Awareness Scenarios The Captive Portal opens because the user is not identified and cannot access the server. The user can successfully browse to the internet for a specified period of time. Click OK. Let users defer client installation for a set time and ask for user agreement confirmation. the File Name server discovery method is used. In this scenario. A link to download the Identity Agent is shown. and application awareness to the Check Point gateway. The user automatically connects to the Finance Web server. They work together in these procedures: Getting Started With Identity Awareness Page 20 . Access roles ("Creating Access Roles" on page 26) to leverage machine awareness. Note . A Welcome to the network window opens.

It also shows Application Control data. Getting Started With Identity Awareness Page 21 . selects AD Query as one of the Identity Sources. Required SmartDashboard Configuration To make this scenario work. You can use all the types of identity sources to acquire identities of users who try to access applications. Next. Enables the Application Control blade on a gateway.checkpoint. User identification in the Logs Logs related to application traffic in SmartView Tracker and SmartEvent show data for identified users.com/documentation_download?ID=11658). you can see which user and IP address accesses which applications. This adds a default rule to the Application Control Rule Base that allows traffic from known applications. with the tracking set to Log. 3.Identity Awareness Scenarios    Use Identity Awareness Access Roles in Application Control rules as the source or destination of the rule. Enables Identity Awareness on a gateway. the IT department can add rules to block specific applications or track them differently in the Application Control policy to make it even more effective. the IT administrator does these steps: 1. Scenario: Identifying Users in Application Control Logs The ACME organization wants to use Identity Awareness to monitor outbound application traffic and learn what their employees are doing. 2. See the R75 Application Control Administration Guide (http://supportcontent. The SmartView Tracker and SmartEvent logs will then show identity information for the traffic. Installs the policy. To do this. In SmartView Tracker logs and SmartEvent events. This SmartView Tracker log entry shows that the system maps the source IP address with the user's identity. the IT administrator must enable Application Control and Identity Awareness.

Identity Awareness Scenarios This SmartEvent Intro log entry shows details of an Application Control event with Identity Awareness user and machine identity. Getting Started With Identity Awareness Page 22 .

Double-click the gateway on which to enable Identity Awareness. Or From the Gateway Properties tree. You can use the wizard to configure one Security Gateway that uses the AD Query and Captive Portal for acquiring identities. Log in to SmartDashboard. Page 23 . On the General Properties page > Additional Features section. When you complete the wizard and install a policy. You cannot use the wizard to configure a multiple gateway environment or to configure client acquisition (another method for acquiring identities). You can use SmartView Tracker and SmartEvent to see the logs for user and machine identity. To enable Identity Awareness: 1. a wizard opens. the system is ready to monitor Identity Awareness. On the Identity Awareness page. The Identity Awareness Configuration wizard opens. expand the Check Point branch. 3. select Identity Awareness. select Enable Identity Awareness. select Identity Awareness. 4. From the Network Objects tree.Chapter 2 Configuring Identity Awareness In This Chapter Enabling Identity Awareness on the Security Gateway Creating Access Roles Using Identity Awareness in the Firewall Rule Base Using Identity Awareness in the Application Control Rule Base Configuring Captive Portal in SmartDashboard Configuring Identity Agents Configuring Identity Awareness for a Log Server 23 26 28 29 31 34 40 Enabling Identity Awareness on the Security Gateway When you enable Identity Awareness on a Security Gateway. 2.

Sends users to a Web page to acquire identities from unidentified users. SmartDashboard suggests this domain automatically. To view/edit the LDAP Account Unit object. 6. If it is necessary for AD Query to fetch data from other domain controllers. Note . If AD Query is not required to operate with some of the domain controllers. you must add them at a later time manually to the LDAP Servers list. the LDAP account unit that the system creates contains only the domain controller you set manually. These options set the methods for acquiring identities of managed and unmanaged assets. Click Next. go to the Firewall tab > Servers and OPSEC Applications tab in the objects tree > LDAP Account Unit. The LDAP Account Unit name syntax is: <domain name>_ _ AD Configuring Identity Awareness Page 24 . When SmartDashboard is part of the domain. See Choosing Identity Sources (on page 41). If you select this domain. Select one or both options.  AD Query .Lets the Security Gateway seamlessly identify Active Directory users and computers. delete them from the LDAP Servers list.Enabling Identity Awareness on the Security Gateway 5.We highly recommend that you go to the LDAP Account Unit and make sure that only necessary domain controllers are in the list. the system creates an LDAP Account Unit with all of the domain controllers in the organization's Active Directory. The Integration With Active Directory window opens.  Captive Portal . If you create a new domain.

The IP address selected by default is the <gateway's main IP address>/connect. Enter the Active Directory credentials and click Connect to verify the credentials.2/DLP Mobile Access Portal .ACME.2.Enabling Identity Awareness on the Security Gateway For example. From the Select an Active Directory list. If you selected to use Captive Portal and do not wish to configure Active Directory. 11. For Captive Portal standard credentials are sufficient.COM_ _ AD. 10. select I do not wish to configure Captive Portal at this time and click Next.2. For example:    Identity Awareness Captive Portal . where unidentified users will be directed. you need to enter a domain name.2.2. All IP addresses configured for the gateway show in the list.2. Click Next. If you have not set up Active Directory.1/connect DLP Portal .2/sslvpn Configuring Identity Awareness Page 25 . Important . select the Active Directory to configure from the list that shows configured LDAP account units or create a new domain. 7.10. CORP.10. the Captive Portal Settings page opens. In the Captive Portal Settings page. password and domain controller credentials.2. 8. If you selected Captive Portal on the first page.20. 9. The same IP address can be used for other portals with different paths.For AD Query you must enter domain administrator credentials. select a URL for the portal. username.

machines and network locations as one object. To create an access role: 1. Click Finish. 13. Configuring Identity Awareness Page 26 . the portal is accessible only through internal interfaces. We do not recommend that you make the portal accessible through external interfaces on a perimeter gateway. The Access Role window opens. CORP. click Access Roles > New Access Role. To view/edit the LDAP Account Unit object. When you set an Active Directory domain. use these access role objects in the Rule Base. user groups or user branches.COM_ _ AD. Active Directory and / or Captive Portal become active. Results of the Wizard These are the results of the wizard:   Depending on the acquisition methods you set.ACME. You can select specific users. The LDAP Account Unit name syntax is: <domain name>_ _ AD For example. To enforce Identity Awareness. Select Policy > Install from the SmartDashboard menu. go to the Firewall tab > Servers and OPSEC Applications tab in the objects tree > LDAP Account Unit. 14. Access role objects define users. The access role can be specified for a certain user. Creating Access Roles After you activate Identity Awareness. 15. click Edit. you can create access role objects. The Identity Awareness is Now Active page opens.Creating Access Roles 12. the system creates an LDAP Account Unit object for the Active Directory domain. By default. To change this. network and machine or be general for a certain user from any network or any machine. Click Next to complete the wizard and see what is configured. From the Users and Administrators tree.

Specific users -click .click and select a network. In the Machines tab. In the Machines tab. 3. Select a Color for the object (optional). 8. Configuring Identity Awareness Page 27 . The access role is added to the Users and Administrators tree. In the Networks tab. select one of these:    Any user All identified users .includes machines identified by a supported authentication method (Active Directory or LDAP machines). A window opens. 7. A window opens. 6. 4. select one of these:   Any network Specific networks . Your selection is shown under the Networks node in the Role Preview pane. In the Users tab. Enter a Name and Comment (optional) for the access role. 5. select Enforce IP spoofing protection (requires full identity agent) if you want to enable the packet tagging feature. You can search for Active Directory entries or select them from the list. Active Directory users or LDAP users). Click OK.click .includes any user identified by a supported authentication method (internal SmartDashboard users. Specific machines. You can search for Active Directory entries or select them from the list. select one of these:    Any machine All identified machines . Your selections are shown in the Users node in the Role Preview pane. Your selections are shown in the Machines node in the Role Preview pane.Creating Access Roles 2.

The connection is http. In a rule that uses an access role in the Source column. When identity data for an IP is unknown and: To redirect http traffic to the Captive Portal: 1. All the rule’s fields match besides the source field with an access role. the rule is applied and the traffic is accepted/dropped based on the action. it can examine the rule for the next connection. If the source identity is known. the gateway allows access to the Configuring Identity Awareness Page 28 . Note: redirection will not occur if the source IP is already mapped to a user checkbox. make sure to place the rule in the correct position in the Rule Base to avoid unwanted behavior. If this property is added. 1 Source Finance_Dept (Access Role) Admin_IP Any Destination Service Action Accept (redirect to Captive Portal) Accept Drop Finance_Web_ Any Server Any Any Any Any 2 3 Example 1 . Important . the user is redirected to the Captive Portal. In rules with access roles. The action is set to redirect to the Captive Portal. If it does not match an access role. Note . Click OK. In rules with access role objects.If an unidentified Finance Dept user tries to access the Finance Web Server with http. If not all conditions apply. criteria matching operates like this:  When identity data for an IP is known:       If it matches an access role. there is no match and the next rule is examined. the traffic is redirected to the Captive Portal to get credentials and see if there is a match. The Action column shows that a redirect to the Captive Portal occurs. After the system gets the credentials from the Captive Portal. If there is no match. right-click the Action column and select Edit Properties. The Action Properties window opens.When you set the option to redirect http traffic from unidentified IP addresses to the Captive Portal. it goes on to examine the next rule. 2. Select the Redirect http connections to an authentication (captive) portal. Below is an example of a Firewall Rule Base that describes how matching operates: No. a redirect to the Captive Portal occurs. you can add a property in the Action field to redirect traffic to the Captive Portal. If all the conditions apply. After the user enters credentials. it examines the packet against the first rule in the Rule Base. it then goes on to the second rule and continues until it matches a rule. When a Security Gateway receives a packet from a connection. when the source identity is unknown and traffic is HTTP. 3.You can only redirect http traffic to the Captive Portal. the Action in the rule (Allow or Block) is enforced immediately and the user is not sent to the Captive Portal.Using Identity Awareness in the Firewall Rule Base Using Identity Awareness in the Firewall Rule Base The Security Gateway examines packets and applies rules in a sequential manner.

If it does not match an access role. After the system gets the credentials from the Captive Portal. you can add a property in the Action field to redirect traffic to the Captive Portal.If an unidentified administrator tries to access the Finance Web Server with http. If no rule matches. let's say that the below rule is positioned above the Any. To prevent access to unidentified users. rule number 2 matches. If there is no match. If the source identity is known. In rules with access role objects. it can examine the rule for the next connection. The rule means that everyone (including unidentified users) can access the Intranet Web Server except for temporary employees. For example. it goes on to the second rule and continues until it completes the Rule Base. it examines the packet against the first rule in the Rule Base. a rule that allows file sharing between the IT department and the Sales department. the user is redirected to the Captive Portal. a redirect to the Captive Portal occurs despite rule number 2. Drop rule. Access is allowed based on rule number 1. If this property is added. In rules with access roles. When the object is an access role. Configuring Identity Awareness Page 29 . add another rule that ensures that only identified employees will be allowed access and that attempts by a temporary employee will be dropped. it goes on to examine the next rule. criteria matching operates like this:  When identity data for an IP is known:   If it matches an access role. which identifies the user through the Captive Portal as belonging to the Finance Dept access role. To let the administrator access the Finance Web Server without redirection to the Captive Portal. When you negate an access role.Using Identity Awareness in the Application Control Rule Base Finance Web Server. the packet is allowed. she will have access to the Intranet Web Server. If a temporary employee is not identified when she accesses the system. After the administrator is identified. Any. For example. switch the order of rules 1 and 2 or add a network restriction to the access role. Using Identity Awareness in the Application Control Rule Base The Security Gateway inspects Application Control requests and applies rules in a sequential manner. the Action in the rule (Allow or Block) is enforced immediately and the user is not sent to the Captive Portal. it means that a given rule applies to all sources/destinations of the request except for the specified source/destination object. when the source identity is unknown and traffic is HTTP. Access Role Objects Access Role objects can be used as a source and/or destination parameter in a rule. When a Security Gateway receives a packet from a connection. Negate and Drop When you negate a source or destination parameter. it means that the rule is applied to "all except for" the access role and unidentified entities. this includes all unidentified entities as well. the rule is applied and the traffic is allowed/blocked based on the action. Example 2 .

but not the Source column. Example 3 . The Action column shows that a redirect to the Captive Portal occurs. 2. Click OK. the traffic is redirected to the Captive Portal to get credentials and see if there is a match. This happens because the action is set to redirect to the Captive Portal. Because the application is not HTTP. This means you cannot have a rule that uses an access role in both the Source column and the Destination column. the user is granted access to Gmail. Example 2 . Furthermore. In rule 3 there is also no match because the action is not set to redirect to the Captive Portal. the user is granted access according to rule number 1.An unidentified Finance user that attempts to access Salesforce is sent to the Captive Portal.An unidentified user that attempts to access the Remote Administration Tool matches rule 2. different users experience different outcomes: Example 1 . you cannot use access roles in both the Source and Destination columns in the same Rule Base. Below is an example of an Application Control Rule Base that shows how criteria matching operates: No. The connection protocol is HTTP. there is no match and the next rule is examined. traffic cannot be redirected to the Captive Portal. To redirect HTTP traffic to the Captive Portal: 1. Source and Destination Fields These issues are related to Source and Destination fields:  You can use access role objects in the Source column or the Destination column of a rule.  Configuring Identity Awareness Page 30 . In a rule that uses an access role in the Source column. you can use a network object together with an access role object. Since none of the rules match. 3. right-click the Action column and select Edit Properties.Using Identity Awareness in the Application Control Rule Base  When identity data for an IP is unknown and:    All the rule’s fields match besides the source field with an access role. the user is granted access to the Remote Administration Tool. But the condition between them is "or" and not "and".An unidentified user that browses to Gmail does not match rules 1 and 2 because of the application. If not all conditions apply. Select Redirect HTTP connections.  When the criteria does not match any of the rules in the Rule Base:  The traffic is allowed. Since none of the rules match. In the Source and Destination columns. If all the conditions apply. The action is set to redirect to the Captive Portal. The Action Properties window opens. 1 Source Finance_Dept (Access Role) Destination Service Application Internet Any Salesforce Action Allow (redirect to Captive Portal) 2 Any_identified_user Internet (Access Role) Any Remote Allow Administration Tool (nonHTTP category) Any recognized Block 3 Any_identified_user Internet (Access Role) Any When browsing the Internet. After entering credentials and being identified.

2. Configuring Captive Portal in SmartDashboard In the Identity Sources section of the Identity Awareness page. ID. It is allowed. This rule makes sure that only identified users will be allowed access and attempts by unidentified users will be blocked.The primary URL that users are redirected to for the Captive Portal. Access Settings Click Edit to open the Portal Access Settings window. when you use negate on an access role you allow all unidentified users and anyone who is not the access role access. This example shows rules that block temporary employees from accessing the Internet and allows access for identified employees. To make the alias work. A more advanced deployment is possible where the portal runs on a different gateway. it must be resolved to the main URL on your DNS server. The default is that the Captive Portal is on the gateway. configure:       Portal Network Location Access Settings Authentication Settings Customize Appearance Users Access Agent Deployment from the Portal Portal Network Location Select if the portal runs on this gateway or a different Identity Awareness enabled gateway. In this window you can configure:   Main URL . To prevent this you must include an access role that prevents access to unidentified users. Aliases . select Captive Portal to send unidentified users to the Captive Portal. if a connection does not match any of the rules. Configuring Identity Awareness Page 31 . For example.Configuring Captive Portal in SmartDashboard Negate and Block Negate and block in the Application Control Rule Base operates similarly to Negate and drop (on page 29) in the Firewall Rule Base. The gateway thus redirects unidentified users to the portal on the same gateway. From the Portal Settings window. This is the basic configuration. Unlike the Firewall Rule Base. See the Deployment section for more details.yourcompany. it is not automatically blocked. You might have already configured this in the Identity Awareness Wizard. Thus.Click the Aliases button to Add URL aliases that are redirected to the main portal URL. To configure the Captive Portal settings: 1. Select Captive Portal and click Settings. If you already configured the portal in the Identity Awareness Wizard or SmartDashboard. its URL shows below Captive Portal.com can send users to the Captive Portal.

Users are sent to the Captive Portal if they use networks connected to these interfaces.   Through all interfaces Through internal interfaces  Including undefined internal interfaces  Including DMZ internal interfaces According to the Firewall policy . You might have already configured this in the Identity Awareness Wizard. Accessibility . Either:  Any . See Server Certificates (on page 54) for more details. RADIUS .   Authentication Settings Click Settings to open the Authentication Settings window.Select one method that known users must use to authenticate.The directory of internal users.Users from all LDAP servers. Customize Appearance Click Edit to open the Portal Customization window and edit the images that users see in the Captive Portal.   Internal users .Click Import to import a certificate for the portal website to use. The options are based on the topology configured for the gateway. External user profiles . Configuring Identity Awareness Page 32 .Users from an LDAP server that you select.Configuring Captive Portal in SmartDashboard  Certificate .A configured RADIUS server. In this window you can configure:  Authentication Method .The directory of users who have external user profiles. Configure the labeled elements of the image below.Select one or more places where the gateway searches to find users when they try to authenticate. LDAP users .Click Edit to select from where the portal can be accessed. Users with identical user names must log in with domain\user.    User name and password .  The default is that all user directory options are selected. If you do not import a certificate. Select the server from the list.  Specific . You might choose only one or two options if users are only from a specified directory or directories and you want to maximize gateway performance when users authenticate. the portal uses a Check Point auto-generated certificate.This can be configured internally or on an LDAP server. This might cause browser warnings if the browser does not recognize Check Point as a trusted Certificate Authority. User Directories .The directory of LDAP users.Select this if there is a rule that states who can access the portal.

You can add user groups and give them settings that are different from other users. The options that you configure per user group are:   If they must accept a user agreement.Makes users sign a user agreement.Select this to use the standard agreement.Let guests who are not known by the gateway access the network after they enter required data.You can require that users sign a user agreement. Settings specified for a user group here override settings configured elsewhere in the Portal Settings. Name and Password Login Settings Click Settings to configure settings for known users after they enter their usernames and passwords successfully.   Access will be granted for xxx minutes . This name is used in the agreement. You can only configure settings about Identity Agent deployment if Identity Agent is selected on the Identity Awareness page. Ask for user agreement .Edit the table shown until it contains the fields that users complete in that sequence. Select Is Mandatory for each field that guests must complete before they can get access to the Configuring Identity Awareness Page 33 . If they must download the Identity Agent and which one. Click Edit to upload an agreement.   Login Fields .Users are prompted to enter an existing username and password.   Name and password login. Select Use my company logo for mobiles and Browse to select a smaller logo image for users who access the portal from mobile devices. This will only let known users authenticate. The default title is Network Access Login. Unregistered guests login . This option is not selected by default because a user agreement is not usually necessary for known users. Unregistered Guest Login Settings Click Settings to configure settings for guests. You can use HTML code. Adjust portal settings for specific user groups . 2 Company Logo 2 Company Logo for mobiles User Access Configure what users can do in the Captive Portal to become identified and access the network.   If they can defer the Identity Agent installation and until when. Select Use my company logo and Browse to select a logo image for the portal. See the text in the Agreement preview. Replace Company Name with the name of your company.For how long can they access network resources before they have to authenticate again. Select an agreement to use:  Default agreement with this company name .Configuring Captive Portal in SmartDashboard Label Number 1 Name Portal Title To do in GUI Enter the title of the portal.Paste the text of a customized agreement into the text box. Ask for user agreement . Click Edit to choose an agreement and the End-user Agreement Settings page opens. Customized agreement .   Access will be granted for xxx minutes .For how long can they access network resources before they have to authenticate again.

Select this if you want to give users flexibility to choose when they install the Identity Agent.To install the Full Identity Agent the computer must have administrator permissions. see Prepackaging Identity Agents (on page 77). enter it in the empty field and then click Add. the Identity Agent must discover and trust the server that it connects to.Full Identity Agent . For more information.  Require users to download .a customized installation package. Use the green arrows to change the sequence of the fields. Light Identity Agent or Custom Identity Agent.Select this to make users install the Identity Agent.You can deploy the Identity Agent for installation through the Captive Portal or use other means you use to deploy software in your organization. Agent Deployment from the Portal If Identity Agents is selected as a method to acquire identities. users enter credentials in another window. You can configure one of five methods. you must think about these elements:  Identity Agent type . For the Full Identity Agent you can enforce IP spoofing protection. an inherent authentication and authorization protocol in Windows networks that is available by default on all Windows servers and workstations. The system securely gets authentication data one time without making users authenticate manually (as is necessary with Captive Portal). Installation permissions . To add a new field. For the Full Identity Agent you can also manage asset detection if you define machines in access roles. It is not necessary to have administrator permissions to install the Light Identity Agent. You get SSO with Kerberos. Until that date a Skip Identity Agent installation option shows in the Captive Portal. The Identity Agent identity source uses SSO to authenticate users when they enter their login credentials (Active Directory or other authentication server). If you do not use SSO. see Kerberos SSO Configuration (on page 71). Configuring Identity Agents Identity Agents are dedicated client agents installed on users' computers that acquire and report identities to the Security Gateway.Identity Agents installed on endpoint computers authenticate users automatically when they log in to the domain using SSO. Select which Identity Agent they must install. you can configure that users must download the Identity Agent from the Captive Portal. Configuring Identity Awareness Page 34 . You can also let users choose not to install the Identity Agent immediately and instead wait until a specified later date.Light Identity Agent .Custom . Automatic authentication using Single Sign-On (SSO) . Before you configure Identity Agents. The first field will show in the SmartView Tracker logs. The Custom Identity Agent is a customized installation package. All necessary configuration is done by administrators and does not require user input. users will only be able to access the network if they install the identity agent. If this option is selected and the defer option is not selected.  Users may defer installation until .Before the Identity Agent can connect to a Security Gateway with Identity Awareness. Installation deployment methods.Configuring Identity Agents network.Full Identity Agent. To set up Kerberos. Server discovery and trust .    Identity Agent Types There are 3 Identity Agent types that you can install:    Identity Agent . Select the date by which they must install it.

The system opens a window for entering credentials.Users that log in to the Active Directory domain are transparently authenticated (with SSO) and identified when using an Identity Agent. It is also possible to poison ARP tables that let users do ARP "man-in-the-middle attacks" that keep a continuous spoofed connectivity status. the Identity Agent automatically detects the change. This is done by a joint effort between the Identity Agent and the Security Gateway that uses a unique technology that sign packets with a shared key. Machine identification . Packet tagging . Configuring Identity Awareness Page 35 .You get machine identification when you use the Full Agent as it requires installing a service. Packet Tagging for Anti-Spoofing IP Spoofing happens when an unauthorized user assigns an IP address of an authenticated user to an endpoint computer.A technology that prevents IP spoofing is available only for the Full Agent as it requires installing a driver. This table shows the similarities and differences of the Identity Agent types. the Identity Agent uses username and password authentication with a standard LDAP server. the user bypasses identity access enforcement rules. Packet Tagging is a patent pending technology that prevents spoofed connections from passing through the gateway.Configuring Identity Agents User identification . The Identity Agent tells the Security Gateway and you stay connected. If you do not configure SSO or you disable it. To protect packets from IP spoofing attempts. IP change detection .When an endpoint IP address changes (interface roaming or DHCP assigns a new address). Identity Agent Light Identity Agent Full Installation Elements Agent format Resident application Resident application + service + driver Administrator Installation permissions Upgrade permissions Security Features User identification Machine identification IP change detection Packet tagging None None None SSO No SSO Yes Yes Yes No Yes The installation file size is 7MB for both types and the installation takes less than a minute. you can enable Packet Tagging. By doing so.

The Success status indicates that a successful key exchange happened. 3. Configuring Identity Awareness Page 36 . Note . select Enforce IP spoofing protection (requires full identity agent).Configuring Identity Agents The Identity Awareness view in SmartView Tracker shows Packet Tagging logs. During installation. To enable IP Spoofing protection: 1. the Identity Agent automatically knows if there are administrator permissions on the computer or not and installs itself accordingly.Packet Tagging can only be set on computers installed with the Full Identity Agent.When you deploy the Full Identity Agent it is necessary for the user that installs the client to have administrator rights on the computer. Click OK. Identity Agent Deployment Methods There are 2 Identity Agent deployment methods:  Using Captive Portal . Create an Access Role ("Creating Access Roles" on page 26). In the Machines tab. You can also let users choose not to install the Identity Agent immediately and instead wait until a specified later date. the Light Identity Agent is installed instead. 4.you can configure that users must download the Identity Agent from the Captive Portal. If the user does not have administrator permissions. Make sure users have the full Identity Agent installed. 2. Note .

Until that date a Skip Identity Agent installation option shows in the Captive Portal. select the Enable Identity Agent checkbox. To give users flexibility to choose when they install the Identity Agent. From the Identity Awareness page. The options that you configure for each user group are:   If they must accept a user agreement.in /linux/windows/Check_Point_Custom_Nac_Client. From the Portal Settings window. Select Name and password login and click Settings. an attempt to launch a Man-in-the-middle attack. 3. 3. Select Captive Portal and click Settings. The msi installation files (Light and Full) can be found in the \linux\windows directory on the supplied DVD. Trust is verified by comparing the server fingerprint calculated during the SSL handshake with the expected fingerprint. 4.msi For more information. Settings specified for a user group here override settings configured elsewhere in the Portal Settings.in /opt/CPNacPortal/htdocs/nac/nacclients/customAgent. 5. Select Captive Portal and click Settings. select the Require users to download checkbox to make users install the Identity Agent. Click OK. Select which Identity Agent they must install.  If they can defer the Identity Agent installation and until when. 4. Server Discovery and Trust Server Discovery refers to the procedure the Identity Agent uses to find which Security Gateway with Identity Awareness to connect to. 5. if you have a group of mobile users that roam and it is necessary for them to stay connected as they move between networks. There are several methods you can use to configure this. users will can only access the network if they install the Identity Agent. The most basic method is to configure one server. Server Trust refers to the procedure that:   Makes sure that the Identity Agent connects to a genuine Security Gateway with Identity Awareness. select Users may defer installation until. 2.Configuring Identity Agents  Using distribution software . Another method is to deploy a domain wide policy of connecting to a Security Gateway with Identity Awareness based on the Identity Agent client's current location. From the Identity Awareness page. 2. Makes sure that the communication between the Identity Agent and the Security Gateway with Identity Awareness is not being tampered with. Select Adjust portal settings for specific user groups . Select the date by which they must install it. see Prepackaging Identity Agents (on page 77).msi Secure Platform installation CD . select the Enable Identity Agent checkbox. If you select this option and you do not select the defer option. You can find a customizable msi version of the Identity Agent (for distribution via a software distribution tool) in these places:   Installed Security Gateway . For example. you can configure specific groups to download the Identity Agent. Click OK.you can deploy the Identity Agent with distribution software. If they must download the Identity Agent and which one. For example. Configuring Agent Deployment for User Groups When necessary. To configure Identity Agent deployment for user groups: 1. Configuring Agent Deployment from Captive Portal To configure Identity Agent deployment from Captive Portal: 1. There are 5 server discovery and trust methods: Configuring Identity Awareness Page 37 .You can add user groups and give them settings that are different from other users.

The options are based on the topology configured for the gateway. you can deploy the server addresses and trust data using a dedicated "Distributed Configuration" tool. During installation. From the Identity Agents Settings window.Configuring Identity Agents  File name based server configuration . Users can communicate with the servers if they use networks connected to these interfaces. PrePackaging – You can create a prepackaged version of the client installation that comes with the Security Gateway with Identity Awareness IP and trust data. see Server Discovery and Server Trust ("Server Discovery and Trust" on page 83). users will have to manually trust the server (a trust window opens). To configure the Identity Agent settings: 1. any Identity Agent downloaded from the Captive Portal is renamed to include the Captive Portal machine IP address in it. You can deploy these values before installing the client (by GPO. configure:     Agent Access Authentication Settings Session details Agent Upgrades Agent Access Click Edit to select from where the Identity Agent can be accessed. This includes the Identity Server addresses and trust data. AD based configuration – If the Identity Agent computers are members of an Active Directory domain.   DNS SRV record based server discovery – You can configure the Security Gateway with Identity Awareness addresses in the DNS server. Configuring Identity Awareness Page 38 . 2. select Identity Agents to configure Identity Agent settings.   For more details. or any other method that lets you control the registry remotely). Remote registry – All client configuration resides in the registry. users will have to manually trust the server (a trust window opens). the Identity Agent uses this IP for the Security Gateway with Identity Awareness. The Identity Agent can then use them immediately.If no other method is configured (out of the box situation). Select Identity Agents and click Settings. Because DNS is not secure. When you use this method. Configuring Identity Agents in SmartDashboard In the Identity Sources section of the Identity Awareness page.

the system will only upgrade versions that are no longer compatible.The directory of LDAP users.  Specific . The keepalive is used as the server assumes the user logged out if it is not sent. You might choose only one or two options if users are only from a specified directory or directories and you want to maximize gateway performance when users authenticate.  Agents send keepalive every X minutes .Select one method that known users must use to authenticate.Users from an LDAP server that you select. Lower values affect bandwidth and network performance. Installed Agents Versions . External user profiles . In this window you can configure:  Authentication Method .      Check agent upgrades for . you can let users save the passwords they enter in the Identity Agent login window.Users from all LDAP servers. Allow user to save password . Select the server from the list.The directory of internal users. Configuring Identity Awareness Page 39 . User Directories .    User name and password .the Identity Agent is automatically updated in the background without asking the user for upgrade confirmation.   Internal users .  The default is that all user directory options are selected. Authentication Settings Click Settings to open the Authentication Settings window. Upgrade agents silently (without user intervention) . Either:  Any . LDAP users .click the button to show the Identity Agent versions installed in the system. Users should reauthenticate every XXX minutes .The interval at which the Identity Agent sends a keepalive signal to the Security Gateway.A configured RADIUS server.For how long can users access network resources before they have to authenticate again. Upgrade only non-compatible versions .Select one or more places where the gateway searches to find users when they try to authenticate.the Identity Agent is accessible through interfaces associated with source networks that appear in access rules used in the Firewall policy.Configuring Identity Agents   Through all interfaces Through internal interfaces   Including undefined internal interfaces Including DMZ internal interfaces  According to the Firewall policy .When SSO is not enabled. Session Configure data for the logged in session using the Identity Agent. RADIUS . Keep agent settings after upgrade . Users with identical user names must log in with domain\user.   Agent Upgrades Configure data for Identity Agent upgrades.This can be configured internally or on an LDAP server. When using SSO.settings made by users before the upgrade are saved.You can select all users or select specific user groups that should be checked for agent upgrades.The directory of users who have external user profiles. this is irrelevant.

To view/edit the LDAP Account Unit object. you must add them at a later time manually to the LDAP Servers list. the server gets the user and machine name from the association map entry that corresponds to the source IP address. select Add Identity to logs received from non-identity aware gateways. password and domain controller credentials. Configuring Identity Awareness Page 40 .For AD Query you must enter domain administrator credentials. select the Active Directory to configure from the list that shows configured LDAP account units or create a new domain.COM_ _ AD. Enter the Active Directory credentials and click Connect to verify the credentials. If AD Query is not required to operate with some of the domain controllers. The Identity Awareness Configuration wizard opens. Get the Active Directory administrator's credentials. If you select this domain. When SmartDashboard is part of the domain. go to the Firewall tab > Servers and OPSEC Applications tab in the objects tree > LDAP Account Unit. SmartDashboard suggests this domain automatically. username. The Integration With Active Directory window opens. the system creates an LDAP Account Unit with all of the domain controllers in the organization's Active Directory. 5. Log in to SmartDashboard. you are incorporating user and machine identification into Check Point logs. To enable Identity Awareness on the Log Server: 1. right-click Check Point and select the gateway with the Log Server. If you have not set up Active Directory. On the Identity Awareness page. From the Network Objects tree. From the Select an Active Directory list. the LDAP account unit that the system creates contains only the domain controller you set manually. If you create a new domain. Click Finish. Click Next. The LDAP Account Unit name syntax is: <domain name>_ _ AD For example. CORP.We highly recommend that you go to the LDAP Account Unit and make sure that only necessary domain controllers are in the list. It then adds this identity aware information to the log. If it is necessary for AD Query to fetch data from other domain controllers. Enabling Identity Awareness on the Log Server Before you enable Identity Awareness on the Log Server:   Make sure there is network connectivity between the Log Server and the domain controller of your Active Directory environment. you need to enter a domain name. Note . select Identity Awareness. 7.ACME. 2. The data extracted from AD is stored in an association map on the Log Server. When Security Gateways generate a Check Point log entry and send it to the Log Server. Important . With Identity Awareness administrators can analyze network traffic and security-related events better. 4. delete them from the LDAP Servers list. From the Gateway Properties tree. The Log Server communicates with Active Directory servers and gets user and machine names along with the source IP address information from AD event logs.Configuring Identity Awareness for a Log Server Configuring Identity Awareness for a Log Server When you configure Identity Awareness for a Log Server. 3. 6.

you can choose to set them separately or as combinations that supplement each other. Note . IP spoofing protection can be set to prevent packets from being IP spoofed. This automatically creates an LDAP Account Unit.these are some identity source options:  AD Query and Captive Portal . For logging and auditing only . The Captive Portal identity source is necessary to include all non-Windows users. Users that are not identified encounter redirects to the Captive Portal.set the AD Query and Captive Portal identity sources. Page 41 . You cannot add domain controllers from two different subdomains into the same account unit. This section presents some examples of how to choose identity sources for different organizational requirements. The AD Query finds all AD users and machines.enable Identity Awareness on the gateway and select AD Query as the identity source.  Identity Agents and Captive Portal .e. For Application Control .  Advanced AD Query Configuration Configuring Identity Awareness for a Domain Forest (Subdomains) You need to create a separate LDAP Account Unit for each domain in the forest (i.Chapter 3 Identity Sources In This Chapter Choosing Identity Sources Advanced AD Query Configuration Advanced Captive Portal Configuration Advanced Identity Agents Configuration 41 41 49 56 Choosing Identity Sources Identity sources are different in terms of security and deployment considerations. You can use the Identity Awareness Configuration Wizard to define one of the subdomains.    For logging and auditing with basic enforcement . It also serves as a fallback option if AD Query cannot identify a user. but you then must make additional changes as listed below in the LDAP Account Unit. You must manually create all other domains you want Identity Awareness to relate to from Servers and OPSEC Applications > Servers > New > LDAP Account Unit. The Captive Portal is used for distributing the Identity Agent. Depending on your organization's requirements.You can add Identity Agents if you have mobile users and also have users that are not identified by AD Query. subdomain).select the Add identity to logs option on the Identity Awareness page.When a high level of security is necessary. For Data Center protection .When most users are desktop users (not remote users) and easy deployment is important.

Make sure the username is one of these:   A Domain administrator account that is a member of the Domain Admins group in the subdomain. For example.DC=DOMAIN_NAME.COM. When AD Query is enabled on Security Gateways. In Objects Management tab > Branches in use . then for the Enterprise administrator John_Doe enter in the Username field: ACME. If you use an Enterprise administrator.COM\John_Doe Note . enter the administrator's name as domain\user. Identity Sources Page 42 . 2.DC=local Specifying Domain Controllers per Security Gateway An organization's Active Directory may have several sites. you may want to configure each Security Gateway to communicate with only some of the domain controllers.DC=ACME. if the domain is ACME.COM and the subdomain is SUB.add the login DN. An Enterprise administrator account that is a member of the Enterprise Admins group in the domain.DC=DOMAIN_SUFFIX to DC=SUB_DOMAIN_NAME. This is configured in the SmartDirectory (LDAP) page of the Gateway Properties. When all of the domain controllers belong to the same Active Directory. where each site has its own domain controllers that are protected by a Security Gateway. change DC=ACME. 3. In LDAP Server Properties tab > Add > Login DN .Advanced AD Query Configuration When you create an LDAP Account Unit for each domain in the forest. note the instructions for these fields: 1. in the LDAP Account Unit go to LDAP Server Properties tab > Add > Username. For each domain controller that is to be ignored.DC=DOMAIN_SUFFIX. the default priority of the Account Unit must be set to a value higher than 1000. For example.DC=local to DC=SUB.In the wizard this is the Username field.Edit the base DN from DC=DOMAIN_NAME. a single LDAP Account Unit is created in SmartDashboard.ACME.

2. let's say that the LDAP Account Unit ad. select SmartDirectory (LDAP). 4. From the Gateway Properties tree.mycompany. right-click Check Point and select the Security Gateway. Create an environment variable named CP_SHOW_SMARTDIRECTORY=0 on the computer that runs SmartDashboard. To specify domain controllers per Security Gateway: 1. Log in to SmartDashboard. On the Security Gateway we want to enable AD Query only for domain controllers dc2 and dc3. 3. Click Selected Account Units list and click Add. From the Network Objects tree. This means that all other domain controllers must be set to a priority higher than 1000 in the gateway properties. Identity Sources Page 43 . 5.Advanced AD Query Configuration For example.com has 5 domain controllers.

Advanced AD Query Configuration 6. Select your Account Unit. 7. dc4 and dc5. Clear the Use default priorities checkbox and set the priority 1001 to dc1. Identity Sources Page 44 .

Identity Sources Page 45 . when a Helpdesk administrator logs on to install a program for a user. Install policy. The CLI command is adlog a dc. a user sitting at the same computer with the same IP address originally authenticated. Checking the Status of Domain Controllers You can make sure that the domain controllers are set properly by using the adlog CLI. To prevent this you can exclude irrelevant accounts ("Excluding Users" on page 46) from being logged. User B will then only have his permissions and not user A's permissions. you can increase the default time (Check Point Gateway Properties > Identity Awareness > Active Directory Query Settings). You can see the domain controllers that the Security Gateway is set to communicate with as well as the domain controllers it ignores. users access resources every 30 minutes that create authentication requests. The system receives a security event log when a user or machine accesses a network resource. For example. if user A logs out before the timeout and user B logs in. a user logs in. Before you can make this assumption. or shares a network drive. For example. If the user does not access an Intranet resource that requires authentication after logging in. Permissions and Timeout AD Query is based on querying the Active Directory Security Event Logs and extracting the user and machine mapping to the network address from them. it is necessary to exclude any service accounts used by user computers. AD Query does not distinguish between application service accounts on a user's machine and the actual user's account.). backup. For example. 9. Multiple accounts can be connected to the same IP address. the user gets the Captive Portal for authentication purposes (if Captive Portal is set). etc.   Single User Assumption A solution for multiple accounts logging in with the same IP address is to assume that only one user is connected to each computer. you can exclude "dummy" user names used for automatic actions or services running on endpoint computers (anti-virus. For example.Advanced AD Query Configuration 8. permissions are no longer applicable. On average. unlocks a screen. Notifications are not sent when a user logs out as the Active Directory is not aware of this. To prevent this you must first filter service accounts and then enable single user assumption. When the administrator logs out. When using AD Query you must be aware of its limitations:  When the defined timeout passes (12 hours by default). When this happens. Click OK. Resulting logs show that multiple accounts are logged in on the same IP. For example. user B will be considered the user connected to the computer. usually this is not a problem. If necessary. This happens because IP permissions are kept until the timeout value passes and Identity Awareness does not detect user logs out. the user will no longer have permissions after the timeout period. the user will get the Helpdesk administrator's permissions plus his own permissions until the timeout.

You do not need to set this attribute when Identity Awareness is enabled on the Security Management Server or Log Server. 3. You can use the * and ? wildcard characters to specify multiple users in a list entry. The observed bandwidth range varies between 0. All other gateways to get identities from the gateway that acquires identities from the given domain controller. Click Add. Excluding Users You can distinguish between application service accounts on a user's machine and the actual user's account by excluding the service accounts. the AD server can become overloaded with WMI queries. Set these options on the Identity Awareness page:   One gateway to share identities with other gateways. 2. If more than one gateway gets identities from the same AD server. Identity Sources Page 46 . To set single user assumption: 1. you must set an attribute. These service accounts are used for automatic actions or services running on endpoint computers (anti-virus.Another way to keep these issues to a minimum is to increase DHCP lease time. See the Deployment Scenarios (on page 62) section for more details. The generated events include event logs and authentication events. 2. 4. Select Assume that only one user is connected per computer. The amounts vary according to the applications running in the network. select Settings for Active Directory Query. Exclude any service accounts. we recommend that you set only one gateway to acquire identities from a given Active Directory domain controller per physical site. Use dbedit or GuiDBEdit tools to set the SupportUnicode attribute to true on the LDAP Account Unit object. Click OK. 3. See Excluding Users (on page 46). Click Advanced. Performance Bandwidth between the Log server and Active Directory Domain Controllers The amount of data transferred between the Log server and domain controllers depends on the amount of events generated. This is the gateway that gets identities from a given domain controller. From the Identity Awareness page. Click OK. In the Excluded Users / Machines section. Programs that have many authentication requests result in a larger amount of logs. To distinguish between application server accounts and a user's account: 1.). From the Identity Awareness page.1 to 0. backup. You can also enter any regular expression via the syntax regexp:<regular expression>. Multiple Gateway Environments In environments that use multiple gateways and AD Query. If you do not exclude them. The LDAP Account Unit object is found in the Servers table. etc. 5. they show up multiple times in logs. select Settings for Active Directory Query. type the name or name pattern of the Active Directory accounts to ignore. 4.Advanced AD Query Configuration Note . Non-English Language Support To support non-English user names on a Security Gateway enabled with Identity Awareness.25 Mbps per each 1000 users.

3. 3. Ping the Security Gateway with Identity Awareness/log server from your domain controller.Advanced AD Query Configuration CPU Impact When using AD Query. 4. click Connect. enter the following information: a) Domain controller in the following format: \\<IP address>\root\cimv2 For example: \\11.exe in the Run window. If there are drops. Use wbemtest to Verify WMI To use the Microsoft wbemtest utility to verify that WMI is functional and accessible.22. In the Connect window.44\root\cimv2 b) Fully qualified AD user name. In the Windows Management Instrumentation Tester window. Perform standard network diagnostics as required. see Configuring the firewall (on page 48) and sk58881 (http://supportcontent. perform the following troubleshooting steps: In this section: Check Connectivity Use wbemtest to Verify WMI Confirm that Security Event Logs are Recorded Install Database for a Log Server 47 47 49 49 Check Connectivity 1. Ping the domain controller from the Security Gateway with Identity Awareness/log server.com\admin Identity Sources Page 47 . 1. For example: ad.com/solutions?id=sk58881). Check SmartView Tracker and see if there are drops between a Security Gateway defined with AD Query (Source) and the domain controller (Destination).checkpoint. 4.33. 2. Enter wbemtest. Click Start > Run. Troubleshooting If you experience connectivity problems between your domain controllers and Security Gateway with Identity Awareness/log servers. the impact on the domain controller's CPU is less than 3%.company. 2.

c) The domain controller IP is incorrect or you are experiencing connectivity issues. configure the Firewall to allow WMI traffic. enter your domain administrator user name and password. Obtain a domain administrator's credentials. For example: \\11. 3. Identity Sources Page 48 . If the domain controller root directory appears. 7.44\c$. Click Connect. In SmartDashboard > Firewall. Configuring the Firewall If a Security Gateway is located between the Security Gateway with Identity Awareness/log server and the Active Directory controller. this indicates that he is not defined as a domain administrator. Check Domain Administrator Credentials To verify your domain administrator credentials: 1.msc in the Run window. If the connection fails. 2. An error message may indicate that: a) If the user does not have sufficient privileges. check for the following conditions: a) Connectivity ("Check Connectivity" on page 47) problems b) Incorrect domain administrator credentials ("Check Domain Administrator Credentials" on page 48). b) You entered the incorrect user name or password.33. right-click this service and select Start from the option menu. To create firewall rules for WMI traffic: 1. Save the policy and install it on Security Gateways. this indicates that your domain administrator account has sufficient privileges. Verify the WMI Service To verify if the WMI service is running: 1. 6. Enter services. If the Windows Management Instrumentation Tester window re-appears with its buttons enabled. create a rule that allows ALL_DCE_RPC traffic:     Source = Security Gateways that run AD Query Destination = Domain Controllers Service = ALL_DCE_RPC Action = Accept 2. In the Logon window. If it has not started. WMI is fully functional. Check and retry. c) WMI service ("Verify the WMI Service" on page 48) is not running d) A firewall is blocking traffic ("Configuring the Firewall" on page 48) between the Security Gateway with Identity Awareness/log server and domain controller. 3. or you receive an error message. Click Start > Run.22. 2. Enter \\<domain controller IP>\c$ in the Run window. Click Start > Run. 4.Advanced AD Query Configuration c) Password 5. Locate the Windows Management Instrumentation service and verify that the service has started.

The Install Database window appears. 3. refer to Microsoft Active Directory documentation for instructions on how to configure these events. This includes changes to the text strings shown on the Captive Portal Network Login page. On the Security Gateway. If the domain controller does not generate these events. 4769.. you can set the Captive Portal to String ID Help Mode. but do not see identities in logs. This mode lets you view the string IDs used for the text captions. To help you understand what each string ID means. These language files are saved on the Security Gateway and cannot be upgraded.com/solutions?id=sk37453) for a solution.4624. Select Policy > Install Database.php Identity Sources Page 49 . Click Close when the script is complete. make sure you installed the database. 4770 Make sure you see the applicable events in the Event Viewer on the domain controller (My computer > Manage > Event Viewer > Security). open the file: /opt/CPNacPortal/phpincs/utils/L10N. see sk37453 (http://supportcontent. Confirm that Security Event Logs are Recorded If you have checked connectivity ("Check Connectivity" on page 47) but still do not see identity information in logs. The Install Database script appears.. AD Query reads these events from the Security Event log:   On Windows 2003 domain controllers . Select the machine(s) on which you would like to install the database and click OK. You can make changes to the default English language or edit files to show text strings in other languages. these files must be configured again. Setting Captive Portal to String ID Help Mode To set the Captive Portal to String ID Help mode: 1. 674 On Windows 2008 domain controllers . The changes are saved in the database and can be upgraded. To configure other languages to show text strings in a specified language on the Captive Portal. 4768. 2.672.Advanced Captive Portal Configuration Note . If you upgrade the Security Gateway..checkpoint. 673. you must configure language files. You can change English text that is shown on the Captive Portal to different English text through the SmartDashboard. Advanced Captive Portal Configuration Customizing Text Strings You can customize some aspects of the web interface. Install Database for a Log Server If you have configured Identity Awareness for a log server. make sure that the necessary event logs are being recorded to the Security Event Log. To install the database: 1.If there are connectivity issues on DCE RPC traffic after this policy is installed.

The Captive Portal opens showing the string IDs. 4. Identity Sources Page 50 . To revert to regular viewing mode. open the file L10N. 2. Replace the line // return $stringID. (delete the two backslashes that you see before the text return $stringID).php and put backslashes before the text return #stringID. Click Configure. See the highlighted text in step number 2 above. Changing Portal Text in SmartDashboard To change the text that shows in SmartDashboard: 1. 3. with return $stringID.Advanced Captive Portal Configuration 2. Reload the Captive Portal in your web browser. Go to Policy > Global Properties > SmartDashboard Customization.

Advanced Captive Portal Configuration 3. Identity Sources Page 51 . Delete the word DEFAULT and type the new English text in the required field. Go to Identity Awareness > Portal Texts. Install the policy. Click OK. 4. 5. 6.

Identity Sources Page 52 . English is the only language entry in the list.php 2. add an entry to the supported languages file: 1. To create a new language. 5. Save the files with UTF-8 encoding and move them to the correct location. By default. you must create an entry in the supported languages file and create a new language file. Set the language selection list to show on the Network Login page. Editing the Language Array The supported language file contains entries for languages that you can see in the list on the Captive Portal page. For example: "de_DE" => "German". 2. Use the English language file as a template to create new language files. 3. create a new locale entry with the syntax: "xx_XX" => "XName". After you set the language selection list. In the $arLanguages array. Open the file: /opt/CPNacPortal/phpincs/conf/L10N/supported_languages. For each new language. To configure a language for Captive Portal you must: 1.Advanced Captive Portal Configuration Adding a New Language You can configure the Captive Portal to show the Network Login pages in different languages. users can choose the language they prefer to log in with from a list at the bottom of the page. Then translate the strings in the new language file. Edit the language array for the new language locale. Make sure the text strings are shown correctly. 4. It has a corresponding language file.

2. use the English language file (portal_en_US. / &lt. When you translate a string.php 2.php) as a template and refer to it for the source language. 6. Rename it to the new language using the syntax portal_xx_XX. Back up the file (for possible future revert). portal_de_DE. Microsoft Word or a different editor to save the file with UTF-8 encoding. When you configure additional languages. Creating New Language Files To create new language files. Copy the English language file: /opt/CPNacPortal/phpincs/conf/L10N/portal_en_US. When using Microsoft Word.php. This is important to prevent breaks in the page layout. the language selection list does not show at the bottom of the Captive Portal Network Login page. open the file: /opt/CPNacPortal/phpincs/view/html/Authentication. It is not necessary to translate all strings.php 3. 3. If this is not possible. Use Notepad. Find the language_selection string which is part of <label for="language_selection">. Save the file. To save a file with UTF-8 encoding: 1. 4. Translate the strings in the copied file. replace the current file with the backup of the original file. The file contains the message strings. You cannot use HTML special character sequences such as &nbsp. consult with technical support.php 2. Captive Portal users can then select the language with which to log in. To see the language list on the Network Login page: 1. On the Security Gateway.txt' file with UTF-8 as the encoding method and rename it to portal_xx_XX. Showing the Language Selection List When you only use the English language. 5. Identity Sources Page 53 .php. Saving New Language Files You must save the language file with UTF-8 encoding. but you must include all strings in the new language file. To create a new language file: 1. Move the file to /opt/CPNacPortal/phpincs/conf/L10N if it is not already there. / &gt in the translated strings. For example. you must show the language selection list on the Network Login page. make sure that the string's length is almost the same in size as the initial English string. To revert back to not showing the language selection list. The language selection list will show on the Network Login page.Advanced Captive Portal Configuration To disable a language:  Comment out the line of the specific language or delete the line. Remove these lines: <?PHP /* */?> You can find the first line a few lines above the language_selection string. You can find the second line about 20 lines below the language_selection string. save the file as a '.

key' Enter PEM pass phrase: 3. Note . If private key files with the same names already exist on the machine. Obtaining and Installing a Trusted Server Certificate To be accepted by an endpoint computer without a warning. Browse from different operating systems with different locale setups. Check Point gateways. For some fields there will be a default value. the administrator must install a server certificate signed by a trusted certificate authority. VeriSign or Thawte). Enter a password and confirm.. Server Certificates For secure SSL communication. the field will be left blank. gateways must establish trust with endpoint computers by showing a Server Certificate. Browsers do not trust this certificate. log in to expert mode. You see this output: Generating a 2048 bit RSA private key . Fill in the data.Advanced Captive Portal Configuration Making Sure the Strings Shows Correctly To make sure the strings show correctly: 1. 3. by default. This section discusses the procedures necessary to generate and install server certificates. Browse to the Captive Portal from a different browser and use a different font size. When an endpoint computer tries to connect to the gateway with the default certificate. Run: cpopenssl req -new -out <CSR file> -keyout <private key file> -config $CPDIR/conf/openssl. 1. Browse to the Captive Portal and select the English language. 2. This certificate can be issued directly to the gateway. because the gateway acts as a server to the clients. There are quite a few fields but you can leave some blank. To prevent these warnings. they are overwritten without warning.+++ writing new private key to 'server1. Identity Sources Page 54 . certificate warning messages open in the browser.'.This procedure creates private key files.+++ . gateways must have a server certificate signed by a known certificate authority (such as Entrust. The next sections describe how to get a certificate that is signed by a known certificate authority (CA) for a gateway. use a certificate created by the Internal Certificate Authority on the Security Management Server as their server certificate. From the gateway command line. Make sure that the text is shown correctly on the Captive Portal pages. 2. generate a Certificate Signing Request (CSR).cnf This command generates a private key. If you enter '. 4. Generating the Certificate Signing Request First. The CSR is for a server certificate. All portals on the same Security Gateway IP address use the same certificate. What you are about to enter is what is called a Distinguished Name or a DN. You see this message: You are about to be asked to enter information that will be incorporated into your certificate request. 5.. Browse to the Captive Portal and select the new language. or be a chained certificate that has a certification path to a trusted root certificate authority (CA).

This is the site that users access.  All other fields are optional. 2. convert these files to PEM (Base-64) format. generate a P12 file that contains the Signed Certificate and the private key.com. It does not affect the certificate installed manually using this procedure.key file that you generated in Generating the Certificate Signing Request (on page 54). If the signed certificate is in P12 or P7B format. The certificate that users see depends on the actual IP address that they use to access the portal.crt file contains the full certificate chain up to a trusted CA. 2.crt file to install the certificate with the *. Make sure that the . Install the policy on the gateway. Sometimes it is in a separate file. Identity Sources Page 55 . click Import or Replace. Get the Signed Certificate for the gateway from the certificate authority. Make sure to request a Signed Certificate in PEM format. a) Run: cpopenssl pkcs12 -export -out <output file> -in <signed cert chain file> -inkey <private key file> For example: cpopenssl pkcs12 -export -out server1. 4. use a text editor to combine them into one file.example.The Repository of Certificates on the IPSec VPN page of the SmartDashboard gateway object is only for self-signed certificates. Use the *. Note . Define the IP address of the portal in the Portal Settings page for the blade.Advanced Captive Portal Configuration  The Common Name field is mandatory. Viewing the Certificate To see the new certificate from a Web browser: The gateway uses the certificate when you connect with a browser to the portal. From the gateway command line.key b) Enter the certificate password when prompted. For example:    Gateway Properties > Mobile Access > Portal Settings Gateway Properties > SecurePlatform Settings Gateway Properties > Data Loss Prevention  Gateway Properties > Identity Awareness > Captive Portal > Settings > Access Settings In the Certificate section. click the lock icon that is next to the address bar in most browsers. log in to expert mode. 1. 1. For example: portal. 3. If the signed certificate and the trust chain are in separate files. 4. Send the CSR file to a trusted certificate authority. Usually you get the certificate chain from the signing CA.key private key file. This field must have the Fully Qualified Domain Name (FQDN). Import the new certificate to the gateway in SmartDashboard from a page that contains the Portal Settings for that blade. Installing the Signed Certificate All portals on the same IP address use the same certificate. Keep the .not only the IP address configured for the portal in SmartDashboard.p12 -in server1. Generating the P12 File After you get the Signed Certificate for the gateway from the certificate Authority. To see the certificate when you connect to the portal.crt -inkey server1.

Prepackaging Identity Agent Installation Prepackaging refers to a procedure that lets you add configuration to the Identity Agents installation. Go to Identity Awareness > Agent. Click OK. Advanced Identity Agents Configuration Customizing Parameters You can change settings for Identity Agent parameters to control agent behavior. Whether to disable the packet tagging feature that prevents IP spoofing. You can change some of the settings from SmartDashboard and some can be prepackaged with the agent. prepackage the agent with the server address. see Prepackaging Identity Agents (on page 77). To change Identity Agents parameters in SmartDashboard: 1. 2. 3. This is a sample list of parameters that you can change: Parameter Description Nac_agent_disable_settings Whether users can right click the Identity Agent client (umbrella icon on their desktops) and change settings.Advanced Identity Agents Configuration To see the new certificate from SmartDashboard: From a page that contains the portal settings for that blade. Note . Go to Policy > Global Properties > SmartDashboard Customization. Unless you resign the installation with your own software signing certificate. click the View button in the Certificate section. for example. Whether to hide the client (the umbrella icon does not show on users' desktops). For more information. You can add a default email address for to which to send client troubleshooting information. Click Configure. Identity Sources Page 56 . users that download the agent through the Captive Portal will receive a notification saying that the installer is not signed. This lets you.When you use prepackaging. You can then have users download the Identity Agents from the Captive Portal or send them the installation through email. Nac_agent_email_for_sending_logs Nac_agent_disable_quit Nac_agent_disable_tagging Nac_agent_hide_client 4. the digital signature in the installer is invalidated. The Agent parameters are shown. Whether users can right click the Identity Agent client (umbrella icon on their desktops) and close the agent.

such as the perimeter firewall and multiple Data Centers. Identity Awareness capability is centrally managed through the Security Management Server and SmartDashboard.Chapter 4 Advanced Deployment In This Chapter Introduction Deployment Options Configuring Clusters in Bridge Mode Deploying a Test Environment Deployment Scenarios 57 58 58 61 62 Introduction You can deploy Check Point Security Gateways enabled with Identity Awareness in various scenarios that provide a maximum level of security for your network environment and corporate data.      Page 57 . deploy the security gateway inline in front of the Data Center. you can create an identity-based firewall security Rule Base together with Application Control. You can deploy a security gateway enabled with Identity Awareness inline in front of the wireless switch. Network segregation – The security gateway helps you migrate or design internal network segregation. there is a need to deploy multiple security gateways at different network locations. Identity information about all users and machines obtained by each gateway is shared between all gateways in the network to provide a complete Identity Awareness infrastructure. You can deploy the security gateway at the remote branch offices to avoid malware threats and unauthorized access to the headquarters' internal network and Data Centers. All traffic that flows is then inspected by the gateway. segregated from the users' network. You can deploy the security gateway in transparent mode (bridge mode) to avoid significant changes in the existing network infrastructure. where you deploy the Check Point security gateway at the perimeter where it protects access to the DMZ and the internal network. Wireless campus – Wireless networks are not considered secure for network access. Identity Awareness lets you control access between different segments in the network by creating an identity-based policy. provide an identity aware access policy and inspect the traffic that comes from WLAN users. Identity Awareness gives guests access by authenticating guests with the web Captive Portal. This section describes recommended deployment scenarios and options available with Identity Awareness. When you enable Identity Awareness at the branch office gateway you make sure that users are authenticated before they reach internal resources. In this case. Distributed enterprise with branch offices – The distributed enterprise consists of remote branch offices connected to the headquarters through VPN lines. The identity information learned from the branch office gateways is shared between internal gateways to avoid unnecessary authentications. you can protect access to the servers with the security gateway. Large scale enterprise deployment – In large scale enterprise networks.  Perimeter security gateway with Identity Awareness – This deployment scenario is the most common scenario. You can deploy the security gateway close to the access network to avoid malware threats and unauthorized access to general resources in the global network. targeted to the Internet. You can control access to resources and applications with an identity-based access policy. You can distribute the identity-based policy to all identity aware security gateways in the network. The perimeter security gateway can also control and inspect outbound traffic. To do this. Data Center protection – If you have a Data Center or server farm. however they are intensively used to provide access to wireless-enabled corporate devices and guests.

The gateway members of a security cluster must have at least 5 interfaces. and Identity Awareness differently. In this case. This deployment method lets you install the security gateway as a Layer 2 device.Cluster members and bridges must be on SecurePlatform or IPSO. We recommend SecurePlatform for full feature support. Due to bridge operations. One component that is deployed on a different gateway that serves as an external Identity Awareness gateway.Deployment Options Deployment Options You can deploy a security gateway enabled with Identity Awareness in two different network options:   IP routing mode Transparent mode (bridge mode) IP routing mode – This is a regular and standard method used to deploy Check Point security gateways. It lets you deploy the gateway inline in the same subnet. you must configure Identity Awareness with these components:   One component that is deployed on the bridge's cluster member gateways. You must configure these interfaces:     1 management (DMI) interface (with an IP address) 1 synchronization interface (with an IP address) 2 interfaces for the bridge (no IP addresses) 1 cluster interface (with a virtual IP address) . bridges. machines and networks) must connect to the same switch. the gateway behaves as an IP router that inspects and forwards traffic from the Internet interface to the external interface and vice versa. rather than an IP router. Transparent mode – Known also as a "bridge mode". Both interfaces should be located and configured using different network subnets and ranges. Important . cluster interfaces and all identity sources (users. The benefit of this method is that it does not require any changes in the network infrastructure. Advanced Deployment Page 58 .to communicate with the external Identity Awareness gateway. The external Identity Awareness gateway. You usually use this mode when you deploy the gateway at the perimeter. Configuring Clusters in Bridge Mode If you have clusters with a bridge in your environment. This deployment option is mostly suitable when you must deploy a gateway for network segregation and Data Center protection purposes. you must configure the cluster members.

Advanced Deployment Page 59 . Vlan Vlan-x Preparing Clusters with a Bridge To prepare clusters with a bridge for Identity Awareness: 1.  Each with an interface (for example.enabled with Identity Awareness Bridge interfaces (without IP addresses) 2 Interfaces Eth0 Eth1 Eth2 Eth3 Eth4 Sync interface Dedicated Management interface (DMI) Cluster interface (with IP address) The Vlan in the network.enabled with Identity Awareness (serves as the external Identity Awareness gateway) R75 or higher cluster member gateways on SecurePlatform .Configuring Clusters in Bridge Mode Item Firewalls 1 Description R75 or higher Security Gateway on SecurePlatform . eth2) for a synchronization IP address. Create the cluster members on SecurePlatform. where x is the Vlan number.

In the Identity Awareness tab.cancel 3. Create a Security Gateway object. At the prompt. run brctl show to see the interfaces attached to the bridge. Configuring the External Identity Awareness Gateway To configure the external Identity Awareness gateway: 1. 2. e) Enter n .Network Connections b) Enter 1 . Select Share local identities with other gateways. Reboot the cluster members. Make sure you see an entry equivalent to the below. 3. make sure that the bridge interfaces are not monitored.next f) Enter c . Click OK. Checking the Bridge Configuration To make sure the bridge was configured correctly: 1. 3.Bridge d) Press spacebar to select the relevant interfaces (for example. eth3) for a management IP address. 4. Configuring the Cluster To configure the cluster: 1. Create a new cluster object: Advanced Deployment Page 60 .if c) Manually add br0 and the bridge interfaces (eth0 and eth1) to this file. 2. Enable the firewall Software Blade.Add new connection c) Enter 3 . Configure the bridge interface on the cluster members. Open SmartDashboard. On each of the gateway members. In sysconfig: a) Enter 5 . run ifconfig. On each of the gateway members. eth0 and eth1). 6. eth4) for a cluster IP address.Configuring Clusters in Bridge Mode  Each with an interface (for example. Open SmartDashboard. select Enable Identity Awareness and select the relevant identity sources. Continue with the sysconfig configurations and then reboot the cluster members. 2. 4. type: a) cd $FWDIR/conf b) vi discntd. 5. At the prompt. 2.  Each with an interface (for example.

The recommended test setup below gives you the ability to test all identity sources and create an identity-based policy. Do not select Not Defined. Install IIS with a sample Web Server. The IP address of each member must be the management IP address. Open SmartDashboard Customization and click Configure. b) Add the cluster members. g) Make sure Network defined by the interface IP and net mask is selected. open Identity Awareness. we recommend that you deploy it in a simple environment. Click OK. 3. You see the management interface. the Windows server that runs IIS (web server). Advanced Deployment Page 61 . Check Point security gateway R75 3. In the cluster object. DNS and IIS (Web resource) Deploy the gateway inline in front of the protected resource. 4. Click OK. 4. 3. Select Enable Identity Awareness and keep all options cleared. 3. Configuring Cluster and Bridge Support To configure cluster and bridge support: 1. You do not see the bridge interfaces in SmartDashboard. d) Click Get all members' topology with Topology. sync interface and the cluster members. Deploying a Test Environment If you want to evaluate how Identity Awareness operates in a security gateway. 2. f) Disable Anti-spoofing. The recommendation is to install 3 main components in the setup: 1. c) Open Topology > Edit Topology. The user host machine will access the protected resource via the security gateway. If the wizard opens. 2. Deploy a security gateway either in routing or bridge mode. Select Get identities from other gateways and select the gateway configured for the external component. 5. Microsoft Windows server with Active Directory. Install Windows Server and configure Active Directory and DNS. 6. 4. Install the user host machine with Windows XP and 7 OS.Deploying a Test Environment a) Enable the Firewall Software Blade. cancel it. Open Firewall-1 > General and select the cxl_is_bridge option. User host (Windows) 2. Open Policy > Global Properties. Testing Identity Sources To configure the test environment: 1. e) Define a Cluster interface in the Network Objective column and give the cluster object a virtual IP address.

Install the client as requested by the Captive Portal. Testing Identity Agents Enable and configure Identity Agents and configure Identity Agents self provisioning via Captive Portal ("Configuring Agent Deployment from Captive Portal" on page 37). 7. However. 13. You are redirected to the Captive Portal. access roles. Create an Access Role and define access for all authenticated users or select users with the Users picker. 6. 9. 16. Add the user host machine to the Active Directory domain. 12. You should be redirected to the Captive Portal. 3. 10. Open SmartView Tracker > Identity Awareness section and check whether the user is authenticated using the AD Query method. Test connectivity between the host and the Windows server. Advanced Deployment Page 62 . From the gateway's CLI revoke the authenticated user by: pdp control revoke_ip IP_ADDRESS 17. On the user host machine open an Internet browser and try to connect to the web resource. Create 3 rules in the Firewall Rule Base: a) Any to Any Negate HTTP accept log b) Access Role to Any HTTP accept log c) Any to Any Drop 11. 15. 14. 2. Install policy. Logout and login again from the user host machine. Access roles let you configure an identity aware policy together with Application Control to allow access only to specified user groups to the applications on the Internet. Follow the wizard and enable the AD Query and Captive Portal identity sources. Use the user host machine to test connectivity to the Web Server. Open a browser and connect to the web resource. The SSO method using Kerberos authentication can be tested as well.Deployment Scenarios 5. Enable Identity Awareness in the gateway. Enter user credentials. 1. see Kerberos SSO Configuration (on page 71). Controlling access to the allowed applications is possible through the Application Control blade. Test connectivity. Not all Internet applications and web sites are secure and some are restricted according to corporate policy. you may require a more granular access policy that is based also on user and machine identity – i. Users located in the internal networks access the Internet resource and applications daily. 4. Deployment Scenarios Perimeter Security Gateway with Identity Awareness Security Challenge The security gateway at the perimeter behaves as a main gate for all incoming and outgoing traffic to and from your corporate network. use the user's credentials to authenticate and access the web resource. When the client is installed wait for an authentication pop-up to enter the user's credentials via the client. Check logs. Blocking all internal access may impact productivity of certain employees that must have access in the context of their daily work definition. The user and machine names show in the connections logs. 8.e.

Deployment Scenarios

In this case Identity Awareness should be enabled on the perimeter security gateway.

Deployment scenario
1. Deploy the gateway at the perimeter in routing mode and define an external interface towards the ISP (the Internet) and an internal interface points to the internal corporate network LAN. Optional: you can define another internal interface which protects DMZ servers. 2. Make sure that NAT or Proxy devices do not exist between the gateway and LAN (the recommendation is to have proxy in the DMZ network). 3. Check that the gateway has connectivity to the internal AD domain controllers. 4. Make sure that users can reach the gateway’s internal interface. 5. Configure the Application Control blade. See the R75 Application Control Administration Guide (http://supportcontent.checkpoint.com/documentation_download?ID=11658). 6. If you have several perimeter gateways leading to the Internet, we recommend that you manage these gateways with one Security Management Server and SmartDashboard to deploy the relevant security policy.

Configuration
1. Enable Identity Awareness and select the appropriate identity sources. 2. Create access roles based on users and machines. You can create multiple access roles that represent different departments, user and machine groups and their location in the network. 3. Add the access roles to the source column of the relevant firewall and application control policies.

Data Center Protection
Security Challenge
The Data Center contains sensitive corporate resources and information that must be securely protected from unauthorized access. You must also protect it from malwares and viruses that can harm databases and steal corporate information. Access to the Data Center and particularly to certain applications must be granted only to compliant users and machines.

Deployment Scenario
1. Deploy the security gateway inline in front of the Date Center core switch, protecting access to the Data Center from the LAN. 2. We recommend that you deploy the gateway in the bridge mode, to avoid any changes in the network. However, IP routing mode is also supported. 3. Define at least two interfaces on the gateway and configure them to be internal or bridged. 4. Make sure that the gateway has connectivity to the Active Directory and all relevant internal domain controllers in the network (LAN).

Advanced Deployment

Page 63

Deployment Scenarios

5. Make sure that users from the LAN can connect to the Data Center through the security gateway with an ANY ANY accept policy. 6. Make sure that you do not have a proxy device between the gateway and users or the LAN.

Configuration
1. Enable Identity Awareness on the gateway and select identity sources. 2. Create access roles for users and apply the access roles to relevant Firewall security rules.

Large Scale Enterprise Deployment
Security Challenge
In complex large scale enterprise networks you must control access from the local network to the Internet and to multiple Data Center resources. Access should be granted only to compliant users and machines. The Data Center contains sensitive corporate resources and information that must be securely protected from unauthorized access. You must also protect it from malwares and viruses that can harm databases and steal corporate information. Users located in the internal networks access the Internet resource and applications daily. Not all Internet applications and web sites are secure and some are restricted according to corporate policy. Blocking all internal access may impact productivity of certain employees that must have access in the context of their daily work definition. Controlling access to the allowed applications is possible through the Application Control blade. However, you may require a more granular access policy that is based also on user and machine identity – i.e. access roles.

Deployment Scenario
1. Deploy or use existing security gateways at the perimeter and in front of the Data Center. 2. Install the gateway at the perimeter in routing mode, and use at least one external interface to the Internet and one to the internal network (define it as an internal interface). 3. Deploy the gateway as an inline device in front of the Data Center in bridge mode to avoid network changes. This is not required, but is recommended. Nonetheless, IP routing mode is also supported. 4. Make sure that all gateways in the Data Centers and perimeter can communicate directly with each other. 5. We recommend that you manage the gateway from one Security Management Server and SmartDashboard. 6. Make sure that there is connectivity from each gateway to the Active Directory internal domain controllers. 7. Make sure that in an "Any Any Accept" policy, users from the LAN can connect to the desired resources. 8. Make sure that there is no NAT or proxy devices installed between the gateways and LAN segment. If there are such devices, consider moving them to DMZ if possible.

Configuration
1. Enable Identity Awareness on the gateway and choose the appropriate identity source method for each gateway, at the perimeter and at the Data Center. 2. Create access roles for users and apply access roles to the relevant firewall security rules. 3. Use the Application Control policy in the perimeter gateway and add access roles to the policy.

Advanced Deployment

Page 64

Deployment Scenarios

4. In the Gateway properties > Identity Awareness tab, make sure to select Share local identities with other gateways.

AD Query Recommended Configuration
When you enable AD Query to obtain user and machine identity, we recommend that you enable the feature on all gateways that participate in the network environment. All gateways should have the Active Directory domain defined with the list of all relevant domain controllers in the internal network.

Identity Agents Recommended Configuration
If you choose to use Identity Agents to authenticate users and machines, you have to select the gateway that will be used to maintain identity agents. For a single Data Center and perimeter gateway it is recommended to define identity agents that connect to a single gateway. Then the identity obtained by the gateway is shared with the other gateways in the network. Select a high capacity / performance gateway, which can also behave as an authentication server, and configure this gateway’s IP / DNS on the Identity Agents (see Identity Agents section). For complex multi Data Center environments where there are several gateways that protect different Data Centers and the perimeter, we recommend that you balance Identity Agents authentication using different gateways. You can configure a list of gateways in the Identity Agent settings, where the agent will connect to different gateways. This provides load balancing across the gateways. Identities learned from the agents are shared between all gateways in the network.

Identity Sharing Advanced Settings
To define a list of gateways between which identity information is shared: 1. Go to Gateway properties > Identity Awareness tab and select Get identities from other gateways. 2. Select the gateways you want to obtain identities from.

Advanced Deployment

Page 65

clear the Share local identities with other gateways option. then define the particular gateway’s DNS/IP in the agent gateway configuration per access segment. keep this option selected and disable Get identities from other gateways in the segment gateway. Make sure that the gateways can communicate with the Active Directory domain controller deployed in each segment (replicated domain controllers). the perimeter gateway. Configuration 1. Distributed Enterprise with Branch Offices Security Challenge In distributed enterprises there is a potential risk of malware and viruses spreading from remote branch offices over VPN links to the corporate's internal networks. Users that connect to the network can potentially spread viruses and malwares across the network that can infect other computers and servers on the network.Deployment Scenarios Network Segregation Security Challenge Networks consist of different network segments and subnets where your internal users reside. You want to make sure that only compliant users and machines can pass and connect across multiple network segments. for example. If you want to use Identity Agents. Deployment scenario        We recommend that you deploy security gateways close to access networks before the core switch. Then go to the perimeter gateway and select Get identities from other gateways. Share identities learned from the segment gateways with the perimeter firewall to create an outgoing traffic firewall policy or use an Application Control policy as well. as well as authenticate users connecting to the servers and the Internet. Captive Portal or Identity Agents. In the Identity Awareness tab. Access between the LAN and the Internet is controlled by the gateways either at each segment or at the perimeter gateway. Access between the LAN and Data Center is controlled by the gateway. 3. 2. If there is a general domain controller that serves all users across the segments. We recommend that you deploy the gateway in bridge mode to avoid network and routing changes. 6. 4. Access between the segments is controlled by the gateway. There is also a challenge of how to provide Advanced Deployment Page 66 . Each gateway of a particular segment authenticates users with the selected method. make sure that all gateways can connect to this domain controller. 5. Either AD Query. If you want to share identities with one gateway. Make sure that there is no proxy or NAT device between the gateways and the LAN. Enable Identity Awareness on each gateway and select an appropriate identity source method. Deploy gateways in each segment in bridge mode.

When a user from a branch office attempts to connect to the Data Center. We recommend using bridge mode. Enable Identity Awareness and select the appropriate methods to get identity. you can deploy low capacity gateways due to a relatively low number of users. Create an access role and apply the roles in the security policy on the branch office gateways. 4. Configuration 1.Deployment Scenarios authorized access to users that come from remote branch offices that request and want to access the Data Center and the Internet. users from the branch office are identified by the local branch office gateway before connecting to the corporate network over VPN. Deployment Scenario 1. 2. 5. 7. 6. In this scenario. establishing a VPN link to the corporate gateways. If you have Active Directory domain controllers replicated across your branch offices make sure that local gateways can communicate with the domain controller. 3. The identities learned by the branch office gateways are then shared with the headquarters' internal and perimeter gateways. We recommend that you deploy security gateways at the remote branch offices and at headquarters in front of the Data Center and at the perimeter. 4. At remote branch offices. make sure that the gateways can access the headquarters' internal domain controller over VPN. The perimeter gateway can serve as a VPN gateway for branch offices as well. You can install the Data Center gateway in bridge mode to avoid changes to the existing network. we recommend that you deploy Data Center gateways to protect access to Data Center resources and applications. as well as a perimeter gateway. 3. Deploy the gateways at the branch offices in routing mode. the user is identified by the gateway at the headquarters Data Center without the need for additional authentication. perimeter and Data Center gateway. Advanced Deployment Page 67 . Select a security gateway according to a performance guideline for your remote branch offices. Define VPN site-to-site if necessary. Deploy a gateway at the perimeter that protects the internal network in routing mode. At the corporate headquarters. Deploy the remote branch gateways in IP routing mode and have them function as a perimeter firewall and VPN gateway. 2. In case you do not have a local domain controller. Deploy gateways inline at the Data Center. 5.

Configuration 1. select the fields you want guests to fill when they register. Advanced Deployment Page 68 . Wireless Campus Security Challenge You use wireless networks to grant access to employees that use Wi-Fi enabled devices. we recommend that you only configure a local domain controller list per site in the relevant gateways. identities are shared with the internal headquarter gateways. 4. 3. Furthermore. since the identity information is shared between branch and internal gateways accordingly. For example. Deploy the security gateway in bridge mode in front of the Wireless Switch. Select Log out users when they close the portal browser. by selecting these settings on the Identity Awareness tab: AD Query Recommended Configuration When you use AD Query to authenticate users from the local and branch offices. Enable Identity Awareness on the gateway. Wireless networks do not give a desired level of security in terms of network access. if you have a branch office gateway and a Data Center gateway. guests and contractors. On the branch office gateway. Select Captive Portal as an identity source. it is not intended for guests and contractors to install any endpoint agents on their devices. It is not necessary to configure all domain controllers available in the network. Identity Agents Recommended Configuration When using Identity Agents. such as Active Directory or RADIUS. 2. select the Active Directory domain controllers replications installed in the branch office only. select Unregistered guests login and in Settings.Deployment Scenarios 8. we recommend that you configure the local branch office gateway’s DNS/IP on the agent. enable AD Query on all gateways. 3. Wireless access is also intensively used to connect mobile devices such as smart phones where agents can be installed. Guests and contractors in some cases cannot use the corporate wired network connection and must connect through WLAN. Make sure that you share identities between the branch offices with the headquarter and Data Center gateways. The agents connect to the local gateway and the user is authenticated. Make sure that the gateway can communicate with the authentication server. 2. On the Data Center gateway. configure a list of domain controllers installed in the internal headquarters network. Deployment Scenario 1. Check that there is no NAT or proxy device between the gateway and the WLAN network. These devices are not part of the Active Directory domain. 4. In the Gateway properties > Identity Awareness tab > Captive Portal Settings. Make sure that the gateway can access the Internet or any other required resource in the network.

Deployment Scenarios Dedicated Identity Acquisition Gateway Security Challenge You have several Security Gateways that protect the Data Center or Internet access where access is based on identity acquisition. Deployment Scenario In this deployment scenario. All users authenticate with this gateway. performance authentication and sharing learned identities with all enforcing gateways in the network. On the enforcement gateways. enable the Identity Awareness feature and select the identity method. If you enable AD Query. The dedicated Security Gateway is responsible for acquiring user identity. Make sure to configure the gateway to share identities with other gateways in the network. 2. The gateways run different blades and deal with heavy traffic inspection. the dedicated gateway should communicate with all Active Directory domain controllers over WMI. 3. 1. On the dedicated identity acquisition gateway. To avoid an impact on performance of the gateways in terms of user identity acquisition and authentication. enable Identity Awareness and select Get identities from other gateways. you have to choose an appropriate appliance to deploy as the dedicated Identity Awareness enabled gateway. Advanced Deployment Page 69 . it is recommended to offload this functionality to a separate Security Gateway.

Deployment Scenarios Advanced Deployment Page 70 .

This means that a user authenticates to the domain one time and has access to all authorized network resources without additional authentication. Kerberos is the default authentication protocol used in Windows 2000 and above. This ticket vouches for the user’s identity.Chapter 5 Kerberos SSO Configuration In This Chapter Overview How SSO Operates References SSO Configuration 71 71 72 73 Overview The Identity Awareness Single Sign-On (SSO) solution gives the ability to transparently authenticate users that are logged in to the domain. How SSO Operates Item A B C Description Domain Controller Data Center Security Gateway that Identity Agents connect to Page 71 . the user authenticates to a domain controller that provides an initial ticket granting ticket (TGT). When the user needs to authenticate against the Security Gateway with Identity Awareness. When a user logs in. You get SSO in Windows domains with the Kerberos authentication protocol. the Identity Agent presents this ticket to the domain controller and requests a service ticket (SR) for a specific resource (Security Gateway that Identity Agents connect to). The Kerberos protocol is based on the idea of tickets. encrypted data packets issued by a trusted authority which in this case is the Active Directory (AD). The Identity Agent then presents this service ticket to the gateway that grants access.

see these links:   http://web.edu/Kerberos/ (http://web.com/enus/library/bb742433.References Item 1 2 Description User logs in to the AD User gets an initial ticket (TGT) Item A B C 1 2 3 Description Domain Controller Data Center Security Gateway that Identity Agents connect to The Identity Agent connects to the Security Gateway The Security Gateway asks for user authentication The Identity Agent requests a service ticket (SR) for the Security Gateway that Identity Agents connect to and presents the TGT The AD sends a ticket (encrypting the user name with the shared secret between the AD and the Security Gateway that Identity Agents connect to) The Identity Agent sends the service ticket The Security Gateway that Identity Agents connect to decrypts the ticket with the shared secret and identifies the user The user gets access based on identity 4 5 6 7 References For detailed information on Kerberos SSO.mit.edu/Kerberos/) http://technet.microsoft.microsoft.aspx) Kerberos SSO Configuration Page 72 .com/en-us/library/bb742433.aspx (http://technet.mit.

open Active Directory Users and Computers (Start->Run->dsa. Add a new user account.msc) 2. Kerberos SSO Configuration Page 73 . You can choose any username and password. Clear User must change password at next logon and select Password Never Expires.Creating an LDAP Account Unit and configuring it with SSO.com. 3. For example: a user account named ckpsso with the password 'qwe123!@#' to the domain corp.SSO Configuration SSO Configuration SSO configuration includes two steps:   AD Configuration .acme. AD Configuration Creating a New User Account 1. SmartDashboard Configuration . In Active Directory.Creating a user account and mapping it to a Kerberos principal name.

AD 2003 SP2 requires support tools for 2003 sp2: http://www.aspx?familyid=96A35011-FD83-419D-939B9A772EA2DF90&displaylang=en) b) Download the support. 2.qa.msi files to a new folder on your AD server.microsoft.exe version on the AD. 1.ACME.exe is not installed by default in Windows 2000/2003. If you are using Windows 2000/2003: a) Retrieve the correct executable from the Microsoft Support site (http://support.cab and suptools.com/downloads/details. the ktpass utility is already installed on your server and you can run the command line.msi. max. c) Run the suptools. It is part of the Windows 2000/2003 support tools.checkpoint.acme.com/downloads/details. A Kerberos principal name consists of a service name (for the Security Gateway that Identity Agents connect to) and the domain name to which the service belongs (e. At the command prompt.com/) prior to installation.SSO Configuration Mapping the User Account to a Kerberos Principal Name This step uses the ktpass utility to create a Kerberos principal name that is used by both the gateway and the AD. run kptass with this syntax: C:> ktpass -princ ckp_pdp/domain_name@DOMAIN_NAME -mapuser username@domain_name -pass password -out unix.COM ckpsso qwe123@# The AD is ready to support Kerberos authentication for the Security Gateway.g. Use Ktpass 1.aspx?familyid=96A35011-FD83-419D-939B9A772EA2DF90&displaylang=en (http://www. Ktpass. If you’re using ActiveDirectory 2008.microsoft. 2.keytab –crypto RC4-HMAC-NT Below is an example of running ktpass with these parameters: Parameter Value domain_name@DOMAIN_NAME username@domain_name password corp.microsoft. You need to open the command prompt as an administrator by right clicking it and selecting "run as an Administrator". Open a command line to run the ktpass tool (Start > Run > cmd). Retrieve the correct executable You must install the correct ktpass. Ktpass is a command-line tool available in Windows 2000 and higher. For example. Kerberos SSO Configuration Page 74 .com).com@CORP.

set_spn –D ckp_pdp/corp. enter the domain name. you must either delete the different account beforehand or remove its association to the principal name (by using set_spn –D ckp_pkp/domain_name old_account name – i.If you have used the ktpass utility before for the same principal name (ckp_pdp/domain_name@DOMAIN_NAME) but with a different account. Entering a value into this field will not affect existing LDAP Account Units. c) In the Domain field. b) In the Profile field.acme. Configuring an Account Unit 1.com ckpsso). Failure to do this will cause the authentication to fail. ADServer. d) Select CRL retrieval and User management. select Microsoft_AD. Add a new host to represent the AD domain controller. 2. 3. In the General tab of the LDAP Account Unit: a) Enter a name. For example. Add a new LDAP Account Unit. Go to Network Objects tab > Nodes > Node > Host. Enter a name and IP address for the AD object and click OK. 4.SSO Configuration Important . Click Active Directory SSO configuration and configure the values (see example): Kerberos SSO Configuration Page 75 .e. Go to Servers and OPSEC Applications tab > Servers > New > LDAP Account Unit. SmartDashboard Configuration This section describes how to configure an LDAP Account Unit to support SSO. 5. It is highly recommended to fill this field for existing account units that you want to use for Identity Awareness.

b) In the Host field. 7. In the Objects Management tab: a) In the Manage objects on field. e) Leave the default settings for Ticket encryption method. 6. select the AD object you configured in step 4 above. c) In the Login DN field. Note . For example. In the Authentication tab. select the AD object you configured in step 4 above. c) Set the number of entries supported.COM c) Enter the account username you created in Creating a New User Account (on page 73). either skip step f or configure your domain controller to support LDAP over SSL.ACME.SSO Configuration a) Select Use kerberos Single Sign On. If you have not configured your domain controller to support LDAP over SSL. b) Enter the domain name. select Check Point Password in the Default authentication scheme and click OK. f) Click OK. ckpsso. For example. e) In the Check Point Gateways are allowed to section. select Use Encryption (SSL). enter the login DN of a predefined user (added in the AD) used for LDAP operations. select Read data from this server. CORP. In the Servers tab: a) Click Add and enter the LDAP Server properties.LDAP over SSL is not supported by default. b) Click Fetch Branches to configure the branches in use. 8. d) Enter the LDAP user password and confirm it. Kerberos SSO Configuration Page 76 . fetch the fingerprint and click OK. d) Enter the account password for that user (the same password you configured for the account username in AD) and confirm it. f) In the Encryption tab.

exe and it is deployed with the agent (Program Files > Check Point > Identity Agent).exe is a shell tool. To use it. Custom . The customization tool is called cpmsi_tool.The installation process and the product configuration can be customized. You can use the template INI file for quick configuration.msi Using the cpmsi_tool. Light agent – The Identity Agent is available for the single user that is running this installation and does not include packet tagging and machine authentication. All of the configuration parameters have default values that are deployed with the product and can remain unchanged.msi Secure Platform installation CD .exe The cpmsi_tool. The Features section controls the installed features. store it in the same location as the installation package and type: cpmsi_tool <installation package name> readini <INI file name> From the INI file you can control the configuration. The INI file is divided into 3 sections:    The Properties section controls the installation process.in /linux/windows/Check_Point_Custom_Nac_Client.exe Sample INI File 77 77 77 82 Background The Check Point Identity Agent has many advanced configuration parameters.Chapter 6 Prepackaging Identity Agents In This Chapter Background Custom Identity Agent msi Using the cpmsi_tool. with packet tagging and machine authentication. There are 3 types of Identity Agents:    Full agent – The Identity Agent is available for all users who use the computer. Page 77 . Custom Identity Agent msi You can find a customizable msi version of the Identity Agent (for distribution via a software distribution tool) in these places:   Installed Security Gateway .in /opt/CPNacPortal/htdocs/nac/nacclients/customAgent. The AddFiles section controls the deployed Identity Agent configuration. Some of these parameters relate to the installation process and some relate to the actual operation of the agent.

By default.Using the cpmsi_tool. If this dialog box is hidden then the installation process behaves as if the user clicked Next without changing anything.You can configure the Properties section properties using msiexec.An installation progress bar is shown while installation takes place. BASIC . Values for this property:   Yes No . FULL . you can type: msiexec. HIDEFEATURES This property determines the visibility of the Custom Setup (feature selection) dialog box in the installation process. the Custom Setup dialog box is shown (it is not hidden). For example.By default.exe.Anyone who uses the computer SINGLEUSER . Note .Only for the user who is installing the Identity Agent ASKUSER .The user sees a full installation user interface. INSTALLTYPE This property lets you can choose one of these installation type values:    ALLUSERS . the Choose Installation orientation dialog box is shown.No user interface is shown to the user.Leaves the dialog box in the installation for the end user to decide. This is the default value.[Properties] Section You can configure these Identity Agent installation properties in the INI file: INSTALLUITYPE There are 3 values for this property:    SILENT . Prepackaging Identity Agents Page 78 .exe The tool has some other options that are not used for Identity Awareness. Configuring Installation .exe /i <installation package name> SILENT=YES HIDEFEATURES=NO This command will start a silent installation where features are not hidden (even though for this type of installation this is irrelevant).

the dialog box is shown to the end user who can decide whether to install or not. MADService This property relates to the Managed Asset Detection service.exe Configuring Installed Features . if you set MADService=Yes then the feature dialog box will force install the Managed Asset Detection service.[Features] Section You can configure the following properties and decide whether or not to install these features. This property is required if you rules in the Rule Base that relate to machines. This is the default value. Prepackaging Identity Agents Page 79 . For example. Values:    Yes No Ask . or let users decide on their own. This driver signs every packet that is sent from the machine. PacketTagging This property relates to the Packet Tagging driver. This is a service that gives you machine authentication and enables managed asset detection prior to logon authentication.Using the cpmsi_tool.

Prepackaging Identity Agents Page 80 .exe This setting is required if you have rules in the Rule Base that use Access Roles and are set to enforce IP spoofing protection on the Machines tab. This is the default value.the dialog box is shown to the end user who can decide whether to install or not. Values:    Yes No Ask .Using the cpmsi_tool.

0 is the default value. Note . Copy it to the same directory as the installation package and the cpmsi_tool.exe Configuring Deployed Identity Agents .reg file.reg file with the relevant parameters. 0 is the default value. to send error logs to MYEmail and disable the agent's settings dialog box: [HKEY_LOCAL_MACHINE\SOFTWARE\C heckPoint\IA] "SendLogsTO"=MYEmail@checkpoint. 4 SendLogsTO String: <email Allows defining the default email addresses addresses to send logs to if an error occurs or if a delimited by ”.”> user chooses to send logs in from the agent’s status dialog box. After you create the defs. 3 HideGui DWORD:1.0 If the value is set to 1 then the quit button will not appear in the Identity Agent's tray menu. you must: 1. 2 DisableQuit DWORD:1. Uncomment the DEF_FILE_NAME line in the INI file. Prepackaging Identity Agents Page 81 .Using the cpmsi_tool. The defs.[AddFiles] Section You can add a defs.reg file to the installation that lets you change the deployed Identity Agent configuration. The registry values are stored in the branch HKEY_LOCAL_MACHINE > SOFTWARE > Checkpoint >IA or in HKEY_CURRENT_USER > SOFTWARE > Checkpoint > IA if the installation is for a single user.reg file does not exist the installation will fail. For example. 0 is the default value.0 If the value is set to 1 then the Identity Agent's tray icon will not appear and there will be no client GUI.0 Automatic Server Discovery You can define a default gateway and trusted gateways by defining a defs.com "DisableSettings"=dword:00000001 DisableSettings DWORD:1. 2. Registry file values: Registry Key 1 Accepted Values Description If the value is set to 1 then the settings button will not appear in the Identity Agent's tray menu.If the defs.reg file is a simple registry file.

Sample INI File For example: Note . Prepackaging Identity Agents Page 82 . the user will be asked to define the Security Gateway with Identity Awareness manually.If a default gateway is not defined and the automatic server discovery fails during installation. Sample INI File Below is a sample INI file with the default configuration.

This section describes these options. Page 83 . It also makes sure that communication between the client and the server was not tampered with by a Man In The Middle (MITM) attack. For this to happen. We offer several methods for configuring server discovery – from a very basic method of simply configuring one server to a method of deploying a domain wide policy of connecting to a server based on your current location.Chapter 7 Server Discovery and Trust In This Chapter Introduction Server Discovery and Trust Options Option Comparison 83 84 84 Introduction The Identity Agent client needs to be connected to a Security Gateway with Identity Awareness. Server trust refers to the process of validating that the server the end user connects to is indeed a genuine one. it must discover the server and trust it. Server discovery refers to the process of deciding which server the client should connect to.

Prepackaging – You can create a prepackaged version of the client installation that includes the with the server IP and trust data. it will ask the user to verify that it is correct manually. you can deploy the server addresses and trust data using a dedicated tool.     Option Comparison Requires Deploy AD Trust Data File name based No No MultiSite No Client Remains Signed? Yes Allows Ongoing Changes No Level Recommended for. Note that as DNS isn’t secure. AD based configuration – If client computers are members of an Active directory domain. During installation. Remote registry – All of the client configuration. Server Discovery and Trust Options These are the options that the client has for discovering a server and trusting it:  File name based server configuration – If no other method is configured (default.. You can deploy the values before installing the client (by GPO.. Note that the user has to trust the server by himself (the trust dialog box opens). If the client does not have the expected fingerprint configured. DNS SRV record based server discovery – It is possible to configure the server addresses in the DNS server. This section describes the methods that allow the expected fingerprint to be known. or any other system that lets you control the registry remotely). Single gateway deployments Very Simple Server Discovery and Trust Page 84 . out-of-the-box situation). the trust data cannot be configured in that way and the user will have to authorize it manually. This lets you use the configuration from first run. any Identity Agent downloaded from the portal will be renamed to have the portal machine IP in it. the client uses this IP to represent the Security Gateway with Identity Awareness.Server Discovery and Trust Options The trust process compares the server fingerprint calculated during the SSL handshake with the expected fingerprint. including the server addresses and trust data reside in the registry. without user intervention.

and there is more than one gateway Prepackaging No Yes Yes No No File Name Based Server Discovery This option is the easiest to deploy. which works with no configuration. Deployments with AD that you can modify Deployments without AD or with an AD you cannot modify. and works out-of-the-box if the Captive Portal is also the Security Gateway with Identity Awareness..Option Comparison Requires Deploy AD Trust Data AD based Yes Yes MultiSite Yes Client Remains Signed? Yes Allows Ongoing Changes Yes Level Recommended for. you can use this option. but the DNS can be changed Simple DNS based No No Partially Yes (per DNS server) Yes Simple Remote registry No Yes Yes Yes Yes Moderate Where remote registry is used for other purposes Advance d When both DNS and AD cannot be changed. If your deployment consists of one Security Gateway with Identity Awareness and a Captive Portal running on the same gateway and it is OK with you that the user needs to verify the server fingerprint and trust it once. Server Discovery and Trust Page 85 ..

Option Comparison

How does it work?
When a user downloads the Identity Agent client from the Captive Portal, the address of the Security Gateway with Identity Awareness is embedded into the file name. During the installation sequence, the client checks if there is any other discovery method configured (prepackaged, AD based, DNS based or local registry). If no method is configured and the server can be reached, it will be used as the Security Gateway with Identity Awareness. You can make sure that this is the case by looking at the client settings and seeing that the server that is shown in the file name is present in the Identity Agent dialog box.

Why can't we use this for trust data?
As the Captive Portal can be deployed in HTTP mode, we cannot be sure that the file name wasn’t modified by an attacker along the way. Therefore, we cannot trust data passed in the file name as authentic, and we need to verify the trust data by another means.

AD Based Configuration
If your client computers are members of an Active Directory domain and you have administrative access to this domain, you can use the Distributed Configuration tool to configure connectivity and trust rules. The Distributed Configuration tool consists of three windows:  Welcome - This window describes the tool and lets you to enter alternate credentials that are used to access the AD.

Server Discovery and Trust

Page 86

Option Comparison

 

Server configuration – This window lets you configure which Security Gateway with Identity Awareness the client should use, depending on its source location. Trusted gateways – This window lets you view and change the list of fingerprints that the Security Gateways with Identity Awareness consider secure.

Server Configuration Rules
If you use the Distributed Configuration tool and you configure ‘Automatically discover’ the server, the client fetches the rule lists and each time it needs to connect to a server, it tries to match itself against a rule, from top to bottom. When it matches a rule, it uses the servers shown in this rule, according to the priority specified. For example:

This configuration means: 1. If the user is coming from ‘192.168.0.1 – 192.168.0.255’, then try to connect to US-GW1. If it isn’t available, try BAK-GS2 (it will be used only if US-GW1 is not available, as its priority is higher). 2. Otherwise, if the user is connected from the Active Directory site ‘UK-SITE’, connect either to UK-GW1 or UK-GW2 (choose between them randomly, as they both have the same priority). If both of them are not available, connect to BAK-GS2. 3. Otherwise, connect to BAK-GS2 (the default rule is always matched when it is encountered).

Server Discovery and Trust

Page 87

Option Comparison

Trusted Gateways
The trusted gateways window shows the list of servers considered trusted – no popups will open when trying to connect to them. You can add, edit or delete a server. If you have connectivity to the server, you can get the name and fingerprint by entering its address and clicking ‘Fetch Fingerprint’. Otherwise, you should enter the same name and fingerprint that is shown when connecting to that server.

Note - The entire configuration is written under a hive named ‘Check Point’ under the ‘Program Data’ Branch in the AD database that is added in the first run of the tool. Adding this hive won’t have any affect on other AD based applications or features.

DNS Based Configuration
If you configure the client to ‘Automatic Discovery’ (the default), it looks for a server by issuing a DNS SRV query for the address ‘CHECKPOINT_NAC_SERVER._tcp’ (the DNS suffix is added automatically). You can configure the address in your DNS server. On the DNS server: 1. 2. 3. 4. 5. 6. 7. 8. 9. Go to Start > All Programs > Administrative Tools > DNS. Go to Forward lookup zones and select the applicable domain. Go to the _tcp subdomain. Right click and select Other new record. Select Service Location, Create Record. In the Service field, enter CHECKPOINT_NAC_SERVER. Set the Port number to 443. In Host offering this server, enter the address of the Security Gateway with Identity Awareness. Click OK. Note - Security Gateway with Identity Awareness load sharing can be achieved by creating several SRV records with the same priority and High Availability can be achieved by creating several SRV records with different priorities.

Server Discovery and Trust

Page 88

company. and saves its configuration to HKEY_LOCAL_MACHINE.212 > Remote Registry If you have another way to deploy registry entries to your client computers (i. Install the client on one of your computers.com Address: 192. and click ‘trust’ on the fingerprint verification dialog box.If you configure AD based and DNS based configuration.e.1. verify their fingerprints.168.Option Comparison Note . Make sure it is installed in the same mode that will be installed on the other computers – the ‘full agent’ installs itself to your program files directory. while the light agent installs itself to the users directory. That way._tcp.com idserver._tcp Server: dns. you can deploy the Security Gateway with Identity Awareness addresses and trust parameters before installing the clients.Displaying SRV Record Stored in the DNS Server Run the following commands: C:\> nslookup > set type=srv > checkpoint_nac_server.168.ad. Server Discovery and Trust Page 89 . Troubleshooting . Active Directory GPO updates). the results are combined according to the specified priority (from the lowest to highest).com internet address = 192. and saves its configuration to HKEY_CURRENT_USER.com SRV service location: priority = 0 weight = 0 port = 443 svr hostname = idserver.17 checkpoint_nac_server.company. 2.company.0. Connect manually to all of the servers that are configured.company. To use the remote registry option: 1. they will use the already deployed settings immediately after installation.

b) INSTALLTYPE Server Discovery and Trust Page 90 . 2.Option Comparison 3. you can click ‘Advanced’ and configure it that way. 4. and will result in security warnings displayed to the user downloading them from the Captive Portal. 4.reg containing the server addresses and trust data you want to deploy. Follow the instructions specified in Configuring Deployed Identity Agents . see Prepackaging Identity Agents (on page 77). (iii) SILENT – No UI will be shown. 3. Prepackaging Identity Agents Prepackaging can be used to control client aspects other than server discovery and trust. For more information. Create a package INI file containing the following: You may want to change the following attributes: a) INSTALLUITYPE (i) BASIC [default] – only a progress bar is shown. will invalidate the signature. click next. To create a prepackaged version of the Identity Agent: 1. If you do not have an Identity Agent installed. under /opt/CPNacPortal/htdocs/nacclients. Export the following registry keys (from HKEY_LOCAL_MACHINE / HKEY_CURRENT_USER. This section focuses mainly on server discover and trust aspects. including prepackaging. according to the client type installed): a) SOFTWARE\CheckPoint\NAC\TrustedGateways (the entire tree) b) SOFTWARE\CheckPoint\NAC\ (i) DefaultGateway (ii) DefaultGatewayEnabled (iii) PredefinedPDPConnRBUsed (iv) PredefinedPDPConnectRuleBase 5. install one (it does not necessarily need to be the custom agent). Deploy the exported keys to the workstations before installing the client on your workstations. You can use Identity Agent prepackaging feature to create a custom client version that comes bundled with the server addresses and trust data configured. Any modification to the Identity Agents. If you need the client to choose a server based on the client location. finish.msi from your Security Gateway with Identity Awareness. no other user interaction. etc. Configure it manually to connect to the requested servers (Use the settings dialog box). (ii) FULL – User will have dialog boxes describing the installation and can cancel. download the customAgent. Important .[AddFiles] Section (on page 81) to create a registry file named defs. See AD Based Configuration (on page 86) to understand how these rules are interpreted. Via SCP.The Identity Agents come digitally signed by Check Point Software Technologies Ltd.

Server Discovery and Trust Page 91 . No administrative privileges are needed.ini 6.Option Comparison (i) ALLUSERS – the client will be installed for any user running on the computer. you can distribute the modified customAgent.Custom. run: cpmsi_tool customAgent.msi readini package. go to the Security Gateway with Identity Awareness. d) Change the Require users to download value to Identity Agent . c) Click on the Captive Portal Settings button. and you don’t have to upload it to your portal). b) Go to the Identity Awareness page. (Note: If you use another software distribution mechanism. c) MADService (i) YES – Install the Managed Asset Detection Service (Requires administrative privileges). a) Under the Smart Dashboard. (ii) NO – Do not install the Managed Asset Detection Service. d) PacketTagging (i) YES – Install the Packet Tagging driver (Requires administrative privileges) (ii) NO – Do not install the Packet Tagging driver. and configure the Captive Portal to distribute the custom agent.msi to your identification portal at /opt/CPNacPortal/htdocs/nacclients. From the Identity Agent directory. Installation will require administrative privileges. (ii) SINGLEUSER – the client will be installed only for the installing user. 5. Upload the modified customAgent.

.

Firewall Rule Base Example • 8 How Captive Portal Operates .Firewall Rule Base • 10 How SSO Operates • 71 How You Download an Identity Agent Example • 11 I Identity Agent Deployment Methods • 36 Identity Agent Types • 34 Identity Agents • 11 Identity Awareness Scenarios • 13 Identity Sources • 41 Important Information • 3 Install Database for a Log Server • 49 Installing the Signed Certificate • 55 Introduction • 6.Index A Access Role Objects • 29 Access Settings • 31 Acquiring Identities for Active Directory Users • 13 Acquiring Identities in Application Control • 20 Acquiring Identities with Identity Agents • 18 Acquiring Identities with the Captive Portal • 15 AD Based Configuration • 86 AD Configuration • 73 AD Query • 8 Adding a New Language • 52 Advanced AD Query Configuration • 41 Advanced Captive Portal Configuration • 49 Advanced Deployment • 57 Advanced Identity Agents Configuration • 56 Agent Access • 38 Agent Deployment from the Portal • 34 Agent Upgrades • 39 Authentication Settings • 32.[Properties] Section • 78 Configuring Installed Features . 83 K Kerberos SSO Configuration • 71 L Large Scale Enterprise Deployment • 64 . 57. 39 Automatic Server Discovery • 81 Configuring the Firewall • 48 Confirm that Security Event Logs are Recorded • 49 Creating a New User Account • 73 Creating Access Roles • 26 Creating New Language Files • 53 Custom Identity Agent msi • 77 Customize Appearance • 32 Customizing Parameters • 56 Customizing Text Strings • 49 D Data Center Protection • 63 Dedicated Identity Acquisition Gateway • 69 Deploying a Test Environment • 61 Deployment • 12 Deployment Options • 58 Deployment Scenarios • 62 Distributed Enterprise with Branch Offices • 66 DNS Based Configuration • 88 E Editing the Language Array • 52 Enabling Identity Awareness on the Log Server • 40 Enabling Identity Awareness on the Security Gateway • 23 Excluding Users • 46 B Background • 77 F File Name Based Server Discovery • 85 C Captive Portal • 9 Changing Portal Text in SmartDashboard • 50 Check Connectivity • 47 Check Domain Administrator Credentials • 48 Checking the Bridge Configuration • 60 Checking the Status of Domain Controllers • 45 Choosing Identity Sources • 41 Configuring Agent Deployment for User Groups • 37 Configuring Agent Deployment from Captive Portal • 37 Configuring an Account Unit • 75 Configuring Captive Portal in SmartDashboard • 31 Configuring Cluster and Bridge Support • 61 Configuring Clusters in Bridge Mode • 58 Configuring Deployed Identity Agents [AddFiles] Section • 81 Configuring Identity Agents • 34 Configuring Identity Agents in SmartDashboard • 38 Configuring Identity Awareness • 23 Configuring Identity Awareness for a Domain Forest (Subdomains) • 41 Configuring Identity Awareness for a Log Server • 40 Configuring Installation .[Features] Section • 79 Configuring the Cluster • 60 Configuring the External Identity Awareness Gateway • 60 G Generating the Certificate Signing Request • 54 Generating the P12 File • 55 Getting Started With Identity Awareness • 6 H How AD Query Operates .

17. 90 Preparing Clusters with a Bridge • 59 V Verify the WMI Service • 48 Viewing the Certificate • 55 W What's Next • 20 Wireless Campus • 68 R References • 72 Remote Registry • 89 Required SmartDashboard Configuration • 16. 83 Server Discovery and Trust Options • 84 Session • 39 Setting Captive Portal to String ID Help Mode • 49 Showing the Language Selection List • 53 Single User Assumption • 45 SmartDashboard Configuration • 75 Source and Destination Fields • 30 Specifying Domain Controllers per Security Gateway • 42 SSO Configuration • 73 Page 94 . 19 User identification in the Logs • 21 User Identification in the Logs • 14. 18. 21 Results of the Wizard • 26 S Sample INI File • 82 Saving New Language Files • 53 Scenario Guest Users from Unmanaged Device • 17 Identifying Users in Application Control Logs • 21 Identity Agent Deployment and User Group Access • 18 Laptop Access • 13 Recognized User from Unmanaged Device • 15 Server Certificates • 54 Server Discovery and Trust • 37.M Making Sure the Strings Shows Correctly • 53 Mapping the User Account to a Kerberos Principal Name • 74 Multiple Gateway Environments • 46 T Testing Identity Agents • 62 Testing Identity Sources • 61 Troubleshooting • 47 Troubleshooting . 18 Using Access Roles • 15 Using Identity Awareness in the Application Control Rule Base • 29 Using Identity Awareness in the Firewall Rule Base • 28 Using the cpmsi_tool.Displaying SRV Record Stored in the DNS Server • 89 N Name and Password Login Settings • 33 Negate and Block • 31 Negate and Drop • 29 Network Segregation • 66 Non-English Language Support • 46 U Unregistered Guest Login Settings • 33 Use wbemtest to Verify WMI • 47 User Access • 33 User Experience • 16.exe • 77 O Obtaining and Installing a Trusted Server Certificate • 54 Option Comparison • 84 Overview • 71 P Packet Tagging for Anti-Spoofing • 35 Performance • 46 Perimeter Security Gateway with Identity Awareness • 62 Permissions and Timeout • 45 Portal Network Location • 31 Prepackaging Identity Agent Installation • 56 Prepackaging Identity Agents • 77. 19. 17.

Sign up to vote on this title
UsefulNot useful