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