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