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