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

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

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

this lets you create firewall rules with any of these properties. 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. 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. it shows the IP address of the user or machine with a name. This lets you enforce access and audit data based on identity. For example. 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. Page 6 .Chapter 1 Getting Started With Identity Awareness In This Chapter Introduction Deployment Identity Awareness Scenarios 6 12 13 Introduction Traditionally. Identity Awareness removes this notion of anonymity since it maps users and machine identities. It is applicable for both Active Directory and non-Active Directory based networks as well as for employees and guest users.

you use Access Role objects to define users.Introduction In SmartDashboard. Getting Started With Identity Awareness Page 7 . Depending on those considerations. you can configure Identity Awareness to use one identity source or a combination of identity sources ("Choosing Identity Sources" on page 41). machines and network locations as one object. 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.

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

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

or RADIUS. 3. The credentials are verified. Getting Started With Identity Awareness Page 10 . A user wants to access the Internal Data Center. Configure this in the Portal Settings.Introduction  Click a link to download an Identity Awareness agent. Check Point internal credentials. 5. In this example they are verified with the AD server. such as LDAP. 1. 2. The user enters his regular office credentials. 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 . 4. The user can now go to the originally requested URL.Firewall Rule Base The steps listed in the example align with the numbers in the image below.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

 Each with an interface (for example.enabled with Identity Awareness (serves as the external Identity Awareness gateway) R75 or higher cluster member gateways on SecurePlatform . eth2) for a synchronization IP address. Vlan Vlan-x Preparing Clusters with a Bridge To prepare clusters with a bridge for Identity Awareness: 1. where x is the Vlan number.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. Create the cluster members on SecurePlatform. Advanced Deployment Page 59 .Configuring Clusters in Bridge Mode Item Firewalls 1 Description R75 or higher Security Gateway on SecurePlatform .

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

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

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

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

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

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

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

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

Deployment Scenarios Advanced Deployment Page 70 .

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

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

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

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

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

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

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

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

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

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

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

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

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. it must discover the server and trust it.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. 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. Page 83 . For this to happen. Server trust refers to the process of validating that the server the end user connects to is indeed a genuine one. Server discovery refers to the process of deciding which server the client should connect to.

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

and there is more than one gateway Prepackaging No Yes Yes No No File Name Based Server Discovery This option is the easiest to deploy. 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.. you can use this option.Option Comparison Requires Deploy AD Trust Data AD based Yes Yes MultiSite Yes Client Remains Signed? Yes Allows Ongoing Changes Yes Level Recommended for. and works out-of-the-box if the Captive Portal is also the Security Gateway with Identity Awareness. Deployments with AD that you can modify Deployments without AD or with an AD you cannot modify.. If your deployment consists of one Security Gateway with Identity Awareness and a Captive Portal running on the same gateway and it is OK with you that the user needs to verify the server fingerprint and trust it once. Server Discovery and Trust Page 85 . which works with no configuration.

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

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

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

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

.

57.[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 .Firewall Rule Base Example • 8 How Captive Portal Operates .[Properties] Section • 78 Configuring Installed Features .Firewall Rule Base • 10 How SSO Operates • 71 How You Download an Identity Agent Example • 11 I Identity Agent Deployment Methods • 36 Identity Agent Types • 34 Identity Agents • 11 Identity Awareness Scenarios • 13 Identity Sources • 41 Important Information • 3 Install Database for a Log Server • 49 Installing the Signed Certificate • 55 Introduction • 6.Index A Access Role Objects • 29 Access Settings • 31 Acquiring Identities for Active Directory Users • 13 Acquiring Identities in Application Control • 20 Acquiring Identities with Identity Agents • 18 Acquiring Identities with the Captive Portal • 15 AD Based Configuration • 86 AD Configuration • 73 AD Query • 8 Adding a New Language • 52 Advanced AD Query Configuration • 41 Advanced Captive Portal Configuration • 49 Advanced Deployment • 57 Advanced Identity Agents Configuration • 56 Agent Access • 38 Agent Deployment from the Portal • 34 Agent Upgrades • 39 Authentication Settings • 32. 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 . 83 K Kerberos SSO Configuration • 71 L Large Scale Enterprise Deployment • 64 .

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

Sign up to vote on this title
UsefulNot useful