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