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).

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

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

Page 6 .Chapter 1 Getting Started With Identity Awareness In This Chapter Introduction Deployment Identity Awareness Scenarios 6 12 13 Introduction Traditionally. For example. 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. This lets you enforce access and audit data based on identity. this lets you create firewall rules with any of these properties. firewalls use IP addresses to monitor traffic and are unaware of the user and machine identities behind those IP addresses. Identity Awareness is an easy to deploy and scalable solution. It is currently available on the Firewall blade and Application Control blade and will operate with other blades in the future. it shows the IP address of the user or machine with a name. 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. It is applicable for both Active Directory and non-Active Directory based networks as well as for employees and guest users. Identity Awareness removes this notion of anonymity since it maps users and machine identities.

you use Access Role objects to define users.Introduction In SmartDashboard. Getting Started With Identity Awareness Page 7 . 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. Identity Awareness also lets you see user activity in SmartView Tracker and SmartEvent based on user and machine name and not just IP addresses. you can configure Identity Awareness to use one identity source or a combination of identity sources ("Choosing Identity Sources" on page 41). Depending on those considerations. machines and network locations as one object.

 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. shares a network drive. AD Query AD Query is an easy to deploy. How AD Query Operates . Identity aware gateways can share the identity information that they acquire with other identity aware gateways. when a user logs in. No installation is necessary on the clients or on the Active Directory server. See Advanced Deployment (on page 57) for more information. or accesses an Intranet portal. AD Query is selected as a way to acquire identities. It is based on Active Directory integration and it is completely transparent to the user.Firewall Rule Base Example The steps listed in the example align with the numbers in the image below. a standard Microsoft protocol. 1. Getting Started With Identity Awareness Page 8 . 2. The Security Gateway registers to receive security event logs from the Active Directory domain controllers. unlocks a screen. users that need to pass through several enforcement points are only identified once. The AD Query option operates when:  An identified asset (user or machine) tries to access an Intranet resource that creates an authentication request. The Security Gateway communicates directly with the Active Directory domain controllers and does not require a separate server. clientless identity acquisition method.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). reads emails through Exchange. It is based on Windows Management Instrumentation (WMI). In this way. For example. A user logs in to a desktop computer using his Active Directory credentials.

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

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

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

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

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

168. Note .ACME. This uses the identity acquired from AD Query.217.AD Query maps the users based on AD activity. This can take some time and depends on user activity. If John Adams is not identified (the IT administrator does not see the log).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.COM. he should lock and unlock the computer.3. This log entry shows that the system maps the source IP to the user John Adams from CORP. Getting Started With Identity Awareness Page 14 .

Her access to resources is based on rules in the Firewall Rule Base. Unmanaged. it is necessary for the administrator to change the current rule in the Rule Base. 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. they are automatically sent to the Captive Portal. Scenario: Recognized User from Unmanaged Device The CEO of ACME recently bought her own personal iPad. To do this. Because the iPad is not a member of the Active Directory domain. 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 wants to access the internal Finance Web server from her iPad. If unidentified users try to connect to resources in the network that are restricted to identified users. Getting Started With Identity Awareness Page 15 . 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. 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. Let's examine some scenarios to understand what the Captive Portal does and the configuration required for each scenario. The IT administrator can then remove the static IP from John Adam's laptop and give it a dynamic IP. she cannot identify seamlessly with AD Query.Identity Awareness Scenarios Using Access Roles To let John Adams access the HR Web Server from any machine. she can enter her AD credentials in the Captive Portal and then get the same access as on her office computer. However.

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

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

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

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

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

You can use all the types of identity sources to acquire identities of users who try to access applications. 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. Enables Identity Awareness on a gateway. This adds a default rule to the Application Control Rule Base that allows traffic from known applications. with the tracking set to Log. In SmartView Tracker logs and SmartEvent events.com/documentation_download?ID=11658). selects AD Query as one of the Identity Sources. the IT administrator must enable Application Control and Identity Awareness. 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. It also shows Application Control data. User identification in the Logs Logs related to application traffic in SmartView Tracker and SmartEvent show data for identified users.checkpoint. This SmartView Tracker log entry shows that the system maps the source IP address with the user's identity. you can see which user and IP address accesses which applications. The SmartView Tracker and SmartEvent logs will then show identity information for the traffic. Getting Started With Identity Awareness Page 21 . Installs the policy. Next. To do this. See the R75 Application Control Administration Guide (http://supportcontent. Enables the Application Control blade on a gateway. 3.Identity Awareness Scenarios    Use Identity Awareness Access Roles in Application Control rules as the source or destination of the rule. Required SmartDashboard Configuration To make this scenario work. 2.

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

the system is ready to monitor Identity Awareness. From the Network Objects tree. Double-click the gateway on which to enable Identity Awareness. You can use the wizard to configure one Security Gateway that uses the AD Query and Captive Portal for acquiring identities. select Enable Identity Awareness. To enable Identity Awareness: 1. Page 23 . select Identity Awareness. The Identity Awareness Configuration wizard opens. 3. Log in to SmartDashboard. a wizard opens. 2.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. Or From the Gateway Properties tree. On the General Properties page > Additional Features section. expand the Check Point branch. 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. 4. When you complete the wizard and install a policy. select Identity Awareness. On the Identity Awareness page.

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

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

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

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

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

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

If all the conditions apply. there is no match and the next rule is examined. the user is granted access to Gmail. Furthermore. The connection protocol is HTTP. This means you cannot have a rule that uses an access role in both the Source column and the Destination column.An unidentified user that browses to Gmail does not match rules 1 and 2 because of the application. This happens because the action is set to redirect to the Captive Portal.An unidentified Finance user that attempts to access Salesforce is sent to the Captive Portal. right-click the Action column and select Edit Properties. Because the application is not HTTP. the user is granted access according to rule number 1. If not all conditions apply. Since none of the rules match. 3. 2. the user is granted access to the Remote Administration Tool. you cannot use access roles in both the Source and Destination columns in the same Rule Base.An unidentified user that attempts to access the Remote Administration Tool matches rule 2. Example 3 . Select Redirect HTTP connections. Since none of the rules match.  When the criteria does not match any of the rules in the Rule Base:  The traffic is allowed.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. 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 . you can use a network object together with an access role object. But the condition between them is "or" and not "and". but not the Source column. The action is set to redirect to the Captive Portal. After entering credentials and being identified. traffic cannot be redirected to the Captive Portal. In a rule that uses an access role in the Source column. Below is an example of an Application Control Rule Base that shows how criteria matching operates: No. The Action column shows that a redirect to the Captive Portal occurs. the traffic is redirected to the Captive Portal to get credentials and see if there is a match. 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. Click OK. Example 2 . In the Source and Destination columns. In rule 3 there is also no match because the action is not set to redirect to the Captive Portal. The Action Properties window opens. To redirect HTTP traffic to the Captive Portal: 1. different users experience different outcomes: Example 1 .

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

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

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

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

If you do not configure SSO or you disable it. To protect packets from IP spoofing attempts.Configuring Identity Agents User identification . The Identity Agent tells the Security Gateway and you stay connected. 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.You get machine identification when you use the Full Agent as it requires installing a service. This table shows the similarities and differences of the Identity Agent types. you can enable Packet Tagging. 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. the Identity Agent automatically detects the change.Users that log in to the Active Directory domain are transparently authenticated (with SSO) and identified when using an Identity Agent. By doing so.When an endpoint IP address changes (interface roaming or DHCP assigns a new address). IP change detection . the user bypasses identity access enforcement rules. Machine identification .A technology that prevents IP spoofing is available only for the Full Agent as it requires installing a driver. the Identity Agent uses username and password authentication with a standard LDAP server. Packet tagging . 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. Configuring Identity Awareness Page 35 . Packet Tagging for Anti-Spoofing IP Spoofing happens when an unauthorized user assigns an IP address of an authenticated user to an endpoint computer. The system opens a window for entering credentials. Packet Tagging is a patent pending technology that prevents spoofed connections from passing through the gateway.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The perimeter security gateway can also control and inspect outbound traffic. deploy the security gateway inline in front of the Data Center.      Page 57 . This section describes recommended deployment scenarios and options available with Identity Awareness. you can protect access to the servers with the security gateway. Wireless campus – Wireless networks are not considered secure for network access. When you enable Identity Awareness at the branch office gateway you make sure that users are authenticated before they reach internal resources. Data Center protection – If you have a Data Center or server farm. 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. You can control access to resources and applications with an identity-based access policy. You can deploy a security gateway enabled with Identity Awareness inline in front of the wireless switch. 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.  Perimeter security gateway with Identity Awareness – This deployment scenario is the most common scenario.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. Identity Awareness lets you control access between different segments in the network by creating an identity-based policy. such as the perimeter firewall and multiple Data Centers. however they are intensively used to provide access to wireless-enabled corporate devices and guests. where you deploy the Check Point security gateway at the perimeter where it protects access to the DMZ and the internal network. The identity information learned from the branch office gateways is shared between internal gateways to avoid unnecessary authentications. To do this. Identity Awareness gives guests access by authenticating guests with the web Captive Portal. provide an identity aware access policy and inspect the traffic that comes from WLAN users. targeted to the Internet. In this case. Identity Awareness capability is centrally managed through the Security Management Server and SmartDashboard. 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. You can deploy the security gateway in transparent mode (bridge mode) to avoid significant changes in the existing network infrastructure. segregated from the users' network. Large scale enterprise deployment – In large scale enterprise networks. All traffic that flows is then inspected by the gateway. Distributed enterprise with branch offices – The distributed enterprise consists of remote branch offices connected to the headquarters through VPN lines. you can create an identity-based firewall security Rule Base together with Application Control. You can distribute the identity-based policy to all identity aware security gateways in the network. 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.

Important . Transparent mode – Known also as a "bridge mode". rather than an IP router. In this case. the gateway behaves as an IP router that inspects and forwards traffic from the Internet interface to the external interface and vice versa. You usually use this mode when you deploy the gateway at the perimeter.Cluster members and bridges must be on SecurePlatform or IPSO. Configuring Clusters in Bridge Mode If you have clusters with a bridge in your environment.to communicate with the external Identity Awareness gateway. We recommend SecurePlatform for full feature support. 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 the cluster members. This deployment option is mostly suitable when you must deploy a gateway for network segregation and Data Center protection purposes. The external Identity Awareness gateway. machines and networks) must connect to the same switch. One component that is deployed on a different gateway that serves as an external Identity Awareness gateway. The gateway members of a security cluster must have at least 5 interfaces. Due to bridge operations. Advanced Deployment Page 58 . cluster interfaces and all identity sources (users. This deployment method lets you install the security gateway as a Layer 2 device. Both interfaces should be located and configured using different network subnets and ranges.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. The benefit of this method is that it does not require any changes in the network infrastructure. 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. and Identity Awareness differently.

 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. where x is the Vlan number. Vlan Vlan-x Preparing Clusters with a Bridge To prepare clusters with a bridge for Identity Awareness: 1. eth2) for a synchronization IP address. Advanced Deployment Page 59 .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 . Create the cluster members on SecurePlatform.

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

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

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). use the user's credentials to authenticate and access the web resource. access roles. Test connectivity. Open a browser and connect to the web resource. 13. Use the user host machine to test connectivity to the Web Server. 7. On the user host machine open an Internet browser and try to connect to the web resource. Blocking all internal access may impact productivity of certain employees that must have access in the context of their daily work definition. You should be redirected to the Captive Portal. 16. The SSO method using Kerberos authentication can be tested as well. Test connectivity between the host and the Windows server. 8. Not all Internet applications and web sites are secure and some are restricted according to corporate policy. From the gateway's CLI revoke the authenticated user by: pdp control revoke_ip IP_ADDRESS 17.e. 2. When the client is installed wait for an authentication pop-up to enter the user's credentials via the client. Enable Identity Awareness in the gateway. Open SmartView Tracker > Identity Awareness section and check whether the user is authenticated using the AD Query method. Create an Access Role and define access for all authenticated users or select users with the Users picker. 15. 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. Controlling access to the allowed applications is possible through the Application Control blade. Advanced Deployment Page 62 . Check logs. Add the user host machine to the Active Directory domain. Logout and login again from the user host machine. 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. 9. 14. 6. 10. 4. see Kerberos SSO Configuration (on page 71). Users located in the internal networks access the Internet resource and applications daily. you may require a more granular access policy that is based also on user and machine identity – i. Follow the wizard and enable the AD Query and Captive Portal identity sources. Enter user credentials.Deployment Scenarios 5. Install the client as requested by the Captive Portal. 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. You are redirected to the Captive Portal. 3. Install policy. 1. 12. However. The user and machine names show in the connections logs.

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

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

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

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

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

Deployment Scenarios Advanced Deployment Page 70 .

When a user logs in. How SSO Operates Item A B C Description Domain Controller Data Center Security Gateway that Identity Agents connect to Page 71 . When the user needs to authenticate against the Security Gateway with Identity Awareness. encrypted data packets issued by a trusted authority which in this case is the Active Directory (AD). the user authenticates to a domain controller that provides an initial ticket granting ticket (TGT). Kerberos is the default authentication protocol used in Windows 2000 and above. You get SSO in Windows domains with the Kerberos authentication protocol. The Identity Agent then presents this service ticket to the gateway that grants access. The Kerberos protocol is based on the idea of tickets. This ticket vouches for the user’s identity. 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).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. This means that a user authenticates to the domain one time and has access to all authorized network resources without additional authentication.

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.edu/Kerberos/ (http://web.aspx (http://technet.com/enus/library/bb742433.aspx) Kerberos SSO Configuration Page 72 .microsoft.edu/Kerberos/) http://technet.microsoft.com/en-us/library/bb742433.mit.mit. see these links:   http://web.

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

1.com@CORP.microsoft. 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.aspx?familyid=96A35011-FD83-419D-939B9A772EA2DF90&displaylang=en) b) Download the support. Kerberos SSO Configuration Page 74 . Ktpass.qa.exe version on the AD.com/downloads/details.cab and suptools.microsoft. the ktpass utility is already installed on your server and you can run the command line. max. 2. c) Run the suptools.exe is not installed by default in Windows 2000/2003.COM ckpsso qwe123@# The AD is ready to support Kerberos authentication for the Security Gateway. Open a command line to run the ktpass tool (Start > Run > cmd). run kptass with this syntax: C:> ktpass -princ ckp_pdp/domain_name@DOMAIN_NAME -mapuser username@domain_name -pass password -out unix.g. For example.checkpoint.com/) prior to installation. AD 2003 SP2 requires support tools for 2003 sp2: http://www. At the command prompt.com/downloads/details. If you’re using ActiveDirectory 2008.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.aspx?familyid=96A35011-FD83-419D-939B9A772EA2DF90&displaylang=en (http://www. You need to open the command prompt as an administrator by right clicking it and selecting "run as an Administrator". 2. Retrieve the correct executable You must install the correct ktpass.ACME.msi files to a new folder on your AD server. If you are using Windows 2000/2003: a) Retrieve the correct executable from the Microsoft Support site (http://support. Use Ktpass 1.com).msi.microsoft.acme. It is part of the Windows 2000/2003 support tools.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. Ktpass is a command-line tool available in Windows 2000 and higher.

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

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

Chapter 6 Prepackaging Identity Agents In This Chapter Background Custom Identity Agent msi Using the cpmsi_tool. You can use the template INI file for quick configuration. The customization tool is called cpmsi_tool. Some of these parameters relate to the installation process and some relate to the actual operation of the agent. To use it.msi Secure Platform installation CD .in /opt/CPNacPortal/htdocs/nac/nacclients/customAgent. The Features section controls the installed features. 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 . The AddFiles section controls the deployed Identity Agent configuration.msi Using the cpmsi_tool. The INI file is divided into 3 sections:    The Properties section controls the installation process. All of the configuration parameters have default values that are deployed with the product and can remain unchanged. 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.The installation process and the product configuration can be customized. Page 77 .exe is a shell tool.in /linux/windows/Check_Point_Custom_Nac_Client.exe and it is deployed with the agent (Program Files > Check Point > Identity Agent).exe The cpmsi_tool. There are 3 types of Identity Agents:    Full agent – The Identity Agent is available for all users who use the computer. with packet tagging and machine authentication. 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. Custom .exe Sample INI File 77 77 77 82 Background The Check Point Identity Agent has many advanced configuration parameters.

exe.Leaves the dialog box in the installation for the end user to decide.Only for the user who is installing the Identity Agent ASKUSER .Anyone who uses the computer SINGLEUSER . Configuring Installation . FULL . you can type: msiexec. INSTALLTYPE This property lets you can choose one of these installation type values:    ALLUSERS . BASIC .exe The tool has some other options that are not used for Identity Awareness. This is the default value. By default.Using the cpmsi_tool. the Choose Installation orientation dialog box is shown.No user interface is shown to the user.An installation progress bar is shown while installation takes place.You can configure the Properties section properties using msiexec. HIDEFEATURES This property determines the visibility of the Custom Setup (feature selection) dialog box in the installation process. Values for this property:   Yes No . the Custom Setup dialog box is shown (it is not hidden).[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 .The user sees a full installation user interface.By default. If this dialog box is hidden then the installation process behaves as if the user clicked Next without changing anything. For example. Note .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).

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

the dialog box is shown to the end user who can decide whether to install or not. This is the default value. Prepackaging Identity Agents Page 80 . Values:    Yes No Ask .Using the cpmsi_tool.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.

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

If a default gateway is not defined and the automatic server discovery fails during installation.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. Sample INI File Below is a sample INI file with the default configuration.

Server trust refers to the process of validating that the server the end user connects to is indeed a genuine one. 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. Page 83 . Server discovery refers to the process of deciding which server the client should connect to. It also makes sure that communication between the client and the server was not tampered with by a Man In The Middle (MITM) attack. This section describes these options. For this to happen. it must discover the server and trust it.

Server Discovery and Trust Options The trust process compares the server fingerprint calculated during the SSL handshake with the expected fingerprint.. any Identity Agent downloaded from the portal will be renamed to have the portal machine IP in it. 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. This lets you use the configuration from first run. Prepackaging – You can create a prepackaged version of the client installation that includes the with the server IP and trust data. During installation. AD based configuration – If client computers are members of an Active directory domain. the trust data cannot be configured in that way and the user will have to authorize it manually. Note that the user has to trust the server by himself (the trust dialog box opens). including the server addresses and trust data reside in the registry. out-of-the-box situation).. Note that as DNS isn’t secure. Remote registry – All of the client configuration. or any other system that lets you control the registry remotely). you can deploy the server addresses and trust data using a dedicated tool. Single gateway deployments Very Simple Server Discovery and Trust Page 84 . without user intervention. 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. it will ask the user to verify that it is correct manually. If the client does not have the expected fingerprint configured. the client uses this IP to represent the Security Gateway with Identity Awareness.     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.

Deployments with AD that you can modify Deployments without AD or with an AD you cannot modify. Server Discovery and Trust Page 85 . 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. 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. and works out-of-the-box if the Captive Portal is also the Security Gateway with Identity Awareness.. which works with no configuration.Option Comparison Requires Deploy AD Trust Data AD based Yes Yes MultiSite Yes Client Remains Signed? Yes Allows Ongoing Changes Yes Level Recommended for. 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. you can use this option..

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

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

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

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

.

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 .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.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.Firewall Rule Base Example • 8 How Captive Portal Operates . 57.[Properties] Section • 78 Configuring Installed Features . 83 K Kerberos SSO Configuration • 71 L Large Scale Enterprise Deployment • 64 .

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 User identification in the Logs • 21 User Identification in the Logs • 14. 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. 19.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.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 . 17. 18. 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 . 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. 17. 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.

Sign up to vote on this title
UsefulNot useful