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