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