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

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

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

this lets you create firewall rules with any of these properties. Page 6 . It is currently available on the Firewall blade and Application Control blade and will operate with other blades in the future. For example. Identity Awareness removes this notion of anonymity since it maps users and machine identities. Identity Awareness lets you easily configure network access and auditing based on network location and:   The identity of a user The identity of a machine When Identity Awareness identifies a source or destination.Chapter 1 Getting Started With Identity Awareness In This Chapter Introduction Deployment Identity Awareness Scenarios 6 12 13 Introduction Traditionally. This lets you enforce access and audit data based on identity. Identity Awareness is an easy to deploy and scalable solution. it shows the IP address of the user or machine with a name. 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. firewalls use IP addresses to monitor traffic and are unaware of the user and machine identities behind those IP addresses. It is applicable for both Active Directory and non-Active Directory based networks as well as for employees and guest 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. Getting Started With Identity Awareness Page 7 . Depending on those considerations. you can configure Identity Awareness to use one identity source or a combination of identity sources ("Choosing Identity Sources" on page 41). Identity Awareness also lets you see user activity in SmartView Tracker and SmartEvent based on user and machine name and not just IP addresses. you use Access Role objects to define users.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Deployment Scenarios Advanced Deployment Page 70 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.

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

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 .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. 17. 17.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. 90 Preparing Clusters with a Bridge • 59 V Verify the WMI Service • 48 Viewing the Certificate • 55 W What's Next • 20 Wireless Campus • 68 R References • 72 Remote Registry • 89 Required SmartDashboard Configuration • 16. 83 Server Discovery and Trust Options • 84 Session • 39 Setting Captive Portal to String ID Help Mode • 49 Showing the Language Selection List • 53 Single User Assumption • 45 SmartDashboard Configuration • 75 Source and Destination Fields • 30 Specifying Domain Controllers per Security Gateway • 42 SSO Configuration • 73 Page 94 . 19 User identification in the Logs • 21 User Identification in the Logs • 14. 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. 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. 18.

Sign up to vote on this title
UsefulNot useful