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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

3. To enable IP Spoofing protection: 1. Make sure users have the full Identity Agent installed. 2. If the user does not have administrator permissions.When you deploy the Full Identity Agent it is necessary for the user that installs the client to have administrator rights on the computer. Configuring Identity Awareness Page 36 .Packet Tagging can only be set on computers installed with the 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. Note .Configuring Identity Agents The Identity Awareness view in SmartView Tracker shows Packet Tagging logs.you can configure that users must download the Identity Agent from the Captive Portal. Click OK. 4. the Light Identity Agent is installed instead. In the Machines tab. Note . the Identity Agent automatically knows if there are administrator permissions on the computer or not and installs itself accordingly. select Enforce IP spoofing protection (requires full identity agent). Identity Agent Deployment Methods There are 2 Identity Agent deployment methods:  Using Captive Portal . Create an Access Role ("Creating Access Roles" on page 26).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Deployment Scenarios Advanced Deployment Page 70 .

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

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

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

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

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

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

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

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

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

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

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

the user will be asked to define the Security Gateway with Identity Awareness manually. Prepackaging Identity Agents Page 82 .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.

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

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

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

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

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

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

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

.

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. 83 K Kerberos SSO Configuration • 71 L Large Scale Enterprise Deployment • 64 . 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 . 57.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.[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 .

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. 18. 17. 83 Server Discovery and Trust Options • 84 Session • 39 Setting Captive Portal to String ID Help Mode • 49 Showing the Language Selection List • 53 Single User Assumption • 45 SmartDashboard Configuration • 75 Source and Destination Fields • 30 Specifying Domain Controllers per Security Gateway • 42 SSO Configuration • 73 Page 94 . 90 Preparing Clusters with a Bridge • 59 V Verify the WMI Service • 48 Viewing the Certificate • 55 W What's Next • 20 Wireless Campus • 68 R References • 72 Remote Registry • 89 Required SmartDashboard Configuration • 16. 21 Results of the Wizard • 26 S Sample INI File • 82 Saving New Language Files • 53 Scenario Guest Users from Unmanaged Device • 17 Identifying Users in Application Control Logs • 21 Identity Agent Deployment and User Group Access • 18 Laptop Access • 13 Recognized User from Unmanaged Device • 15 Server Certificates • 54 Server Discovery and Trust • 37.M Making Sure the Strings Shows Correctly • 53 Mapping the User Account to a Kerberos Principal Name • 74 Multiple Gateway Environments • 46 T Testing Identity Agents • 62 Testing Identity Sources • 61 Troubleshooting • 47 Troubleshooting . 17.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. 19 User identification in the Logs • 21 User Identification in the Logs • 14. 19. 18 Using Access Roles • 15 Using Identity Awareness in the Application Control Rule Base • 29 Using Identity Awareness in the Firewall Rule Base • 28 Using the cpmsi_tool.

Sign up to vote on this title
UsefulNot useful