This action might not be possible to undo. Are you sure you want to continue?
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.
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).
Date 30 December 2010 15 December 2010 Description Improved documentation, formatting and document layout First release of this document
Check Point is engaged in a continuous effort to improve its documentation. Please help us by sending your comments (mailto:firstname.lastname@example.org?subject=Feedback on Identity Awareness R75 Administration Guide).
................56 .............................31 Configuring Captive Portal in SmartDashboard ...............3 Getting Started With Identity Awareness .................................................................41 Specifying Domain Controllers per Security Gateway ...............................................................................................................................................................46 Troubleshooting .................................40 Identity Sources ..............................................................................................................................................34 Identity Agent Types ...........................................................................................................................................................................................................................26 Creating Access Roles ....31 Access Settings ..............46 Non-English Language Support ............31 Portal Network Location ......................................................................................................................................................................41 Choosing Identity Sources .....................................................................................................................................................................................................................................................................................................30 Negate and Block ...................32 User Access .............................20 Configuring Identity Awareness ........56 Customizing Parameters .....................................13 Acquiring Identities for Active Directory Users .................................23 Enabling Identity Awareness on the Security Gateway ...............................................................29 Source and Destination Fields .................46 Performance ..................................................................................................................................49 Customizing Text Strings ...................31 Authentication Settings ......................................................................................................................................................................... 6 AD Query ................41 Configuring Identity Awareness for a Domain Forest (Subdomains) ...........................................................................13 Acquiring Identities with the Captive Portal ........23 Results of the Wizard ...........Contents Important Information .......................................................................................................................................................................52 Server Certificates ...............................................................................................................................................28 Access Role Objects .............................................................................................................................................38 Configuring Identity Awareness for a Log Server ....36 Server Discovery and Trust.......29 Using Identity Awareness in the Application Control Rule Base .....................11 Deployment ............................42 Permissions and Timeout ..........40 Enabling Identity Awareness on the Log Server ......................18 Acquiring Identities in Application Control .............................................................................................................................................................. 9 Identity Agents .............33 Agent Deployment from the Portal .......................................................................................................................34 Identity Agent Deployment Methods ................54 Advanced Identity Agents Configuration ....................................................34 Configuring Identity Agents..................................................................................................................................................41 Advanced AD Query Configuration ............................................................................................15 Acquiring Identities with Identity Agents .........................................................................................................................49 Adding a New Language............................................................................................. 8 Captive Portal ............12 Identity Awareness Scenarios .........47 Advanced Captive Portal Configuration ........................................................................37 Configuring Identity Agents in SmartDashboard...................................................................................................................................................................................26 Using Identity Awareness in the Firewall Rule Base .......45 Multiple Gateway Environments .....................................................................................................................................................29 Negate and Drop ........................................................................................................32 Customize Appearance.................................................6 Introduction .........................................................
...........................................................................83 Server Discovery and Trust Options ...........................................................64 Network Segregation ...............................68 Dedicated Identity Acquisition Gateway .......................................................................................66 Distributed Enterprise with Branch Offices ..................................................79 Configuring Deployed Identity Agents ..................66 Wireless Campus.........................................................................................................................................................................................................................................................................90 Index .86 DNS Based Configuration ..............84 Option Comparison..............................................................................59 Checking the Bridge Configuration.........Prepackaging Identity Agent Installation ........................................................................[Properties] Section ..............................................................................................77 Background ..........................................................................................62 Deployment Scenarios .........................................................................................62 Perimeter Security Gateway with Identity Awareness .....................................................................................58 Configuring Clusters in Bridge Mode ....................................................................................................................................77 Configuring Installation ................................................................................................................................................................85 AD Based Configuration ...................................................................................................................81 Sample INI File .........60 Configuring Cluster and Bridge Support ........77 Using the cpmsi_tool.61 Deploying a Test Environment ..................73 AD Configuration .................................................................................................................................71 Overview ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................84 File Name Based Server Discovery ...............................................exe.....................................82 Server Discovery and Trust ........................................................................................................................................................................61 Testing Identity Sources ....83 Introduction ......................................................58 Preparing Clusters with a Bridge ...............69 Kerberos SSO Configuration .......................................................61 Testing Identity Agents ......60 Configuring the Cluster ...................................................73 SmartDashboard Configuration ........................................................................................................71 How SSO Operates ...................93 .........88 Remote Registry .....................................................60 Configuring the External Identity Awareness Gateway ............................75 Prepackaging Identity Agents ..............63 Large Scale Enterprise Deployment ......56 Advanced Deployment ...................77 Custom Identity Agent msi ...........................57 Deployment Options ...............................................................[AddFiles] Section ...62 Data Center Protection ......................................................................................................................57 Introduction .......72 SSO Configuration............71 References ................................................................................................................................................................................89 Prepackaging Identity Agents ......................................................................[Features] Section ...............................................................................................................................78 Configuring Installed Features ......................
it shows the IP address of the user or machine with a name. Page 6 . This lets you enforce access and audit data based on identity. It is currently available on the Firewall blade and Application Control blade and will operate with other blades in the future. It is applicable for both Active Directory and non-Active Directory based networks as well as for employees and guest users. Identity Awareness is an easy to deploy and scalable solution. this lets you create firewall rules with any of these properties. Identity Awareness lets you easily configure network access and auditing based on network location and: The identity of a user The identity of a machine When Identity Awareness identifies a source or destination.Chapter 1 Getting Started With Identity Awareness In This Chapter Introduction Deployment Identity Awareness Scenarios 6 12 13 Introduction Traditionally. firewalls use IP addresses to monitor traffic and are unaware of the user and machine identities behind those IP addresses. Identity Awareness removes this notion of anonymity since it maps users and machine identities. For example. You can define a firewall rule for specific users when they send traffic from specific machines or a firewall rule for a specific user regardless of which machine they send traffic from.
Identity Awareness also lets you see user activity in SmartView Tracker and SmartEvent based on user and machine name and not just IP addresses. machines and network locations as one object. you use Access Role objects to define users. 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. Depending on those considerations. Getting Started With Identity Awareness Page 7 .Introduction In SmartDashboard. you can configure Identity Awareness to use one identity source or a combination of identity sources ("Choosing Identity Sources" on page 41).
No installation is necessary on the clients or on the Active Directory server. 1. It is based on Windows Management Instrumentation (WMI).Firewall Rule Base Example The steps listed in the example align with the numbers in the image below. or accesses an Intranet portal. The Security Gateway communicates directly with the Active Directory domain controllers and does not require a separate server. AD Query AD Query is an easy to deploy. How AD Query Operates .Introduction Source AD Query Description Gets identity data seamlessly from Microsoft Active Directory (AD) Recommended Usage Identity based auditing and logging Leveraging identity in Internet application control Basic identity enforcement in the internal network Identity based enforcement for non-AD users (non-Windows and guest users) For deployment of Identity Agents Leveraging identity for Data Center protection Protecting highly sensitive servers When accuracy in detecting identity is crucial Deployment Considerations Easy configuration (requires AD administrator credentials) Preferred for desktop users Only detects AD users and machines Captive Portal Sends unidentified users to a Web portal for authentication Used for identity enforcement (not intended for logging purposes) Identity Agent A lightweight endpoint agent that authenticates securely with Single Sign-On (SSO) See Choosing Identity Sources (on page 41). The AD Query option operates when: An identified asset (user or machine) tries to access an Intranet resource that creates an authentication request. shares a network drive. The Security Gateway registers to receive security event logs from the Active Directory domain controllers. reads emails through Exchange. 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. a standard Microsoft protocol. A user logs in to a desktop computer using his Active Directory credentials. AD Query is selected as a way to acquire identities. In this way. unlocks a screen. Identity aware gateways can share the identity information that they acquire with other identity aware gateways. Getting Started With Identity Awareness Page 8 . It is based on Active Directory integration and it is completely transparent to the user. 2. when a user logs in. clientless identity acquisition method. For example. users that need to pass through several enforcement points are only identified once. See Advanced Deployment (on page 57) for more information.
The Active Directory DC sends the security event log to the Security Gateway. When these criteria are true. they might be able to access the resource. For guest users. But if users are identified. enter required credentials. When users try to access a protected resource. Getting Started With Identity Awareness Page 9 . 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. 4.Introduction 3. Captive Portal acquires the identities of users. machine name and source IP address). they get a web page that must fill out to continue. Unidentified users cannot access that resource because of rules with access roles in the Firewall / Application Rule Base. 5. The Security Gateway extracts the user and IP information (user name@domain. It is a simple method that authenticates users through a web interface before granting them access to Intranet resources. Captive Portal The Captive Portal is a tool that acquires identities from unidentified users. From the Captive Portal users can: Enter an existing user name and password if they have them. 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.
Check Point internal credentials. Identity Awareness does not recognize him and redirects the browser to the Captive Portal. 3. A user wants to access the Internal Data Center. The credentials can be AD or other Check Point supported authentication methods. 4. The credentials are verified. Configure this in the Portal Settings. Getting Started With Identity Awareness Page 10 . How Captive Portal Operates . such as LDAP. 1. 2. The user can now go to the originally requested URL. In this example they are verified with the AD server. The user enters his regular office credentials. or RADIUS.Introduction Click a link to download an Identity Awareness agent.Firewall Rule Base The steps listed in the example align with the numbers in the image below. 5.
Example This is how a user downloads the Identity Agent from the Captive Portal: 1. A user logs in to his PC with his credentials and wants to access the Internal Data Center. If you do not want to use SSO. If installed by a user without administrator permissions. users enter their credentials manually. The Full agent performs packet tagging and machine authentication. For more information. 2.does not require administrator permissions for installation. Custom .users stay automatically identified when they move between networks.a customized installation package.all necessary configuration is done by administrators and does not require user input. Seamless connectivity . Connectivity through roaming . 3. It contains a link that he can use to download the Identity Agent.transparent authentication using Kerberos Single Sign-On (SSO) when users are logged in to the domain.Introduction Identity Agents Identity Agents are dedicated client agents installed on users' computers that acquire and report identities to the Security Gateway. The Security Gateway sends a page that shows the Captive Portal to the user. You can let them save these credentials.you can use the patented packet tagging technology to prevent IP Spoofing. Getting Started With Identity Awareness Page 11 . The Security Gateway enabled with Identity Awareness does not recognize him and sends him to the Captive Portal. it will automatically revert to installing the Light agent. How You Download an Identity Agent .requires administrator permissions for installation. Added security . Cannot be configured with packet tagging or machine authentication. Identity Agents also gives you strong (Kerberos based) user and machine authentication. see the Prepackaging Identity Agents (on page 77). Light . as the client detects the movement and reconnects. 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). Using Identity Agents gives you: User and machine identity Minimal user intervention . There are 3 types of Identity Agents: Full .
You can have one or more gateways acquire identities and share them with the other gateways. Deploy on branch office gateways and central gateways. 5. The user is authenticated and the Security Gateway sends the connection to its destination according to the Firewall Rule Base. In Bridge mode it can use an existing subnet with no change to the hosts' IP addresses. you can deploy a gateway cluster in Active-Standby (HA) or Active-Active (LS) modes. Identity awareness supports ClusterXL HA and LS modes. the user is automatically connected. The user downloads the Identity Agent from the Captive Portal and installs it on his PC.Deployment 4. such as data centers. This can be in addition to on the perimeter gateway but does not require a perimeter gateway. Identity Awareness can be deployed in Bridge mode or Route mode. To protect internal data centers. For redundancy. The Identity Agent client connects to the Security Gateway. Common scenarios include: Deploy on your perimeter gateway and data center gateway. You can also share identities between gateways managed in different Multi-Domain Servers. It is frequently used in conjunction with Application Control. Deployment Identity Awareness is commonly enabled on the perimeter gateway of the organization. If you deploy Identity Awareness on more than one gateway. Getting Started With Identity Awareness Page 12 . Identity Awareness can be enabled on an internal gateway in front of internal servers. Deploy on several data center gateways. In Route mode the gateway acts as a router with different subnets connected to its network interfaces. you can configure the gateways to share identity information. 6. If SSO with Kerberos is configured.
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. 3.Identity Awareness Scenarios Identity Awareness Scenarios This section describes scenarios in which you can use Identity Awareness to let users access network resources. you are configuring clientless employee access for all Active Directory users. To enforce access options. He wants to move around the organization and continue to have access to the HR Web Server.217. To make this scenario work. but that limits him to operating it only from his desk. 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. Thus.3.3. Checks SmartView Tracker to make sure the system identifies John Adams in the logs. Getting Started With Identity Awareness Page 13 . Sees how the system tracks the actions of the access role in SmartView Tracker.168. He received a laptop and wants to access the HR Web Server from anywhere in the organization. Active Directory users that log in and are authenticated will have seamless access to resources based on Firewall Rule Base rules. make rules in the Firewall Rule Base that contain access role objects. machines and network locations as one object. The current Rule Base contains a rule that lets John Adams access the HR Web Server from his laptop with a static IP (192. When you set the AD Query option to get identities. The last scenario describes the use of Identity Awareness in an Application Control environment. The first 3 scenarios describe different situations of acquiring identities in a Firewall Rule Base environment. Scenario: Laptop Access John Adams is an HR partner in the ACME organization. 2. Let's examine a scenario to understand what AD Query does. Enables Identity Awareness on a gateway.217). ACME IT wants to limit access to HR servers to designated IP addresses to minimize malware infection and unauthorized access risks. 4. the gateway policy permits access only from John's desktop which is assigned a status IP address 192. An access role object defines users. The IT department gave the laptop a static IP address. the IT administrator does these steps: 1. selects AD Query as one of the Identity Sources and installs the policy.168.
This log entry shows that the system maps the source IP to the user John Adams from CORP. This can take some time and depends on user activity. Note .168. This uses the identity acquired from AD Query.3.COM.AD Query maps the users based on AD activity. If John Adams is not identified (the IT administrator does not see the log).Identity Awareness Scenarios User Identification in the Logs The SmartView Tracker log below shows how the system recognizes John Adams as the user behind IP 192. Getting Started With Identity Awareness Page 14 .ACME.217. he should lock and unlock the computer.
Let's examine some scenarios to understand what the Captive Portal does and the configuration required for each scenario. However.Identity Awareness Scenarios Using Access Roles To let John Adams access the HR Web Server from any machine. To do this. she can enter her AD credentials in the Captive Portal and then get the same access as on her office computer. Unmanaged. she cannot identify seamlessly with AD Query. Getting Started With Identity Awareness Page 15 . guest users such as partners or contractors. Her access to resources is based on rules in the Firewall Rule Base. She wants to access the internal Finance Web server from her 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. If unidentified users try to connect to resources in the network that are restricted to identified users. 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. they are automatically sent to the Captive Portal. it is necessary for the administrator to change the current rule in the Rule Base. it is necessary to create an access role ("Creating Access Roles" on page 26) for John Adams that includes the specific user John Adams from any network and any machine. The IT administrator can then remove the static IP from John Adam's laptop and give it a dynamic IP. Scenario: Recognized User from Unmanaged Device The CEO of ACME recently bought her own personal iPad. 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.
Browses to the Finance server from her iPad. 3. right-click to create an Access Role. Create a new rule in the Firewall Rule Base to let Jennifer McHanry access network destinations. Click OK. 4. make sure that Name and password login is selected. 3. 2. 7. From the Source of the rule. select Specific users and choose Jennifer McHanry. b) In the Users tab. 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. Select the Redirect http connections to an authentication (captive) portal. 6. 5. Getting Started With Identity Awareness Page 16 . In the Portal Settings window in the User Access section. Right-click the Action column and select Edit Properties.Identity Awareness Scenarios Required SmartDashboard Configuration To make this scenario work. a) Enter a Name for the Access Role. User Experience Jennifer McHanry does these steps: 1. Enable Identity Awareness on a gateway and select Captive Portal as one of the Identity Sources. A Welcome to the network window opens. The Action Properties window opens. Note: redirection will not occur if the source IP is already mapped to a user checkbox. d) Click OK. the IT administrator must: 1. She can successfully browse to the Finance server. 2. She enters her usual system credentials in the Captive Portal. The Access Role is added to the rule. Select accept as the Action.
email address. Scenario: Guest Users from Unmanaged Device Guests frequently come to the ACME company. the Captive Portal opens.Identity Awareness Scenarios User Identification in the Logs The SmartView Tracker log below shows how the system recognizes Jennifer McHanry from her iPad. Enable Identity Awareness on a gateway and select Captive Portal as one of the Identity Sources. the IT administrator must: 1. 2. She makes a rule in the Firewall Rule Base to let unauthenticated guests access the Internet only. 3. Guests enter their name. For how long users can access the network resources. In the Unregistered Guest Login Settings window. configure: The data guests must enter. Amy.Settings. company. This uses the identity acquired from Captive Portal. the IT administrator configures the Captive Portal to let unregistered guests log in to the portal to get network access. Getting Started With Identity Awareness Page 17 . They then agree to the terms and conditions written in a network access agreement. While they visit. Click Unregistered guest login . the CEO wants to let them access the Internet on their own laptops. Afterwards they are given access to the Iinternet for a specified period of time. and phone number in the portal. make sure that Unregistered guest login is selected. This log entry shows that the system maps the source "Jennifer_McHanry" to the user name. In the Portal Settings window in the User Access section. If a user agreement is required and its text. When guests browse to the Internet. Required SmartDashboard Configuration To make this scenario work. 4.
Browses to an internet site from her laptop. 3. The Access Role is added to the rule. create a rule that identified users can access the internet from the organization. Note: redirection will not occur if the source IP is already mapped to a user checkbox. User Identification in the Logs The SmartView Tracker log below shows how the system recognizes a guest. The Captive Portal opens because she is not identified and therefore cannot access the Internet. She enters her identifying data in the Captive Portal and reads through and accepts a network access agreement.Identity Awareness Scenarios 5. Amy. (iii) In the Users tab. select Specific users and choose Unauthenticated Guests. (iii) In the Users tab. the IT administrator wants to leverage the use of Identity Agents so: Getting Started With Identity Awareness Page 18 . (v) The Access Role is added to the rule. right-click to create an Access Role. (vi) Select accept as the Action. She can successfully browse to the Internet for a specified period of time. (ii) Enter a Name for the Access Role. 2. In this case. (vii) Right-click the Action column and select Edit Properties. (v) Click OK. (i) From the Source of the rule. 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. b) Create a rule to let Unauthorized Guests access only the internet. (i) From the Source of the rule. A Welcome to the network window opens. (viii) Select the Redirect http connections to an authentication (captive) portal. Create two new rules in the Firewall Rule Base: a) If it is not already there. This log entry shows that the system maps the source IP address with the user's identity. User Experience From the perspective of a guest at ACME. (iv) Click OK. right-click to create an Access Role. (ix) Click OK. she does these steps: 1. (iv) In the Machines tab select Any machine if guests will access the network from their own machines or Specific machines to choose a computer that they will use. (ii) Enter a Name for the Access Role. select All identified users. The current Rule Base uses static IP addresses to define access for the Finance department. the identity is "guest" because that is how the user is identified in the Captive Portal. The Action Properties window opens.
Getting Started With Identity Awareness Page 19 . Click the Captive Portal Settings button.Full option. A rule in the Rule Base with an access role for Finance users. Configure Kerberos SSO ("Kerberos SSO Configuration" on page 71). you can set Identity Agent download for a specific group ("Configuring Agent Deployment for User Groups" on page 37). She needs to deploy the Full Identity Agent so she can set the IP spoofing protection. Required SmartDashboard Configuration To make this scenario work. select Name and password login. the IT administrator must: 1. User Experience A Finance department user does this: 1. Install policy. Agent deployment for the Finance department group from the Captive Portal. f) Click OK. 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. After configuration and policy install. g) The Access Role is added to the rule. b) Enter a Name for the Access Role. Users that roam the organization will have continuous access to the Finance Web server. No configuration is necessary on the client for IP spoofing protection.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). 7. select Require users to download and select Identity Agent . 4. right-click to create an Access Role. 2. Enable Identity Awareness on a gateway and select Identity Agents and Captive Portal as Identity Sources. Note . select Specific users and add the Active Directory Finance user group. users that browse to the Finance Web server will get the Captive Portal and can download the Identity Agent. Access to the Finance Web server will be more secure by preventing IP spoofing attempts. select All identified users. In the Portal Settings window in the Users Access section. d) In the Users tab. She needs to configure: Identity Agents as an identity source for Identity Awareness. 5. c) In the Networks tab. 3. e) In the Machines tab.This configures Identity Agent for all users. select All identified machines and select Enforce IP spoofing protection (requires Full Identity Agent). 6. Alternatively. Amy wants Finance users to download the Identity Agent from the Captive Portal. Browses to the Finance Web server. from all managed machines and from all locations with IP spoofing protection enabled. In the Identity Agent Deployment from the Portal.
Click OK. The user clicks the link to download the Identity Agent. machine awareness. 2. Access roles ("Creating Access Roles" on page 26) to leverage machine awareness. They work together in these procedures: Getting Started With Identity Awareness Page 20 . End user interface protection so users cannot access the client settings. In this scenario. Note . the File Name server discovery method is used. 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. Acquiring Identities in Application Control Identity Awareness and Application Control can be used together to add user awareness. See Server Discovery and Trust (on page 37)for more details. The user automatically connects to the Finance Web server.The trust window opens because the user connects to the Security Gateway with Identity Awareness using the File name based server discovery option. See User Access (on page 33).Identity Awareness Scenarios The Captive Portal opens because the user is not identified and cannot access the server. A window opens asking the user to trust the server. The user automatically connects to the gateway. Let users defer client installation for a set time and ask for user agreement confirmation. and application awareness to the Check Point gateway. The user can successfully browse to the internet for a specified period of time. A Welcome to the network window opens. A link to download the Identity Agent is shown. See Server Discovery and Trust (on page 37) for more details on other server discovery methods that do not require user trust confirmation. 3.
In SmartView Tracker logs and SmartEvent events. To do this.Identity Awareness Scenarios Use Identity Awareness Access Roles in Application Control rules as the source or destination of the rule. You can use all the types of identity sources to acquire identities of users who try to access applications. with the tracking set to Log.com/documentation_download?ID=11658). See the R75 Application Control Administration Guide (http://supportcontent. It also shows Application Control data. 2. the IT department can add rules to block specific applications or track them differently in the Application Control policy to make it even more effective. the IT administrator must enable Application Control and Identity Awareness. Enables Identity Awareness on a gateway. Enables the Application Control blade on a gateway. This adds a default rule to the Application Control Rule Base that allows traffic from known applications. 3. selects AD Query as one of the Identity Sources. The SmartView Tracker and SmartEvent logs will then show identity information for the traffic. User identification in the Logs Logs related to application traffic in SmartView Tracker and SmartEvent show data for identified users. This SmartView Tracker log entry shows that the system maps the source IP address with the user's identity. Required SmartDashboard Configuration To make this scenario work. Next. Installs the policy. the IT administrator does these steps: 1. you can see which user and IP address accesses which applications.checkpoint. Scenario: Identifying Users in Application Control Logs The ACME organization wants to use Identity Awareness to monitor outbound application traffic and learn what their employees are doing. Getting Started With Identity Awareness Page 21 .
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.
select Identity Awareness. You can use the wizard to configure one Security Gateway that uses the AD Query and Captive Portal for acquiring identities. select Enable Identity Awareness. You cannot use the wizard to configure a multiple gateway environment or to configure client acquisition (another method for acquiring identities). On the General Properties page > Additional Features section. 3. On the Identity Awareness page. The Identity Awareness Configuration wizard opens. Double-click the gateway on which to enable Identity Awareness. You can use SmartView Tracker and SmartEvent to see the logs for user and machine identity. Log in to SmartDashboard.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. expand the Check Point branch. When you complete the wizard and install a policy. 2. the system is ready to monitor Identity Awareness. To enable Identity Awareness: 1. From the Network Objects tree. a wizard opens. Page 23 . Or From the Gateway Properties tree. select Identity Awareness. 4.
go to the Firewall tab > Servers and OPSEC Applications tab in the objects tree > LDAP Account Unit.Lets the Security Gateway seamlessly identify Active Directory users and computers. When SmartDashboard is part of the domain.Sends users to a Web page to acquire identities from unidentified users. The LDAP Account Unit name syntax is: <domain name>_ _ AD Configuring Identity Awareness Page 24 . The Integration With Active Directory window opens.We highly recommend that you go to the LDAP Account Unit and make sure that only necessary domain controllers are in the list. See Choosing Identity Sources (on page 41). Captive Portal . the system creates an LDAP Account Unit with all of the domain controllers in the organization's Active Directory. Note . Click Next. These options set the methods for acquiring identities of managed and unmanaged assets.Enabling Identity Awareness on the Security Gateway 5. SmartDashboard suggests this domain automatically. To view/edit the LDAP Account Unit object. the LDAP account unit that the system creates contains only the domain controller you set manually. If you select this domain. you must add them at a later time manually to the LDAP Servers list. If it is necessary for AD Query to fetch data from other domain controllers. AD Query . 6. If you create a new domain. delete them from the LDAP Servers list. Select one or both options. If AD Query is not required to operate with some of the domain controllers.
2. 8. select the Active Directory to configure from the list that shows configured LDAP account units or create a new domain. select a URL for the portal. where unidentified users will be directed. The IP address selected by default is the <gateway's main IP address>/connect.2. Important .20.2/DLP Mobile Access Portal . For example: Identity Awareness Captive Portal . If you selected to use Captive Portal and do not wish to configure Active Directory.2. password and domain controller credentials.Enabling Identity Awareness on the Security Gateway For example. Enter the Active Directory credentials and click Connect to verify the credentials. 11.2. select I do not wish to configure Captive Portal at this time and click Next. the Captive Portal Settings page opens. 10. 9. All IP addresses configured for the gateway show in the list. Click Next. From the Select an Active Directory list.10.For AD Query you must enter domain administrator credentials.2. The same IP address can be used for other portals with different paths. you need to enter a domain name.ACME. For Captive Portal standard credentials are sufficient. In the Captive Portal Settings page. CORP. username.1/connect DLP Portal .COM_ _ AD. 7.10. If you have not set up Active Directory.2. If you selected Captive Portal on the first page.2/sslvpn Configuring Identity Awareness Page 25 .
The Access Role window opens. By default. Select Policy > Install from the SmartDashboard menu. To view/edit the LDAP Account Unit object. Active Directory and / or Captive Portal become active. the portal is accessible only through internal interfaces.COM_ _ AD. When you set an Active Directory domain. To enforce Identity Awareness.ACME. We do not recommend that you make the portal accessible through external interfaces on a perimeter gateway. use these access role objects in the Rule Base. Access role objects define users. the system creates an LDAP Account Unit object for the Active Directory domain. network and machine or be general for a certain user from any network or any machine.Creating Access Roles 12. user groups or user branches. Click Next to complete the wizard and see what is configured. Creating Access Roles After you activate Identity Awareness. From the Users and Administrators tree. click Edit. The access role can be specified for a certain user. 15. go to the Firewall tab > Servers and OPSEC Applications tab in the objects tree > LDAP Account Unit. You can select specific users. Configuring Identity Awareness Page 26 . click Access Roles > New Access Role. To create an access role: 1. The LDAP Account Unit name syntax is: <domain name>_ _ AD For example. you can create access role objects. machines and network locations as one object. To change this. 13. CORP. Results of the Wizard These are the results of the wizard: Depending on the acquisition methods you set. 14. The Identity Awareness is Now Active page opens. Click Finish.
7. A window opens. In the Machines tab. A window opens.click and select a network. 3. Enter a Name and Comment (optional) for the access role. select one of these: Any user All identified users . Specific machines. 5. Click OK. You can search for Active Directory entries or select them from the list. Specific users -click . Select a Color for the object (optional). The access role is added to the Users and Administrators tree.includes any user identified by a supported authentication method (internal SmartDashboard users. 6. Active Directory users or LDAP users).Creating Access Roles 2. 4. In the Machines tab. select one of these: Any machine All identified machines . In the Users tab. select Enforce IP spoofing protection (requires full identity agent) if you want to enable the packet tagging feature. select one of these: Any network Specific networks . 8. Your selections are shown in the Machines node in the Role Preview pane. Your selections are shown in the Users node in the Role Preview pane.includes machines identified by a supported authentication method (Active Directory or LDAP machines). You can search for Active Directory entries or select them from the list.click . Your selection is shown under the Networks node in the Role Preview pane. Configuring Identity Awareness Page 27 . In the Networks tab.
it then goes on to the second rule and continues until it matches a rule. If all the conditions apply. After the user enters credentials. Important . 1 Source Finance_Dept (Access Role) Admin_IP Any Destination Service Action Accept (redirect to Captive Portal) Accept Drop Finance_Web_ Any Server Any Any Any Any 2 3 Example 1 . In rules with access roles. when the source identity is unknown and traffic is HTTP. When identity data for an IP is unknown and: To redirect http traffic to the Captive Portal: 1. All the rule’s fields match besides the source field with an access role. make sure to place the rule in the correct position in the Rule Base to avoid unwanted behavior. a redirect to the Captive Portal occurs. it can examine the rule for the next connection. the Action in the rule (Allow or Block) is enforced immediately and the user is not sent to the Captive Portal. it examines the packet against the first rule in the Rule Base. Click OK. there is no match and the next rule is examined.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. In a rule that uses an access role in the Source column. Note . you can add a property in the Action field to redirect traffic to the Captive Portal. If it does not match an access role. the gateway allows access to the Configuring Identity Awareness Page 28 . If the source identity is known. 2. 3. the traffic is redirected to the Captive Portal to get credentials and see if there is a match. After the system gets the credentials from the Captive Portal. the user is redirected to the Captive Portal. In rules with access role objects. it goes on to examine the next rule. Below is an example of a Firewall Rule Base that describes how matching operates: No. The action is set to redirect to the Captive Portal. The Action column shows that a redirect to the Captive Portal occurs.When you set the option to redirect http traffic from unidentified IP addresses to the Captive Portal. criteria matching operates like this: When identity data for an IP is known: If it matches an access role. The Action Properties window opens. the rule is applied and the traffic is accepted/dropped based on the action. If this property is added. When a Security Gateway receives a packet from a connection.If an unidentified Finance Dept user tries to access the Finance Web Server with http. right-click the Action column and select Edit Properties. If not all conditions apply. Note: redirection will not occur if the source IP is already mapped to a user checkbox. The connection is http.You can only redirect http traffic to the Captive Portal. Select the Redirect http connections to an authentication (captive) portal. If there is no match.
When you negate an access role. Negate and Drop When you negate a source or destination parameter. Drop rule. If a temporary employee is not identified when she accesses the system. In rules with access role objects. it examines the packet against the first rule in the Rule Base. when the source identity is unknown and traffic is HTTP. it goes on to examine the next rule. Example 2 . it means that the rule is applied to "all except for" the access role and unidentified entities. If the source identity is known. To prevent access to unidentified users. switch the order of rules 1 and 2 or add a network restriction to the access role. If this property is added. the packet is allowed. a redirect to the Captive Portal occurs despite rule number 2. Access is allowed based on rule number 1. it means that a given rule applies to all sources/destinations of the request except for the specified source/destination object. the user is redirected to the Captive Portal. When the object is an access role. she will have access to the Intranet Web Server. Access Role Objects Access Role objects can be used as a source and/or destination parameter in a rule. which identifies the user through the Captive Portal as belonging to the Finance Dept access role. a rule that allows file sharing between the IT department and the Sales department. Any. rule number 2 matches. 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 means that everyone (including unidentified users) can access the Intranet Web Server except for temporary employees. If there is no match. If no rule matches. After the system gets the credentials from the Captive Portal. criteria matching operates like this: When identity data for an IP is known: If it matches an access role. the rule is applied and the traffic is allowed/blocked based on the action. To let the administrator access the Finance Web Server without redirection to the Captive Portal. After the administrator is identified. 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 . For example. For example. the Action in the rule (Allow or Block) is enforced immediately and the user is not sent to the Captive Portal.Using Identity Awareness in the Application Control Rule Base Finance Web Server. When a Security Gateway receives a packet from a connection. it can examine the rule for the next connection. it goes on to the second rule and continues until it completes the Rule Base. If it does not match an access role. let's say that the below rule is positioned above the Any. you can add a property in the Action field to redirect traffic to the Captive Portal. In rules with access roles.If an unidentified administrator tries to access the Finance Web Server with http. this includes all unidentified entities as well.
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. Below is an example of an Application Control Rule Base that shows how criteria matching operates: No. there is no match and the next rule is examined. Example 2 . 2. If all the conditions apply. To redirect HTTP traffic to the Captive Portal: 1. the traffic is redirected to the Captive Portal to get credentials and see if there is a match. right-click the Action column and select Edit Properties. Furthermore. 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. Because the application is not HTTP. The connection protocol is HTTP. The Action column shows that a redirect to the Captive Portal occurs. This happens because the action is set to redirect to the Captive Portal. In the Source and Destination columns. you can use a network object together with an access role object. 3. traffic cannot be redirected to the Captive Portal. The Action Properties window opens. After entering credentials and being identified. In rule 3 there is also no match because the action is not set to redirect to the Captive Portal.An unidentified user that attempts to access the Remote Administration Tool matches rule 2. Select Redirect HTTP connections. If not all conditions apply. Configuring Identity Awareness Page 30 . Since none of the rules match. the user is granted access to the Remote Administration Tool.An unidentified user that browses to Gmail does not match rules 1 and 2 because of the application. the user is granted access to Gmail. This means you cannot have a rule that uses an access role in both the Source column and the Destination column. The action is set to redirect to the Captive Portal. the user is granted access according to rule number 1. Example 3 . but not the Source column. But the condition between them is "or" and not "and". different users experience different outcomes: Example 1 . you cannot use access roles in both the Source and Destination columns in the same Rule Base. When the criteria does not match any of the rules in the Rule Base: The traffic is allowed. Since none of the rules 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. In a rule that uses an access role in the Source column.An unidentified Finance user that attempts to access Salesforce is sent to the Captive Portal. Click OK.
A more advanced deployment is possible where the portal runs on a different gateway. This is the basic configuration. 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. To make the alias work. its URL shows below Captive Portal. Configuring Identity Awareness Page 31 . select Captive Portal to send unidentified users to the Captive Portal.yourcompany. it is not automatically blocked. This example shows rules that block temporary employees from accessing the Internet and allows access for identified employees. Access Settings Click Edit to open the Portal Access Settings window. it must be resolved to the main URL on your DNS server. Unlike the Firewall Rule Base. Configuring Captive Portal in SmartDashboard In the Identity Sources section of the Identity Awareness page. It is allowed.com can send users to the Captive Portal.Configuring Captive Portal in SmartDashboard Negate and Block Negate and block in the Application Control Rule Base operates similarly to Negate and drop (on page 29) in the Firewall Rule Base. Select Captive Portal and click Settings. From the Portal Settings window. 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. In this window you can configure: Main URL .The primary URL that users are redirected to for the Captive Portal.Click the Aliases button to Add URL aliases that are redirected to the main portal URL. Aliases . 2. To configure the Captive Portal settings: 1. ID. The default is that the Captive Portal is on the gateway. If you already configured the portal in the Identity Awareness Wizard or SmartDashboard. This rule makes sure that only identified users will be allowed access and attempts by unidentified users will be blocked. The gateway thus redirects unidentified users to the portal on the same gateway. if a connection does not match any of the rules. See the Deployment section for more details. For example.
The directory of internal users. Configure the labeled elements of the image below. Select the server from the list. User name and password . You might choose only one or two options if users are only from a specified directory or directories and you want to maximize gateway performance when users authenticate.Click Import to import a certificate for the portal website to use. Internal users .Select one method that known users must use to authenticate.Select one or more places where the gateway searches to find users when they try to authenticate.The directory of users who have external user profiles. The default is that all user directory options are selected. the portal uses a Check Point auto-generated certificate. Specific . User Directories .The directory of LDAP users. Customize Appearance Click Edit to open the Portal Customization window and edit the images that users see in the Captive Portal. Users are sent to the Captive Portal if they use networks connected to these interfaces. LDAP users .Users from all LDAP servers. You might have already configured this in the Identity Awareness Wizard. External user profiles . Accessibility . The options are based on the topology configured for the gateway.This can be configured internally or on an LDAP server. In this window you can configure: Authentication Method . Authentication Settings Click Settings to open the Authentication Settings window. Through all interfaces Through internal interfaces Including undefined internal interfaces Including DMZ internal interfaces According to the Firewall policy .Click Edit to select from where the portal can be accessed.Select this if there is a rule that states who can access the portal. Users with identical user names must log in with domain\user. RADIUS . See Server Certificates (on page 54) for more details. If you do not import a certificate.Users from an LDAP server that you select. Configuring Identity Awareness Page 32 .A configured RADIUS server.Configuring Captive Portal in SmartDashboard Certificate . Either: Any . This might cause browser warnings if the browser does not recognize Check Point as a trusted Certificate Authority.
Name and password login. The default title is Network Access Login. Select Is Mandatory for each field that guests must complete before they can get access to the Configuring Identity Awareness Page 33 .For how long can they access network resources before they have to authenticate again. Settings specified for a user group here override settings configured elsewhere in the Portal Settings.Paste the text of a customized agreement into the text box. Unregistered Guest Login Settings Click Settings to configure settings for guests. Access will be granted for xxx minutes . You can use HTML code. Customized agreement .Edit the table shown until it contains the fields that users complete in that sequence. You can only configure settings about Identity Agent deployment if Identity Agent is selected on the Identity Awareness page. This option is not selected by default because a user agreement is not usually necessary for known users. Access will be granted for xxx minutes .Let guests who are not known by the gateway access the network after they enter required data. If they can defer the Identity Agent installation and until when. If they must download the Identity Agent and which one. Click Edit to upload an agreement.Users are prompted to enter an existing username and password. Replace Company Name with the name of your company.Select this to use the standard agreement. Ask for user agreement .Configuring Captive Portal in SmartDashboard Label Number 1 Name Portal Title To do in GUI Enter the title of the portal. See the text in the Agreement preview. This will only let known users authenticate. Select Use my company logo for mobiles and Browse to select a smaller logo image for users who access the portal from mobile devices.You can require that users sign a user agreement. This name is used in the agreement. Name and Password Login Settings Click Settings to configure settings for known users after they enter their usernames and passwords successfully. Unregistered guests login . The options that you configure per user group are: If they must accept a user agreement. 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. Login Fields . Adjust portal settings for specific user groups . Ask for user agreement . Select Use my company logo and Browse to select a logo image for the portal. Select an agreement to use: Default agreement with this company name .Makes users sign a user agreement.You can add user groups and give them settings that are different from other users. Click Edit to choose an agreement and the End-user Agreement Settings page opens.For how long can they access network resources before they have to authenticate again.
To install the Full Identity Agent the computer must have administrator permissions. Before you configure Identity Agents. Configuring Identity Agents Identity Agents are dedicated client agents installed on users' computers that acquire and report identities to the Security Gateway. To add a new field. The Identity Agent identity source uses SSO to authenticate users when they enter their login credentials (Active Directory or other authentication server). Light Identity Agent or Custom Identity Agent.Before the Identity Agent can connect to a Security Gateway with Identity Awareness. you can configure that users must download the Identity Agent from the Captive Portal. The first field will show in the SmartView Tracker logs. It is not necessary to have administrator permissions to install the Light Identity Agent. see Kerberos SSO Configuration (on page 71). Agent Deployment from the Portal If Identity Agents is selected as a method to acquire identities. Until that date a Skip Identity Agent installation option shows in the Captive Portal. You can also let users choose not to install the Identity Agent immediately and instead wait until a specified later date. the Identity Agent must discover and trust the server that it connects to. Automatic authentication using Single Sign-On (SSO) .Select this if you want to give users flexibility to choose when they install the Identity Agent. If you do not use SSO.Configuring Identity Agents network.Identity Agents installed on endpoint computers authenticate users automatically when they log in to the domain using SSO. Users may defer installation until . Server discovery and trust .Light Identity Agent .Full Identity Agent . All necessary configuration is done by administrators and does not require user input. For the Full Identity Agent you can enforce IP spoofing protection.Select this to make users install the Identity Agent. The Custom Identity Agent is a customized installation package.Custom . enter it in the empty field and then click Add. You can configure one of five methods. Use the green arrows to change the sequence of the fields. users enter credentials in another window. To set up Kerberos. you must think about these elements: Identity Agent type . Require users to download . For the Full Identity Agent you can also manage asset detection if you define machines in access roles. Select the date by which they must install it. For more information. see Prepackaging Identity Agents (on page 77).You can deploy the Identity Agent for installation through the Captive Portal or use other means you use to deploy software in your organization. an inherent authentication and authorization protocol in Windows networks that is available by default on all Windows servers and workstations. Configuring Identity Awareness Page 34 . The system securely gets authentication data one time without making users authenticate manually (as is necessary with Captive Portal).Full Identity Agent. Installation deployment methods. Select which Identity Agent they must install. You get SSO with Kerberos.a customized installation package. Installation permissions . If this option is selected and the defer option is not selected. users will only be able to access the network if they install the identity agent. Identity Agent Types There are 3 Identity Agent types that you can install: Identity Agent .
the Identity Agent automatically detects the change. The Identity Agent tells the Security Gateway and you stay connected. the user bypasses identity access enforcement rules. Packet Tagging is a patent pending technology that prevents spoofed connections from passing through the gateway. IP change detection . you can enable Packet Tagging. Identity Agent Light Identity Agent Full Installation Elements Agent format Resident application Resident application + service + driver Administrator Installation permissions Upgrade permissions Security Features User identification Machine identification IP change detection Packet tagging None None None SSO No SSO Yes Yes Yes No Yes The installation file size is 7MB for both types and the installation takes less than a minute. 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. Packet tagging . The system opens a window for entering credentials. This table shows the similarities and differences of the Identity Agent types. By doing so. the Identity Agent uses username and password authentication with a standard LDAP server.A technology that prevents IP spoofing is available only for the Full Agent as it requires installing a driver. If you do not configure SSO or you disable it. 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. Packet Tagging for Anti-Spoofing IP Spoofing happens when an unauthorized user assigns an IP address of an authenticated user to an endpoint computer. To protect packets from IP spoofing attempts.You get machine identification when you use the Full Agent as it requires installing a service.Users that log in to the Active Directory domain are transparently authenticated (with SSO) and identified when using an Identity Agent. Machine identification . Configuring Identity Awareness Page 35 .Configuring Identity Agents User identification .When an endpoint IP address changes (interface roaming or DHCP assigns a new address).
You can also let users choose not to install the Identity Agent immediately and instead wait until a specified later date. 2.When you deploy the Full Identity Agent it is necessary for the user that installs the client to have administrator rights on the computer. To enable IP Spoofing protection: 1. In the Machines tab. 4. If the user does not have administrator permissions. Create an Access Role ("Creating Access Roles" on page 26). Make sure users have the full Identity Agent installed. 3. Note . Click OK. Identity Agent Deployment Methods There are 2 Identity Agent deployment methods: Using Captive Portal .you can configure that users must download the Identity Agent from the Captive Portal. select Enforce IP spoofing protection (requires full identity agent).Packet Tagging can only be set on computers installed with the Full Identity Agent. the Light Identity Agent is installed instead. The Success status indicates that a successful key exchange happened. the Identity Agent automatically knows if there are administrator permissions on the computer or not and installs itself accordingly. Configuring Identity Awareness Page 36 . Note .Configuring Identity Agents The Identity Awareness view in SmartView Tracker shows Packet Tagging logs. During installation.
The msi installation files (Light and Full) can be found in the \linux\windows directory on the supplied DVD. Click OK. For example. Click OK. The options that you configure for each user group are: If they must accept a user agreement. Settings specified for a user group here override settings configured elsewhere in the Portal Settings. 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.in /opt/CPNacPortal/htdocs/nac/nacclients/customAgent. select the Enable Identity Agent checkbox. select the Enable Identity Agent checkbox.msi Secure Platform installation CD . 2. From the Identity Awareness page. 4.in /linux/windows/Check_Point_Custom_Nac_Client.You can add user groups and give them settings that are different from other users. There are 5 server discovery and trust methods: Configuring Identity Awareness Page 37 . Server Trust refers to the procedure that: Makes sure that the Identity Agent connects to a genuine Security Gateway with Identity Awareness. If they can defer the Identity Agent installation and until when. If you select this option and you do not select the defer option. users will can only access the network if they install the Identity Agent. For example. 4. The most basic method is to configure one server. select the Require users to download checkbox to make users install the Identity Agent. Configuring Agent Deployment for User Groups When necessary. There are several methods you can use to configure this. an attempt to launch a Man-in-the-middle attack. You can find a customizable msi version of the Identity Agent (for distribution via a software distribution tool) in these places: Installed Security Gateway . 3. 5. Select Captive Portal and click Settings. select Users may defer installation until. Select which Identity Agent they must install. From the Portal Settings window. 5. 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. if you have a group of mobile users that roam and it is necessary for them to stay connected as they move between networks. Select Adjust portal settings for specific user groups . Select the date by which they must install it. To configure Identity Agent deployment for user groups: 1.msi For more information. Select Name and password login and click Settings. Another method is to deploy a domain wide policy of connecting to a Security Gateway with Identity Awareness based on the Identity Agent client's current location. Trust is verified by comparing the server fingerprint calculated during the SSL handshake with the expected fingerprint.you can deploy the Identity Agent with distribution software. you can configure specific groups to download the Identity Agent. see Prepackaging Identity Agents (on page 77). 2. Makes sure that the communication between the Identity Agent and the Security Gateway with Identity Awareness is not being tampered with. Select Captive Portal and click Settings. Configuring Agent Deployment from Captive Portal To configure Identity Agent deployment from Captive Portal: 1.Configuring Identity Agents Using distribution software . From the Identity Awareness page. 3. If they must download the Identity Agent and which one.
configure: Agent Access Authentication Settings Session details Agent Upgrades Agent Access Click Edit to select from where the Identity Agent can be accessed. you can deploy the server addresses and trust data using a dedicated "Distributed Configuration" tool. You can deploy these values before installing the client (by GPO. DNS SRV record based server discovery – You can configure the Security Gateway with Identity Awareness addresses in the DNS server. PrePackaging – You can create a prepackaged version of the client installation that comes with the Security Gateway with Identity Awareness IP and trust data. users will have to manually trust the server (a trust window opens). see Server Discovery and Server Trust ("Server Discovery and Trust" on page 83). From the Identity Agents Settings window. AD based configuration – If the Identity Agent computers are members of an Active Directory domain.Configuring Identity Agents File name based server configuration . Users can communicate with the servers if they use networks connected to these interfaces.If no other method is configured (out of the box situation). Select Identity Agents and click Settings. 2. the Identity Agent uses this IP for the Security Gateway with Identity Awareness. 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. select Identity Agents to configure Identity Agent settings. or any other method that lets you control the registry remotely). users will have to manually trust the server (a trust window opens). Remote registry – All client configuration resides in the registry. Configuring Identity Awareness Page 38 . During installation. When you use this method. The options are based on the topology configured for the gateway. For more details. Configuring Identity Agents in SmartDashboard In the Identity Sources section of the Identity Awareness page. Because DNS is not secure. This includes the Identity Server addresses and trust data. To configure the Identity Agent settings: 1.
In this window you can configure: Authentication Method . Session Configure data for the logged in session using the Identity Agent. Agent Upgrades Configure data for Identity Agent upgrades.When SSO is not enabled.A configured RADIUS server. External user profiles .Select one or more places where the gateway searches to find users when they try to authenticate. this is irrelevant.The directory of internal users. RADIUS . Select the server from the list. User Directories . Installed Agents Versions . You might choose only one or two options if users are only from a specified directory or directories and you want to maximize gateway performance when users authenticate.click the button to show the Identity Agent versions installed in the system. The default is that all user directory options are selected. Check agent upgrades for . Internal users .the Identity Agent is accessible through interfaces associated with source networks that appear in access rules used in the Firewall policy. Lower values affect bandwidth and network performance. Authentication Settings Click Settings to open the Authentication Settings window. Keep agent settings after upgrade . you can let users save the passwords they enter in the Identity Agent login window.Users from an LDAP server that you select. When using SSO.the system will only upgrade versions that are no longer compatible. Agents send keepalive every X minutes . Either: Any . LDAP users . Specific . Configuring Identity Awareness Page 39 .For how long can users access network resources before they have to authenticate again. Upgrade only non-compatible versions .Select one method that known users must use to authenticate.This can be configured internally or on an LDAP server.settings made by users before the upgrade are saved.Configuring Identity Agents Through all interfaces Through internal interfaces Including undefined internal interfaces Including DMZ internal interfaces According to the Firewall policy . Users with identical user names must log in with domain\user. The keepalive is used as the server assumes the user logged out if it is not sent.The interval at which the Identity Agent sends a keepalive signal to the Security Gateway. Upgrade agents silently (without user intervention) . User name and password .You can select all users or select specific user groups that should be checked for agent upgrades. Users should reauthenticate every XXX minutes .The directory of LDAP users.the Identity Agent is automatically updated in the background without asking the user for upgrade confirmation. Allow user to save password .The directory of users who have external user profiles.Users from all LDAP servers.
Enter the Active Directory credentials and click Connect to verify the credentials. select Add Identity to logs received from non-identity aware gateways. Important . you need to enter a domain name. 6. Log in to SmartDashboard. the LDAP account unit that the system creates contains only the domain controller you set manually. To view/edit the LDAP Account Unit object. If it is necessary for AD Query to fetch data from other domain controllers.We highly recommend that you go to the LDAP Account Unit and make sure that only necessary domain controllers are in the list. The LDAP Account Unit name syntax is: <domain name>_ _ AD For example. If you create a new domain. The data extracted from AD is stored in an association map on the Log Server. right-click Check Point and select the gateway with the Log Server. Click Finish. password and domain controller credentials. you must add them at a later time manually to the LDAP Servers list. From the Select an Active Directory list. select Identity Awareness. With Identity Awareness administrators can analyze network traffic and security-related events better. To enable Identity Awareness on the Log Server: 1. the server gets the user and machine name from the association map entry that corresponds to the source IP address. 3. Configuring Identity Awareness Page 40 .For AD Query you must enter domain administrator credentials. Get the Active Directory administrator's credentials.COM_ _ AD. From the Network Objects tree. When Security Gateways generate a Check Point log entry and send it to the Log Server. delete them from the LDAP Servers list. Note . 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. CORP. SmartDashboard suggests this domain automatically. select the Active Directory to configure from the list that shows configured LDAP account units or create a new domain. go to the Firewall tab > Servers and OPSEC Applications tab in the objects tree > LDAP Account Unit. 7. you are incorporating user and machine identification into Check Point logs. If you select this domain.ACME. 5. username. When SmartDashboard is part of the domain. From the Gateway Properties tree.Configuring Identity Awareness for a Log Server Configuring Identity Awareness for a Log Server When you configure Identity Awareness for a Log Server. The Integration With Active Directory window opens. 4. 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. It then adds this identity aware information to the log. the system creates an LDAP Account Unit with all of the domain controllers in the organization's Active Directory. 2. On the Identity Awareness page. The Identity Awareness Configuration wizard opens. Click Next. If you have not set up Active Directory. If AD Query is not required to operate with some of the domain controllers.
subdomain). but you then must make additional changes as listed below in the LDAP Account Unit. Identity Agents and Captive Portal . This automatically creates an LDAP Account Unit. This section presents some examples of how to choose identity sources for different organizational requirements. For Data Center protection .set the AD Query and Captive Portal identity sources. For logging and auditing with basic enforcement . you can choose to set them separately or as combinations that supplement each other. Note .select the Add identity to logs option on the Identity Awareness page. The AD Query finds all AD users and machines. Users that are not identified encounter redirects to the Captive Portal. Page 41 .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. It also serves as a fallback option if AD Query cannot identify a user. The Captive Portal is used for distributing the Identity Agent.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.When most users are desktop users (not remote users) and easy deployment is important. For logging and auditing only .When a high level of security is necessary. You can use the Identity Awareness Configuration Wizard to define one of the subdomains. The Captive Portal identity source is necessary to include all non-Windows users. You must manually create all other domains you want Identity Awareness to relate to from Servers and OPSEC Applications > Servers > New > LDAP Account Unit. IP spoofing protection can be set to prevent packets from being IP spoofed.these are some identity source options: AD Query and Captive Portal . Depending on your organization's requirements.e. For Application Control . Advanced AD Query Configuration Configuring Identity Awareness for a Domain Forest (Subdomains) You need to create a separate LDAP Account Unit for each domain in the forest (i.enable Identity Awareness on the gateway and select AD Query as the identity source.
For each domain controller that is to be ignored. An Enterprise administrator account that is a member of the Enterprise Admins group in the domain. This is configured in the SmartDirectory (LDAP) page of the Gateway Properties.DC=DOMAIN_SUFFIX to DC=SUB_DOMAIN_NAME. in the LDAP Account Unit go to LDAP Server Properties tab > Add > Username. If you use an Enterprise administrator.Advanced AD Query Configuration When you create an LDAP Account Unit for each domain in the forest.DC=local Specifying Domain Controllers per Security Gateway An organization's Active Directory may have several sites. if the domain is ACME. In LDAP Server Properties tab > Add > Login DN . enter the administrator's name as domain\user.DC=DOMAIN_SUFFIX. where each site has its own domain controllers that are protected by a Security Gateway.ACME. 2.DC=DOMAIN_NAME. When all of the domain controllers belong to the same Active Directory. 3. In Objects Management tab > Branches in use .COM and the subdomain is SUB.COM\John_Doe Note . a single LDAP Account Unit is created in SmartDashboard. then for the Enterprise administrator John_Doe enter in the Username field: ACME.COM.In the wizard this is the Username field. you may want to configure each Security Gateway to communicate with only some of the domain controllers.DC=ACME.Edit the base DN from DC=DOMAIN_NAME.add the login DN. When AD Query is enabled on Security Gateways. note the instructions for these fields: 1.DC=local to DC=SUB. Identity Sources Page 42 . For example. For example. change DC=ACME. Make sure the username is one of these: A Domain administrator account that is a member of the Domain Admins group in the subdomain. the default priority of the Account Unit must be set to a value higher than 1000.
let's say that the LDAP Account Unit ad. Identity Sources Page 43 . 3. 2. From the Network Objects tree. right-click Check Point and select the Security Gateway. 5.mycompany.Advanced AD Query Configuration For example. On the Security Gateway we want to enable AD Query only for domain controllers dc2 and dc3. Click Selected Account Units list and click Add. select SmartDirectory (LDAP).com has 5 domain controllers. 4. Log in to SmartDashboard. Create an environment variable named CP_SHOW_SMARTDIRECTORY=0 on the computer that runs SmartDashboard. From the Gateway Properties tree. To specify domain controllers per Security Gateway: 1. This means that all other domain controllers must be set to a priority higher than 1000 in the gateway properties.
Select your Account Unit. 7. Identity Sources Page 44 . dc4 and dc5.Advanced AD Query Configuration 6. Clear the Use default priorities checkbox and set the priority 1001 to dc1.
AD Query does not distinguish between application service accounts on a user's machine and the actual user's account. For example. Checking the Status of Domain Controllers You can make sure that the domain controllers are set properly by using the adlog CLI. Before you can make this assumption. Multiple accounts can be connected to the same IP address. 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. Notifications are not sent when a user logs out as the Active Directory is not aware of this. For example. Click OK. Identity Sources Page 45 . If the user does not access an Intranet resource that requires authentication after logging in. On average. etc.). you can exclude "dummy" user names used for automatic actions or services running on endpoint computers (anti-virus. Install policy.Advanced AD Query Configuration 8. backup. When using AD Query you must be aware of its limitations: When the defined timeout passes (12 hours by default). the user will no longer have permissions after the timeout period. when a Helpdesk administrator logs on to install a program for a user. The CLI command is adlog a dc. users access resources every 30 minutes that create authentication requests. or shares a network drive. unlocks a screen. a user sitting at the same computer with the same IP address originally authenticated. user B will be considered the user connected to the computer. When the administrator logs out. a user logs in. permissions are no longer applicable. For example. The system receives a security event log when a user or machine accesses a network resource. 9. 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. User B will then only have his permissions and not user A's permissions. the user will get the Helpdesk administrator's permissions plus his own permissions until the timeout. you can increase the default time (Check Point Gateway Properties > Identity Awareness > Active Directory Query Settings). it is necessary to exclude any service accounts used by user computers. 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. usually this is not a problem. To prevent this you can exclude irrelevant accounts ("Excluding Users" on page 46) from being logged. You can see the domain controllers that the Security Gateway is set to communicate with as well as the domain controllers it ignores. This happens because IP permissions are kept until the timeout value passes and Identity Awareness does not detect user logs out. If necessary. Resulting logs show that multiple accounts are logged in on the same IP. When this happens. if user A logs out before the timeout and user B logs in. For example. For example.
The amounts vary according to the applications running in the network.). Click OK. This is the gateway that gets identities from a given domain controller. 3.25 Mbps per each 1000 users. All other gateways to get identities from the gateway that acquires identities from the given domain controller. type the name or name pattern of the Active Directory accounts to ignore. In the Excluded Users / Machines section. 3. The LDAP Account Unit object is found in the Servers table. 2. Performance Bandwidth between the Log server and Active Directory Domain Controllers The amount of data transferred between the Log server and domain controllers depends on the amount of events generated. backup. select Settings for Active Directory Query. Use dbedit or GuiDBEdit tools to set the SupportUnicode attribute to true on the LDAP Account Unit object. If more than one gateway gets identities from the same AD server. See Excluding Users (on page 46). To set single user assumption: 1. To distinguish between application server accounts and a user's account: 1. The generated events include event logs and authentication events.Advanced AD Query Configuration Note . you must set an attribute. etc. 2. 4. Programs that have many authentication requests result in a larger amount of logs. Select Assume that only one user is connected per computer. From the Identity Awareness page. Click Add. You can also enter any regular expression via the syntax regexp:<regular expression>. they show up multiple times in logs.1 to 0. The observed bandwidth range varies between 0. Identity Sources Page 46 . 4. Non-English Language Support To support non-English user names on a Security Gateway enabled with Identity Awareness. we recommend that you set only one gateway to acquire identities from a given Active Directory domain controller per physical site. 5. See the Deployment Scenarios (on page 62) section for more details. Excluding Users You can distinguish between application service accounts on a user's machine and the actual user's account by excluding the service accounts. the AD server can become overloaded with WMI queries. These service accounts are used for automatic actions or services running on endpoint computers (anti-virus. Exclude any service accounts. From the Identity Awareness page. You do not need to set this attribute when Identity Awareness is enabled on the Security Management Server or Log Server. Click Advanced. Click OK. Multiple Gateway Environments In environments that use multiple gateways and AD Query.Another way to keep these issues to a minimum is to increase DHCP lease time. If you do not exclude them. Set these options on the Identity Awareness page: One gateway to share identities with other gateways. select Settings for Active Directory Query. You can use the * and ? wildcard characters to specify multiple users in a list entry.
enter the following information: a) Domain controller in the following format: \\<IP address>\root\cimv2 For example: \\11. Check SmartView Tracker and see if there are drops between a Security Gateway defined with AD Query (Source) and the domain controller (Destination). see Configuring the firewall (on page 48) and sk58881 (http://supportcontent. In the Connect window.company. 2.Advanced AD Query Configuration CPU Impact When using AD Query.com/solutions?id=sk58881).44\root\cimv2 b) Fully qualified AD user name.com\admin Identity Sources Page 47 .checkpoint. 3.33. 4. Click Start > Run.exe in the Run window. In the Windows Management Instrumentation Tester window. Ping the Security Gateway with Identity Awareness/log server from your domain controller. 3. Enter wbemtest. click Connect.22. If there are drops. the impact on the domain controller's CPU is less than 3%. 4. Troubleshooting If you experience connectivity problems between your domain controllers and Security Gateway with Identity Awareness/log servers. 2. Use wbemtest to Verify WMI To use the Microsoft wbemtest utility to verify that WMI is functional and accessible. For example: ad. Ping the domain controller from the Security Gateway with Identity Awareness/log server. 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. 1. Perform standard network diagnostics as required.
Obtain a domain administrator's credentials. right-click this service and select Start from the option menu. configure the Firewall to allow WMI traffic. Enter \\<domain controller IP>\c$ in the Run window. If the Windows Management Instrumentation Tester window re-appears with its buttons enabled. Locate the Windows Management Instrumentation service and verify that the service has started. b) You entered the incorrect user name or password. If the domain controller root directory appears. Save the policy and install it on Security Gateways.22. Configuring the Firewall If a Security Gateway is located between the Security Gateway with Identity Awareness/log server and the Active Directory controller. enter your domain administrator user name and password. 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. this indicates that your domain administrator account has sufficient privileges. 3. If it has not started.44\c$. 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. In SmartDashboard > Firewall. or you receive an error message. Check and retry. For example: \\11. this indicates that he is not defined as a domain administrator. Identity Sources Page 48 . 6. Click Connect. 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). 2. If the connection fails.msc in the Run window. WMI is fully functional. Click Start > Run. Click Start > Run. Enter services. 7.33. In the Logon window.Advanced AD Query Configuration c) Password 5. 4. Verify the WMI Service To verify if the WMI service is running: 1. Check Domain Administrator Credentials To verify your domain administrator credentials: 1. To create firewall rules for WMI traffic: 1. 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.
Select Policy > Install Database. these files must be configured again. you must configure language files.If there are connectivity issues on DCE RPC traffic after this policy is installed. make sure you installed the database. AD Query reads these events from the Security Event log: On Windows 2003 domain controllers . Install Database for a Log Server If you have configured Identity Awareness for a log server.php Identity Sources Page 49 . open the file: /opt/CPNacPortal/phpincs/utils/L10N. If the domain controller does not generate these events. Select the machine(s) on which you would like to install the database and click OK. 3.checkpoint. 673. Click Close when the script is complete. you can set the Captive Portal to String ID Help Mode. see sk37453 (http://supportcontent.672. The Install Database script appears. This includes changes to the text strings shown on the Captive Portal Network Login page. You can change English text that is shown on the Captive Portal to different English text through the SmartDashboard. 4770 Make sure you see the applicable events in the Event Viewer on the domain controller (My computer > Manage > Event Viewer > Security). make sure that the necessary event logs are being recorded to the Security Event Log. These language files are saved on the Security Gateway and cannot be upgraded. To help you understand what each string ID means. 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. This mode lets you view the string IDs used for the text captions. If you upgrade the Security Gateway. You can make changes to the default English language or edit files to show text strings in other languages. 4768... 4769. To configure other languages to show text strings in a specified language on the Captive Portal.4624.Advanced Captive Portal Configuration Note .. The Install Database window appears. Setting Captive Portal to String ID Help Mode To set the Captive Portal to String ID Help mode: 1.com/solutions?id=sk37453) for a solution. The changes are saved in the database and can be upgraded. Advanced Captive Portal Configuration Customizing Text Strings You can customize some aspects of the web interface. 2. 674 On Windows 2008 domain controllers . but do not see identities in logs. On the Security Gateway. refer to Microsoft Active Directory documentation for instructions on how to configure these events. To install the database: 1.
The Captive Portal opens showing the string IDs. 4. Replace the line // return $stringID. (delete the two backslashes that you see before the text return $stringID).php and put backslashes before the text return #stringID. Click Configure. Changing Portal Text in SmartDashboard To change the text that shows in SmartDashboard: 1. 3. with return $stringID.Advanced Captive Portal Configuration 2. open the file L10N. 2. Identity Sources Page 50 . To revert to regular viewing mode. Reload the Captive Portal in your web browser. See the highlighted text in step number 2 above. Go to Policy > Global Properties > SmartDashboard Customization.
5. Delete the word DEFAULT and type the new English text in the required field. Identity Sources Page 51 . Click OK. 6. Install the policy.Advanced Captive Portal Configuration 3. 4. Go to Identity Awareness > Portal Texts.
2. create a new locale entry with the syntax: "xx_XX" => "XName". 3.php 2. For example: "de_DE" => "German". 4.Advanced Captive Portal Configuration Adding a New Language You can configure the Captive Portal to show the Network Login pages in different languages. Identity Sources Page 52 . English is the only language entry in the list. Edit the language array for the new language locale. To configure a language for Captive Portal you must: 1. Make sure the text strings are shown correctly. After you set the language selection list. Then translate the strings in the new language file. you must create an entry in the supported languages file and create a new language file. add an entry to the supported languages file: 1. By default. Set the language selection list to show on the Network Login page. Save the files with UTF-8 encoding and move them to the correct location. For each new language. In the $arLanguages array. Use the English language file as a template to create new language files. Open the file: /opt/CPNacPortal/phpincs/conf/L10N/supported_languages. users can choose the language they prefer to log in with from a list at the bottom of the page. To create a new language. Editing the Language Array The supported language file contains entries for languages that you can see in the list on the Captive Portal page. It has a corresponding language file. 5.
To create a new language file: 1.php. You cannot use HTML special character sequences such as  .txt' file with UTF-8 as the encoding method and rename it to portal_xx_XX. make sure that the string's length is almost the same in size as the initial English string. When you configure additional languages. This is important to prevent breaks in the page layout. Save the file. When you translate a string. Copy the English language file: /opt/CPNacPortal/phpincs/conf/L10N/portal_en_US. but you must include all strings in the new language file. Showing the Language Selection List When you only use the English language. Remove these lines: <?PHP /* */?> You can find the first line a few lines above the language_selection string. Microsoft Word or a different editor to save the file with UTF-8 encoding. consult with technical support. Identity Sources Page 53 . portal_de_DE. Back up the file (for possible future revert). 3. open the file: /opt/CPNacPortal/phpincs/view/html/Authentication. On the Security Gateway. If this is not possible.php 2. To save a file with UTF-8 encoding: 1. replace the current file with the backup of the original file. The file contains the message strings. Use Notepad. Rename it to the new language using the syntax portal_xx_XX. It is not necessary to translate all strings. the language selection list does not show at the bottom of the Captive Portal Network Login page. 2. 5. 6. Find the language_selection string which is part of <label for="language_selection">. Move the file to /opt/CPNacPortal/phpincs/conf/L10N if it is not already there. When using Microsoft Word.php. To revert back to not showing the language selection list.php 3. Saving New Language Files You must save the language file with UTF-8 encoding.Advanced Captive Portal Configuration To disable a language: Comment out the line of the specific language or delete the line.php) as a template and refer to it for the source language. Creating New Language Files To create new language files.php 2. Translate the strings in the copied file. 4. To see the language list on the Network Login page: 1. You can find the second line about 20 lines below the language_selection string. / <. save the file as a '. use the English language file (portal_en_US. Captive Portal users can then select the language with which to log in. For example. / > in the translated strings. The language selection list will show on the Network Login page. you must show the language selection list on the Network Login page.
Make sure that the text is shown correctly on the Captive Portal pages. Identity Sources Page 54 . This section discusses the procedures necessary to generate and install server certificates. This certificate can be issued directly to the gateway. When an endpoint computer tries to connect to the gateway with the default certificate. From the gateway command line. certificate warning messages open in the browser. Server Certificates For secure SSL communication. Browse from different operating systems with different locale setups. because the gateway acts as a server to the clients. Check Point gateways. Run: cpopenssl req -new -out <CSR file> -keyout <private key file> -config $CPDIR/conf/openssl.+++ . All portals on the same Security Gateway IP address use the same certificate. or be a chained certificate that has a certification path to a trusted root certificate authority (CA). 3. Browse to the Captive Portal from a different browser and use a different font size. Browse to the Captive Portal and select the new language. 4.'. If you enter '. 1. Generating the Certificate Signing Request First. Note . There are quite a few fields but you can leave some blank. Obtaining and Installing a Trusted Server Certificate To be accepted by an endpoint computer without a warning.. The next sections describe how to get a certificate that is signed by a known certificate authority (CA) for a gateway. log in to expert mode. gateways must have a server certificate signed by a known certificate authority (such as Entrust. 2. the field will be left blank. You see this output: Generating a 2048 bit RSA private key . VeriSign or Thawte). gateways must establish trust with endpoint computers by showing a Server Certificate.cnf This command generates a private key.Advanced Captive Portal Configuration Making Sure the Strings Shows Correctly To make sure the strings show correctly: 1. generate a Certificate Signing Request (CSR). the administrator must install a server certificate signed by a trusted certificate authority. use a certificate created by the Internal Certificate Authority on the Security Management Server as their server certificate. What you are about to enter is what is called a Distinguished Name or a DN.+++ writing new private key to 'server1. 5. Fill in the data. by default.key' Enter PEM pass phrase: 3. 2. If private key files with the same names already exist on the machine. For some fields there will be a default value. The CSR is for a server certificate.This procedure creates private key files. You see this message: You are about to be asked to enter information that will be incorporated into your certificate request. Browsers do not trust this certificate.. Browse to the Captive Portal and select the English language. they are overwritten without warning. To prevent these warnings. Enter a password and confirm.
4. click the lock icon that is next to the address bar in most browsers. Keep the . 4. Install the policy on the gateway. 2. All other fields are optional. Make sure to request a Signed Certificate in PEM format.example. Send the CSR file to a trusted certificate authority. Sometimes it is in a separate file. click Import or Replace. log in to expert mode.key file that you generated in Generating the Certificate Signing Request (on page 54).The Repository of Certificates on the IPSec VPN page of the SmartDashboard gateway object is only for self-signed certificates. Generating the P12 File After you get the Signed Certificate for the gateway from the certificate Authority. This is the site that users access. 3. Define the IP address of the portal in the Portal Settings page for the blade. 1. If the signed certificate and the trust chain are in separate files.crt -inkey server1. use a text editor to combine them into one file.crt file to install the certificate with the *.com. a) Run: cpopenssl pkcs12 -export -out <output file> -in <signed cert chain file> -inkey <private key file> For example: cpopenssl pkcs12 -export -out server1. Use the *. Make sure that the . For example: portal. 1. The certificate that users see depends on the actual IP address that they use to access the portal. It does not affect the certificate installed manually using this procedure. Usually you get the certificate chain from the signing CA. If the signed certificate is in P12 or P7B format. 2.crt file contains the full certificate chain up to a trusted CA.key b) Enter the certificate password when prompted.Advanced Captive Portal Configuration The Common Name field is mandatory. To see the certificate when you connect to the portal. Get the Signed Certificate for the gateway from the certificate authority. From the gateway command line. generate a P12 file that contains the Signed Certificate and the private key. Import the new certificate to the gateway in SmartDashboard from a page that contains the Portal Settings for that blade. Viewing the Certificate To see the new certificate from a Web browser: The gateway uses the certificate when you connect with a browser to the portal. 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. Installing the Signed Certificate All portals on the same IP address use the same certificate. This field must have the Fully Qualified Domain Name (FQDN). Note . convert these files to PEM (Base-64) format. Identity Sources Page 55 .not only the IP address configured for the portal in SmartDashboard.p12 -in server1.key private key file.
Advanced Identity Agents Configuration Customizing Parameters You can change settings for Identity Agent parameters to control agent behavior. Whether to hide the client (the umbrella icon does not show on users' desktops). This lets you. prepackage the agent with the server address. Whether to disable the packet tagging feature that prevents IP spoofing.Advanced Identity Agents Configuration To see the new certificate from SmartDashboard: From a page that contains the portal settings for that blade. You can then have users download the Identity Agents from the Captive Portal or send them the installation through email.When you use prepackaging. for example. Prepackaging Identity Agent Installation Prepackaging refers to a procedure that lets you add configuration to the Identity Agents installation. 3. You can change some of the settings from SmartDashboard and some can be prepackaged with the agent. Click Configure. click the View button in the Certificate section. Click OK. 2. Unless you resign the installation with your own software signing certificate. 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. Identity Sources Page 56 . The Agent parameters are shown. Nac_agent_email_for_sending_logs Nac_agent_disable_quit Nac_agent_disable_tagging Nac_agent_hide_client 4. You can add a default email address for to which to send client troubleshooting information. users that download the agent through the Captive Portal will receive a notification saying that the installer is not signed. Note . For more information. Whether users can right click the Identity Agent client (umbrella icon on their desktops) and close the agent. Go to Identity Awareness > Agent. see Prepackaging Identity Agents (on page 77). Go to Policy > Global Properties > SmartDashboard Customization. the digital signature in the installer is invalidated. To change Identity Agents parameters in SmartDashboard: 1.
All traffic that flows is then inspected by the gateway. there is a need to deploy multiple security gateways at different network locations. Large scale enterprise deployment – In large scale enterprise networks. The identity information learned from the branch office gateways is shared between internal gateways to avoid unnecessary authentications. such as the perimeter firewall and multiple Data Centers. targeted to the Internet. You can deploy the security gateway at the remote branch offices to avoid malware threats and unauthorized access to the headquarters' internal network and Data Centers. You can control access to resources and applications with an identity-based access policy. however they are intensively used to provide access to wireless-enabled corporate devices and guests. Identity Awareness capability is centrally managed through the Security Management Server and SmartDashboard. deploy the security gateway inline in front of the Data Center. You can distribute the identity-based policy to all identity aware security gateways in the network. 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 close to the access network to avoid malware threats and unauthorized access to general resources in the global network. This section describes recommended deployment scenarios and options available with Identity Awareness. The perimeter security gateway can also control and inspect outbound traffic. Perimeter security gateway with Identity Awareness – This deployment scenario is the most common scenario. When you enable Identity Awareness at the branch office gateway you make sure that users are authenticated before they reach internal resources. Network segregation – The security gateway helps you migrate or design internal network segregation. You can deploy a security gateway enabled with Identity Awareness inline in front of the wireless switch. To do this. In this case. Page 57 .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. Distributed enterprise with branch offices – The distributed enterprise consists of remote branch offices connected to the headquarters through VPN lines. Data Center protection – If you have a Data Center or server farm. provide an identity aware access policy and inspect the traffic that comes from WLAN users. Wireless campus – Wireless networks are not considered secure for network access. you can protect access to the servers with the security gateway. Identity Awareness gives guests access by authenticating guests with the web Captive Portal. segregated from the users' network. 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. you can create an identity-based firewall security Rule Base together with Application Control. You can deploy the security gateway in transparent mode (bridge mode) to avoid significant changes in the existing network infrastructure.
bridges.Cluster members and bridges must be on SecurePlatform or IPSO. you must configure Identity Awareness with these components: One component that is deployed on the bridge's cluster member gateways. This deployment option is mostly suitable when you must deploy a gateway for network segregation and Data Center protection purposes. and Identity Awareness differently. The gateway members of a security cluster must have at least 5 interfaces. machines and networks) must connect to the same switch. One component that is deployed on a different gateway that serves as an external Identity Awareness gateway. you must configure the cluster members. The external Identity Awareness gateway. Both interfaces should be located and configured using different network subnets and ranges. It lets you deploy the gateway inline in the same subnet. rather than an IP router. Transparent mode – Known also as a "bridge mode". cluster interfaces and all identity sources (users. the gateway behaves as an IP router that inspects and forwards traffic from the Internet interface to the external interface and vice versa. Important .Deployment Options Deployment Options You can deploy a security gateway enabled with Identity Awareness in two different network options: IP routing mode Transparent mode (bridge mode) IP routing mode – This is a regular and standard method used to deploy Check Point security gateways. You usually use this mode when you deploy the gateway at the perimeter. The benefit of this method is that it does not require any changes in the network infrastructure. This deployment method lets you install the security gateway as a Layer 2 device.to communicate with the external Identity Awareness gateway. In this case. Advanced Deployment Page 58 . Configuring Clusters in Bridge Mode If you have clusters with a bridge in your environment. Due to bridge operations. 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) . We recommend SecurePlatform for full feature support.
Advanced Deployment Page 59 . where x is the Vlan number.Configuring Clusters in Bridge Mode Item Firewalls 1 Description R75 or higher Security Gateway on SecurePlatform . Vlan Vlan-x Preparing Clusters with a Bridge To prepare clusters with a bridge for Identity Awareness: 1.enabled with Identity Awareness (serves as the external Identity Awareness gateway) R75 or higher cluster member gateways on SecurePlatform . eth2) for a synchronization IP address.enabled with Identity Awareness Bridge interfaces (without IP addresses) 2 Interfaces Eth0 Eth1 Eth2 Eth3 Eth4 Sync interface Dedicated Management interface (DMI) Cluster interface (with IP address) The Vlan in the network. Create the cluster members on SecurePlatform. Each with an interface (for example.
2. 2. e) Enter n . eth4) for a cluster IP address. Select Share local identities with other gateways. Each with an interface (for example. Reboot the cluster members.Bridge d) Press spacebar to select the relevant interfaces (for example. run ifconfig. make sure that the bridge interfaces are not monitored. 3.if c) Manually add br0 and the bridge interfaces (eth0 and eth1) to this file. At the prompt. Create a Security Gateway object. Configure the bridge interface on the cluster members. In sysconfig: a) Enter 5 . 4. 5. Open SmartDashboard. 4.Network Connections b) Enter 1 . At the prompt. Continue with the sysconfig configurations and then reboot the cluster members.Add new connection c) Enter 3 . Open SmartDashboard. eth0 and eth1). 3. On each of the gateway members.Configuring Clusters in Bridge Mode Each with an interface (for example. In the Identity Awareness tab. eth3) for a management IP address. Checking the Bridge Configuration To make sure the bridge was configured correctly: 1. Click OK. Configuring the External Identity Awareness Gateway To configure the external Identity Awareness gateway: 1. run brctl show to see the interfaces attached to the bridge.cancel 3. Make sure you see an entry equivalent to the below. Enable the firewall Software Blade.next f) Enter c . type: a) cd $FWDIR/conf b) vi discntd. 2. Create a new cluster object: Advanced Deployment Page 60 . 2. 6. On each of the gateway members. Configuring the Cluster To configure the cluster: 1. select Enable Identity Awareness and select the relevant identity sources.
Do not select Not Defined. Open SmartDashboard Customization and click Configure. Microsoft Windows server with Active Directory. If the wizard opens. DNS and IIS (Web resource) Deploy the gateway inline in front of the protected resource. d) Click Get all members' topology with Topology. User host (Windows) 2. 6. the Windows server that runs IIS (web server). f) Disable Anti-spoofing. 3. Install IIS with a sample Web Server. b) Add the cluster members. Open Policy > Global Properties. Deploying a Test Environment If you want to evaluate how Identity Awareness operates in a security gateway. You do not see the bridge interfaces in SmartDashboard. 2. Deploy a security gateway either in routing or bridge mode. The recommended test setup below gives you the ability to test all identity sources and create an identity-based policy. Select Get identities from other gateways and select the gateway configured for the external component. Testing Identity Sources To configure the test environment: 1. 5. c) Open Topology > Edit Topology. 3. Configuring Cluster and Bridge Support To configure cluster and bridge support: 1. Open Firewall-1 > General and select the cxl_is_bridge option. Install the user host machine with Windows XP and 7 OS. Check Point security gateway R75 3. 4. You see the management interface. Click OK. Install Windows Server and configure Active Directory and DNS. The user host machine will access the protected resource via the security gateway. open Identity Awareness. sync interface and the cluster members. 4. Select Enable Identity Awareness and keep all options cleared. Click OK. The IP address of each member must be the management IP address. Advanced Deployment Page 61 .Deploying a Test Environment a) Enable the Firewall Software Blade. we recommend that you deploy it in a simple environment. In the cluster object. 2. 4. 3. e) Define a Cluster interface in the Network Objective column and give the cluster object a virtual IP address. cancel it. g) Make sure Network defined by the interface IP and net mask is selected. The recommendation is to install 3 main components in the setup: 1.
2. 12. 15. However. 9. Open SmartView Tracker > Identity Awareness section and check whether the user is authenticated using the AD Query method. access roles. 7. Access roles let you configure an identity aware policy together with Application Control to allow access only to specified user groups to the applications on the Internet. Open a browser and connect to the web resource. Create an Access Role and define access for all authenticated users or select users with the Users picker. Check logs. You should be redirected to the Captive Portal. Advanced Deployment Page 62 . use the user's credentials to authenticate and access the web resource. Controlling access to the allowed applications is possible through the Application Control blade. Install the client as requested by the Captive Portal. 13. Add the user host machine to the Active Directory domain. You are redirected to the Captive Portal. Testing Identity Agents Enable and configure Identity Agents and configure Identity Agents self provisioning via Captive Portal ("Configuring Agent Deployment from Captive Portal" on page 37). 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. you may require a more granular access policy that is based also on user and machine identity – i. 3. see Kerberos SSO Configuration (on page 71). Test connectivity between the host and the Windows server. Blocking all internal access may impact productivity of certain employees that must have access in the context of their daily work definition. 10. 8. 16. Enable Identity Awareness in the gateway. 14. 4. From the gateway's CLI revoke the authenticated user by: pdp control revoke_ip IP_ADDRESS 17.e. The SSO method using Kerberos authentication can be tested as well. On the user host machine open an Internet browser and try to connect to the web resource. Users located in the internal networks access the Internet resource and applications daily. Logout and login again from the user host machine. Deployment Scenarios Perimeter Security Gateway with Identity Awareness Security Challenge The security gateway at the perimeter behaves as a main gate for all incoming and outgoing traffic to and from your corporate network. Enter user credentials. Test connectivity. Not all Internet applications and web sites are secure and some are restricted according to corporate policy. Use the user host machine to test connectivity to the Web Server. The user and machine names show in the connections logs. When the client is installed wait for an authentication pop-up to enter the user's credentials via the client. Install policy. 6.Deployment Scenarios 5. 1. Follow the wizard and enable the AD Query and Captive Portal identity sources.
In this case Identity Awareness should be enabled on the perimeter security gateway.
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.
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
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.
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).
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.
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
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.
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.
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.
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.
Deployment Scenarios Network Segregation Security Challenge Networks consist of different network segments and subnets where your internal users reside. make sure that all gateways can connect to this domain controller. clear the Share local identities with other gateways option. the perimeter gateway. Deployment scenario We recommend that you deploy security gateways close to access networks before the core switch. 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. In the Identity Awareness tab. as well as authenticate users connecting to the servers and the Internet. If you want to share identities with one gateway. 2. Make sure that there is no proxy or NAT device between the gateways and the LAN. Then go to the perimeter gateway and select Get identities from other gateways. 4. If you want to use Identity Agents. If there is a general domain controller that serves all users across the segments. Each gateway of a particular segment authenticates users with the selected method. There is also a challenge of how to provide Advanced Deployment Page 66 . We recommend that you deploy the gateway in bridge mode to avoid network and routing changes. 5. for example. Access between the LAN and Data Center is controlled by the gateway. Access between the segments is controlled by the gateway. You want to make sure that only compliant users and machines can pass and connect across multiple network segments. Enable Identity Awareness on each gateway and select an appropriate identity source method. Access between the LAN and the Internet is controlled by the gateways either at each segment or at the perimeter gateway. 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. Deploy gateways in each segment in bridge mode. Configuration 1. then define the particular gateway’s DNS/IP in the agent gateway configuration per access segment. Make sure that the gateways can communicate with the Active Directory domain controller deployed in each segment (replicated domain controllers). Captive Portal or Identity Agents. 6. 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. 3. keep this option selected and disable Get identities from other gateways in the segment gateway. Either AD Query.
Deploy gateways inline at the Data Center. You can install the Data Center gateway in bridge mode to avoid changes to the existing network. as well as a perimeter gateway. Select a security gateway according to a performance guideline for your remote branch offices. When a user from a branch office attempts to connect to the Data Center. Define VPN site-to-site if necessary. 5. If you have Active Directory domain controllers replicated across your branch offices make sure that local gateways can communicate with the domain controller. 4. Deploy a gateway at the perimeter that protects the internal network in routing mode. We recommend using bridge mode. At remote branch offices. 7. At the corporate headquarters. the user is identified by the gateway at the headquarters Data Center without the need for additional authentication. we recommend that you deploy Data Center gateways to protect access to Data Center resources and applications. 4. 2. The perimeter gateway can serve as a VPN gateway for branch offices as well. 3. perimeter and Data Center gateway. The identities learned by the branch office gateways are then shared with the headquarters' internal and perimeter gateways. 3. Deploy the gateways at the branch offices in routing mode. 2. Deploy the remote branch gateways in IP routing mode and have them function as a perimeter firewall and VPN gateway. you can deploy low capacity gateways due to a relatively low number of users. Advanced Deployment Page 67 . In this scenario. Configuration 1. In case you do not have a local domain controller. establishing a VPN link to the corporate gateways. We recommend that you deploy security gateways at the remote branch offices and at headquarters in front of the Data Center and at the perimeter. 6. Create an access role and apply the roles in the security policy on the branch office gateways. users from the branch office are identified by the local branch office gateway before connecting to the corporate network over VPN. Enable Identity Awareness and select the appropriate methods to get identity.Deployment Scenarios authorized access to users that come from remote branch offices that request and want to access the Data Center and the Internet. 5. Deployment Scenario 1. make sure that the gateways can access the headquarters' internal domain controller over VPN.
Configuration 1. we recommend that you only configure a local domain controller list per site in the relevant gateways. Deployment Scenario 1. On the branch office gateway. Check that there is no NAT or proxy device between the gateway and the WLAN network. Advanced Deployment Page 68 . enable AD Query on all gateways. Wireless networks do not give a desired level of security in terms of network access. 3. 2. In the Gateway properties > Identity Awareness tab > Captive Portal Settings. since the identity information is shared between branch and internal gateways accordingly. select Unregistered guests login and in Settings. it is not intended for guests and contractors to install any endpoint agents on their devices. On the Data Center gateway. Furthermore. Identity Agents Recommended Configuration When using Identity Agents. guests and contractors. Wireless Campus Security Challenge You use wireless networks to grant access to employees that use Wi-Fi enabled devices. 2. Make sure that the gateway can communicate with the authentication server. 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. Wireless access is also intensively used to connect mobile devices such as smart phones where agents can be installed. Guests and contractors in some cases cannot use the corporate wired network connection and must connect through WLAN. Enable Identity Awareness on the gateway. by selecting these settings on the Identity Awareness tab: AD Query Recommended Configuration When you use AD Query to authenticate users from the local and branch offices.Deployment Scenarios 8. It is not necessary to configure all domain controllers available in the network. we recommend that you configure the local branch office gateway’s DNS/IP on the agent. Deploy the security gateway in bridge mode in front of the Wireless Switch. select the Active Directory domain controllers replications installed in the branch office only. 4. Make sure that the gateway can access the Internet or any other required resource in the network. These devices are not part of the Active Directory domain. such as Active Directory or RADIUS. select the fields you want guests to fill when they register. identities are shared with the internal headquarter gateways. Select Log out users when they close the portal browser. Select Captive Portal as an identity source. configure a list of domain controllers installed in the internal headquarters network. The agents connect to the local gateway and the user is authenticated. 4. For example. 3.
Deployment Scenarios Advanced Deployment Page 70 .
the user authenticates to a domain controller that provides an initial ticket granting ticket (TGT). When the user needs to authenticate against the Security Gateway with Identity Awareness. When a user logs in. Kerberos is the default authentication protocol used in Windows 2000 and above. encrypted data packets issued by a trusted authority which in this case is the Active Directory (AD). How SSO Operates Item A B C Description Domain Controller Data Center Security Gateway that Identity Agents connect to Page 71 . You get SSO in Windows domains with the Kerberos authentication protocol. This ticket vouches for the user’s identity. the Identity Agent presents this ticket to the domain controller and requests a service ticket (SR) for a specific resource (Security Gateway that Identity Agents connect to).Chapter 5 Kerberos SSO Configuration In This Chapter Overview How SSO Operates References SSO Configuration 71 71 72 73 Overview The Identity Awareness Single Sign-On (SSO) solution gives the ability to transparently authenticate users that are logged in to the domain. The Kerberos protocol is based on the idea of tickets. The Identity Agent then presents this service ticket to the gateway that grants access. This means that a user authenticates to the domain one time and has access to all authorized network resources without additional authentication.
mit.References Item 1 2 Description User logs in to the AD User gets an initial ticket (TGT) Item A B C 1 2 3 Description Domain Controller Data Center Security Gateway that Identity Agents connect to The Identity Agent connects to the Security Gateway The Security Gateway asks for user authentication The Identity Agent requests a service ticket (SR) for the Security Gateway that Identity Agents connect to and presents the TGT The AD sends a ticket (encrypting the user name with the shared secret between the AD and the Security Gateway that Identity Agents connect to) The Identity Agent sends the service ticket The Security Gateway that Identity Agents connect to decrypts the ticket with the shared secret and identifies the user The user gets access based on identity 4 5 6 7 References For detailed information on Kerberos SSO.microsoft.microsoft.com/enus/library/bb742433.aspx) Kerberos SSO Configuration Page 72 .com/en-us/library/bb742433.edu/Kerberos/ (http://web.edu/Kerberos/) http://technet. see these links: http://web.aspx (http://technet.mit.
open Active Directory Users and Computers (Start->Run->dsa.acme. SmartDashboard Configuration . Clear User must change password at next logon and select Password Never Expires.Creating an LDAP Account Unit and configuring it with SSO. AD Configuration Creating a New User Account 1. You can choose any username and password.com. Add a new user account.Creating a user account and mapping it to a Kerberos principal name. For example: a user account named ckpsso with the password 'qwe123!@#' to the domain corp. In Active Directory.SSO Configuration SSO Configuration SSO configuration includes two steps: AD Configuration . 3.msc) 2. Kerberos SSO Configuration Page 73 .
c) Run the suptools.msi files to a new folder on your AD server. For example. AD 2003 SP2 requires support tools for 2003 sp2: http://www. You need to open the command prompt as an administrator by right clicking it and selecting "run as an Administrator".ACME.com/downloads/details.checkpoint.com/downloads/details.cab and suptools.aspx?familyid=96A35011-FD83-419D-939B9A772EA2DF90&displaylang=en) b) Download the support. max.exe version on the AD.microsoft. 2. 2. It is part of the Windows 2000/2003 support tools. 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. If you’re using ActiveDirectory 2008.msi. If you are using Windows 2000/2003: a) Retrieve the correct executable from the Microsoft Support site (http://support.microsoft.qa.g.acme.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. Kerberos SSO Configuration Page 74 . the ktpass utility is already installed on your server and you can run the command line.com/) prior to installation. Open a command line to run the ktpass tool (Start > Run > cmd).aspx?familyid=96A35011-FD83-419D-939B9A772EA2DF90&displaylang=en (http://www.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.microsoft. At the command prompt. Use Ktpass 1.com@CORP. Retrieve the correct executable You must install the correct ktpass. Ktpass.com).exe is not installed by default in Windows 2000/2003.COM ckpsso qwe123@# The AD is ready to support Kerberos authentication for the Security Gateway. 1. run kptass with this syntax: C:> ktpass -princ ckp_pdp/domain_name@DOMAIN_NAME -mapuser username@domain_name -pass password -out unix. Ktpass is a command-line tool available in Windows 2000 and higher.
2. In the General tab of the LDAP Account Unit: a) Enter a name. SmartDashboard Configuration This section describes how to configure an LDAP Account Unit to support SSO.SSO Configuration Important . 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. Failure to do this will cause the authentication to fail. Configuring an Account Unit 1. select Microsoft_AD. Add a new host to represent the AD domain controller. b) In the Profile field. Enter a name and IP address for the AD object and click OK. Go to Network Objects tab > Nodes > Node > Host. Entering a value into this field will not affect existing LDAP Account Units.com ckpsso). It is highly recommended to fill this field for existing account units that you want to use for Identity Awareness. Click Active Directory SSO configuration and configure the values (see example): Kerberos SSO Configuration Page 75 . ADServer. For example. 3. 5.acme.e. Go to Servers and OPSEC Applications tab > Servers > New > LDAP Account Unit. c) In the Domain field. 4. d) Select CRL retrieval and User management. enter the domain name. Add a new LDAP Account Unit. set_spn –D ckp_pdp/corp.If you have used the ktpass utility before for the same principal name (ckp_pdp/domain_name@DOMAIN_NAME) but with a different account.
ckpsso. d) Enter the LDAP user password and confirm it. d) Enter the account password for that user (the same password you configured for the account username in AD) and confirm it. 7. select the AD object you configured in step 4 above. e) In the Check Point Gateways are allowed to section. f) In the Encryption tab. For example. In the Authentication tab. 8. select Use Encryption (SSL). fetch the fingerprint and click OK. f) Click OK. either skip step f or configure your domain controller to support LDAP over SSL.LDAP over SSL is not supported by default. Note . b) Click Fetch Branches to configure the branches in use. enter the login DN of a predefined user (added in the AD) used for LDAP operations. Kerberos SSO Configuration Page 76 . e) Leave the default settings for Ticket encryption method. select the AD object you configured in step 4 above. select Check Point Password in the Default authentication scheme and click OK. 6. In the Objects Management tab: a) In the Manage objects on field.ACME. c) Set the number of entries supported. For example. If you have not configured your domain controller to support LDAP over SSL. b) Enter the domain name.SSO Configuration a) Select Use kerberos Single Sign On. b) In the Host field. In the Servers tab: a) Click Add and enter the LDAP Server properties. CORP. select Read data from this server.COM c) Enter the account username you created in Creating a New User Account (on page 73). c) In the Login DN field.
The customization tool is called cpmsi_tool.msi Using the cpmsi_tool. Some of these parameters relate to the installation process and some relate to the actual operation of the agent.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 .msi Secure Platform installation CD .The installation process and the product configuration can be customized.exe The cpmsi_tool. Page 77 .exe and it is deployed with the agent (Program Files > Check Point > Identity Agent).exe Sample INI File 77 77 77 82 Background The Check Point Identity Agent has many advanced configuration parameters. There are 3 types of Identity Agents: Full agent – The Identity Agent is available for all users who use the computer. Custom . The Features section controls the installed features.in /linux/windows/Check_Point_Custom_Nac_Client.Chapter 6 Prepackaging Identity Agents In This Chapter Background Custom Identity Agent msi Using the cpmsi_tool. with packet tagging and machine authentication. 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. 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. To use it. The INI file is divided into 3 sections: The Properties section controls the installation process. The AddFiles section controls the deployed Identity Agent configuration.in /opt/CPNacPortal/htdocs/nac/nacclients/customAgent. You can use the template INI file for quick configuration. All of the configuration parameters have default values that are deployed with the product and can remain unchanged.
By default. FULL . the Custom Setup dialog box is shown (it is not hidden).Anyone who uses the computer SINGLEUSER . Configuring Installation .exe.exe /i <installation package name> SILENT=YES HIDEFEATURES=NO This command will start a silent installation where features are not hidden (even though for this type of installation this is irrelevant). For example. Note . INSTALLTYPE This property lets you can choose one of these installation type values: ALLUSERS .[Properties] Section You can configure these Identity Agent installation properties in the INI file: INSTALLUITYPE There are 3 values for this property: SILENT .An installation progress bar is shown while installation takes place. If this dialog box is hidden then the installation process behaves as if the user clicked Next without changing anything.The user sees a full installation user interface. This is the default value. Values for this property: Yes No .Using the cpmsi_tool.You can configure the Properties section properties using msiexec.No user interface is shown to the user.Only for the user who is installing the Identity Agent ASKUSER . the Choose Installation orientation dialog box is shown. By default. Prepackaging Identity Agents Page 78 . HIDEFEATURES This property determines the visibility of the Custom Setup (feature selection) dialog box in the installation process. BASIC .exe The tool has some other options that are not used for Identity Awareness. you can type: msiexec.Leaves the dialog box in the installation for the end user to decide.
PacketTagging This property relates to the Packet Tagging driver. if you set MADService=Yes then the feature dialog box will force install the Managed Asset Detection service.the dialog box is shown to the end user who can decide whether to install or not. Values: Yes No Ask . For example. or let users decide on their own. MADService This property relates to the Managed Asset Detection service. This property is required if you rules in the Rule Base that relate to machines. Prepackaging Identity Agents Page 79 . This is the default value. This driver signs every packet that is sent from the machine.[Features] Section You can configure the following properties and decide whether or not to install these features. This is a service that gives you machine authentication and enables managed asset detection prior to logon authentication.Using the cpmsi_tool.exe Configuring Installed Features .
the dialog box is shown to the end user who can decide whether to install or not. This is the default value.exe This setting is required if you have rules in the Rule Base that use Access Roles and are set to enforce IP spoofing protection on the Machines tab. Values: Yes No Ask . Prepackaging Identity Agents Page 80 .Using the cpmsi_tool.
2. Uncomment the DEF_FILE_NAME line in the INI file.Using the cpmsi_tool.reg file with the relevant parameters.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 does not exist the installation will fail. to send error logs to MYEmail and disable the agent's settings dialog box: [HKEY_LOCAL_MACHINE\SOFTWARE\C heckPoint\IA] "SendLogsTO"=MYEmail@checkpoint.reg file. 0 is the default value.reg file to the installation that lets you change the deployed Identity Agent configuration. you must: 1. 4 SendLogsTO String: <email Allows defining the default email addresses addresses to send logs to if an error occurs or if a delimited by ”. After you create the defs. Note .exe Configuring Deployed Identity Agents . The defs. 0 is the default value. For example. Copy it to the same directory as the installation package and the cpmsi_tool. Prepackaging Identity Agents Page 81 . 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.0 Automatic Server Discovery You can define a default gateway and trusted gateways by defining a defs. 3 HideGui DWORD:1. 2 DisableQuit DWORD:1.0 If the value is set to 1 then the quit button will not appear in the Identity Agent's tray menu.”> user chooses to send logs in from the agent’s status dialog box.[AddFiles] Section You can add a defs.com "DisableSettings"=dword:00000001 DisableSettings DWORD:1.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. 0 is the default value.If the defs.
Sample INI File Below is a sample INI file with the default configuration. Prepackaging Identity Agents Page 82 .Sample INI File For example: Note . the user will be asked to define the Security Gateway with Identity Awareness manually.If a default gateway is not defined and the automatic server discovery fails during installation.
it must discover the server and trust it. It also makes sure that communication between the client and the server was not tampered with by a Man In The Middle (MITM) attack. Server trust refers to the process of validating that the server the end user connects to is indeed a genuine one.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. For this to happen. We offer several methods for configuring server discovery – from a very basic method of simply configuring one server to a method of deploying a domain wide policy of connecting to a server based on your current location. Page 83 . Server discovery refers to the process of deciding which server the client should connect to. This section describes these options.
out-of-the-box situation). You can deploy the values before installing the client (by GPO. it will ask the user to verify that it is correct manually. Option Comparison Requires Deploy AD Trust Data File name based No No MultiSite No Client Remains Signed? Yes Allows Ongoing Changes No Level Recommended for. Note that as DNS isn’t secure. Prepackaging – You can create a prepackaged version of the client installation that includes the with the server IP and trust data.. including the server addresses and trust data reside in the registry.Server Discovery and Trust Options The trust process compares the server fingerprint calculated during the SSL handshake with the expected fingerprint. If the client does not have the expected fingerprint configured. This lets you use the configuration from first run. Single gateway deployments Very Simple Server Discovery and Trust Page 84 . Remote registry – All of the client configuration. During installation. Note that the user has to trust the server by himself (the trust dialog box opens). or any other system that lets you control the registry remotely). 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. AD based configuration – If client computers are members of an Active directory domain. any Identity Agent downloaded from the portal will be renamed to have the portal machine IP in it. DNS SRV record based server discovery – It is possible to configure the server addresses in the DNS server. the trust data cannot be configured in that way and the user will have to authorize it manually. This section describes the methods that allow the expected fingerprint to be known.. without user intervention. you can deploy the server addresses and trust data using a dedicated tool. the client uses this IP to represent the Security Gateway with Identity Awareness.
which works with no configuration. 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. and works out-of-the-box if the Captive Portal is also the Security Gateway with Identity Awareness. but the DNS can be changed Simple DNS based No No Partially Yes (per DNS server) Yes Simple Remote registry No Yes Yes Yes Yes Moderate Where remote registry is used for other purposes Advance d When both DNS and AD cannot be changed. If your deployment consists of one Security Gateway with Identity Awareness and a Captive Portal running on the same gateway and it is OK with you that the user needs to verify the server fingerprint and trust it once. Deployments with AD that you can modify Deployments without AD or with an AD you cannot modify. Server Discovery and Trust Page 85 .Option Comparison Requires Deploy AD Trust Data AD based Yes Yes MultiSite Yes Client Remains Signed? Yes Allows Ongoing Changes Yes Level Recommended for.
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
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
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
while the light agent installs itself to the users directory. the results are combined according to the specified priority (from the lowest to highest). and click ‘trust’ on the fingerprint verification dialog box.company.Option Comparison Note .com SRV service location: priority = 0 weight = 0 port = 443 svr hostname = idserver.0. That way.17 checkpoint_nac_server.e. you can deploy the Security Gateway with Identity Awareness addresses and trust parameters before installing the clients. 2. Server Discovery and Trust Page 89 ._tcp Server: dns. Install the client on one of your computers. and saves its configuration to HKEY_CURRENT_USER.1.ad.212 > Remote Registry If you have another way to deploy registry entries to your client computers (i.company.company. they will use the already deployed settings immediately after installation.168.If you configure AD based and DNS based configuration.com Address: 192. verify their fingerprints. Active Directory GPO updates). Troubleshooting .168.Displaying SRV Record Stored in the DNS Server Run the following commands: C:\> nslookup > set type=srv > checkpoint_nac_server. To use the remote registry option: 1._tcp.com idserver. 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. Connect manually to all of the servers that are configured.company.com internet address = 192. and saves its configuration to HKEY_LOCAL_MACHINE.
click next. (ii) FULL – User will have dialog boxes describing the installation and can cancel. under /opt/CPNacPortal/htdocs/nacclients. download the customAgent. 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. Any modification to the Identity Agents.[AddFiles] Section (on page 81) to create a registry file named defs.msi from your Security Gateway with Identity Awareness. 2. 3. 4. and will result in security warnings displayed to the user downloading them from the Captive Portal. If you need the client to choose a server based on the client location. see Prepackaging Identity Agents (on page 77). no other user interaction. finish. If you do not have an Identity Agent installed. You can use Identity Agent prepackaging feature to create a custom client version that comes bundled with the server addresses and trust data configured. you can click ‘Advanced’ and configure it that way.Option Comparison 3. To create a prepackaged version of the Identity Agent: 1.reg containing the server addresses and trust data you want to deploy. For more information. Prepackaging Identity Agents Prepackaging can be used to control client aspects other than server discovery and trust. Important . etc.The Identity Agents come digitally signed by Check Point Software Technologies Ltd. 4. (iii) SILENT – No UI will be shown. b) INSTALLTYPE Server Discovery and Trust Page 90 . 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. including prepackaging. Follow the instructions specified in Configuring Deployed Identity Agents . This section focuses mainly on server discover and trust aspects. Configure it manually to connect to the requested servers (Use the settings dialog box). install one (it does not necessarily need to be the custom agent). 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. will invalidate the signature. Export the following registry keys (from HKEY_LOCAL_MACHINE / HKEY_CURRENT_USER.
c) Click on the Captive Portal Settings button. run: cpmsi_tool customAgent. (Note: If you use another software distribution mechanism. d) Change the Require users to download value to Identity Agent . b) Go to the Identity Awareness page.Option Comparison (i) ALLUSERS – the client will be installed for any user running on the computer. you can distribute the modified customAgent. c) MADService (i) YES – Install the Managed Asset Detection Service (Requires administrative privileges).msi to your identification portal at /opt/CPNacPortal/htdocs/nacclients. 5. and configure the Captive Portal to distribute the custom agent. Installation will require administrative privileges. Server Discovery and Trust Page 91 . and you don’t have to upload it to your portal). (ii) SINGLEUSER – the client will be installed only for the installing user. Upload the modified customAgent. From the Identity Agent directory.msi readini package. No administrative privileges are needed. a) Under the Smart Dashboard.ini 6.Custom. (ii) NO – Do not install the Managed Asset Detection Service. d) PacketTagging (i) YES – Install the Packet Tagging driver (Requires administrative privileges) (ii) NO – Do not install the Packet Tagging driver. go to the Security Gateway with Identity Awareness.
Firewall Rule Base Example • 8 How Captive Portal Operates .Firewall Rule Base • 10 How SSO Operates • 71 How You Download an Identity Agent Example • 11 I Identity Agent Deployment Methods • 36 Identity Agent Types • 34 Identity Agents • 11 Identity Awareness Scenarios • 13 Identity Sources • 41 Important Information • 3 Install Database for a Log Server • 49 Installing the Signed Certificate • 55 Introduction • 6.Index A Access Role Objects • 29 Access Settings • 31 Acquiring Identities for Active Directory Users • 13 Acquiring Identities in Application Control • 20 Acquiring Identities with Identity Agents • 18 Acquiring Identities with the Captive Portal • 15 AD Based Configuration • 86 AD Configuration • 73 AD Query • 8 Adding a New Language • 52 Advanced AD Query Configuration • 41 Advanced Captive Portal Configuration • 49 Advanced Deployment • 57 Advanced Identity Agents Configuration • 56 Agent Access • 38 Agent Deployment from the Portal • 34 Agent Upgrades • 39 Authentication Settings • 32.[Properties] Section • 78 Configuring Installed Features . 57. 83 K Kerberos SSO Configuration • 71 L Large Scale Enterprise Deployment • 64 .[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 . 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 .
18 Using Access Roles • 15 Using Identity Awareness in the Application Control Rule Base • 29 Using Identity Awareness in the Firewall Rule Base • 28 Using the cpmsi_tool.Displaying SRV Record Stored in the DNS Server • 89 N Name and Password Login Settings • 33 Negate and Block • 31 Negate and Drop • 29 Network Segregation • 66 Non-English Language Support • 46 U Unregistered Guest Login Settings • 33 Use wbemtest to Verify WMI • 47 User Access • 33 User Experience • 16.M Making Sure the Strings Shows Correctly • 53 Mapping the User Account to a Kerberos Principal Name • 74 Multiple Gateway Environments • 46 T Testing Identity Agents • 62 Testing Identity Sources • 61 Troubleshooting • 47 Troubleshooting . 83 Server Discovery and Trust Options • 84 Session • 39 Setting Captive Portal to String ID Help Mode • 49 Showing the Language Selection List • 53 Single User Assumption • 45 SmartDashboard Configuration • 75 Source and Destination Fields • 30 Specifying Domain Controllers per Security Gateway • 42 SSO Configuration • 73 Page 94 .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. 21 Results of the Wizard • 26 S Sample INI File • 82 Saving New Language Files • 53 Scenario Guest Users from Unmanaged Device • 17 Identifying Users in Application Control Logs • 21 Identity Agent Deployment and User Group Access • 18 Laptop Access • 13 Recognized User from Unmanaged Device • 15 Server Certificates • 54 Server Discovery and Trust • 37. 17. 17. 19 User identification in the Logs • 21 User Identification in the Logs • 14. 19. 18.