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