Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities
on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export
laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses.
See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information
on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
This Novell® ZENworks® Endpoint Security Management Administration Guide is written for
ZENworks Endpoint Security Management Administrators who are required to manage the
Endpoint Security Management services, create security policies for the enterprise, generate and
analyze reporting data, and provide troubleshooting for end users. Instructions for completing these
tasks are provided in this manual.
The information in this guide is organized as follows:
Chapter 1, “ZENworks Endpoint Security Management,” on page 11
Chapter 2, “Policy Distribution Service,” on page 17
Chapter 3, “Configuring the Directory Service,” on page 21
Chapter 4, “Using the ZENworks Endpoint Security Management Service,” on page 37
Chapter 5, “Using the ZENworks Storage Encryption Solution Management Console,” on
page 41
Chapter 6, “Creating and Distributing Security Policies,” on page 75
novdocx (en) 17 September 2009
Chapter 7, “Managing the Endpoint Security Client 3.5,” on page 175
Chapter 8, “Managing the Endpoint Security Client 4.0,” on page 191
This guide is written for the ZENworks Endpoint Security Management administrators.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to the Novell Documentation Feedback site (http://www.novell.com/
documentation/feedback.html) and enter your comments there.
Additional Documentation
ZENworks Endpoint Security Management is supported by other documentation (in both PDF and
HTML formats) that you can use to learn about and implement the product. For additional
documentation, see the ZENworks Endpoint Security Management 3.5 documentation Web site
(http://www.novell.com/documentation/zesm35).
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
®
A trademark symbol (
trademark.
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
About This Guide9
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux*, should use forward slashes as required by your software.
Novell® ZENworks® Endpoint Security Management provides complete, centralized security
management for all endpoints in the enterprise. Because ZENworks Endpoint Security Management
applies security at the most vulnerable point, the endpoint, all security settings are applied and
enforced regardless of whether the user is connecting to the network directly, dialing in remotely, or
even not connecting to corporate infrastructure at all. This is critical to not only protect the data
within the corporate perimeter, but also to protect the critical data that resides on the endpoint device
itself.
ZENworks Endpoint Security Management automatically adjusts security settings and user
permissions based on the current network environment characteristics. A sophisticated engine is
used to determine the user's location and automatically adjusts firewall settings and permissions for
applications, adapters, hardware, etc.
Security is enforced through the creation and distribution of ZENworks Endpoint Security
Management security policies. Each location (Work, Home, Alternate, Airport, etc.) listed in a
security policy is assigned to a network environment (or multiple network environments). A location
determines which hardware is available and the degree of firewall settings that are activated within
the network environment. The firewall settings determine which networking ports, access control
lists (ACLs), and applications are accessible/required. Various integrity checks and scripts can be
run at location change to ensure that all required security software is up to date and running.
1
Figure 1-1 Effectiveness of NDIS-Layer Firewall
In securing mobile devices, ZENworks Endpoint Security Management is superior to typical
personal firewall technologies, which operate only in the application layer or as a firewall-hook
driver. ZENworks Endpoint Security Management client security is integrated into the Network
Driver Interface Specification (NDIS) driver for each network interface card (NIC), providing
security protection from the moment traffic enters the computer. Differences between ZENworks
Endpoint Security Management and application-layer firewalls and filter drivers are illustrated in
Figure 1-1, “Effectiveness of NDIS-Layer Firewall,” on page 11.
ZENworks Endpoint Security Management
11
Security decisions and system performance are optimized when security implementations operate at
the lowest appropriate layer of the protocol stack. With the ZENworks Security Management
Endpoint Security Client, unsolicited traffic is dropped at the lowest levels of the NDIS driver stack
by means of Adaptive Port Blocking (stateful packet inspection) technology. This approach protects
against protocol-based attacks, including unauthorized port scans, SYN Flood, NetBIOS, and
DDOS attacks.
The Endpoint Security Client is responsible for enforcement of the distributed security policies on
the endpoint system. When the Endpoint Security Client is installed on all enterprise computers,
these computers (endpoints) can now travel outside the corporate perimeter and maintain their
security, while endpoints inside the perimeter receive additional security checks within the perimeter
firewall.
Each Central Management component is installed separately, the following components are installed
on servers that are secured inside the corporate perimeter:
Policy Distribution Service: Responsible for the distribution of security policies to the
Endpoint Security Client, and retrieval of reporting data from the Endpoint Security Clients.
The Policy Distribution Service can be deployed in the DMZ or outside the enterprise firewall,
to ensure regular policy updates for mobile endpoints.
Management Service: Responsible for user policy assignment and component authentication;
reporting data retrieval, creation and dissemination of ZENworks Endpoint Security
Management reports; and security policy creation and storage.
Management Console: The visible user interface, which can run directly on the server hosting
the Management Service or on a workstation residing inside the corporate firewall with
connection to the Management Service server. The Management Console is used to configure
the Management Service and to create and manage user and group security policies. Policies
can be created, copied, edited, disseminated, or deleted using the Management Console.
1.2 System Requirements
novdocx (en) 17 September 2009
Server System RequirementsClient System Requirements
Windows 3.1 Installer
All Windows updates should be current
Standalone Management Control:
Supported RDBMS (SQL Server Standard, SQL
Server Enterprise, Microsoft SQL Server 2000
SP4, SQL 2005, SQL Express)
ZENworks Endpoint Security Management13
1.2.1 ASP.NET
The Policy Distribution and Management services require a LOCAL account of ASP.NET to be
enabled. If this is disabled, the services will not work correctly.
1.2.2 Reliable Time Stamp
The Novell ZENworks Endpoint Security Management solution gathers data from multiple sources
and collates this data to create a wide variety of security and audit reports. The utility and probative
value of these reports is greatly diminished if disparate sources disagree as to times, and so it is
strongly recommended that anyone installing ZENworks Endpoint Security Management provide
for enterprise-wide time synchronization (such as that provided by Active Directory* or through the
use of Network Time Protocol).
ZENworks Endpoint Security Management Administrators should follow all installation, operation,
and maintenance recommendations provided in this document and the ZENworks Endpoint Security
Management Installation Guide in order to ensure a strong security environment.
1.3 About the ZENworks Endpoint Security
novdocx (en) 17 September 2009
Management Manuals
The ZENworks Endpoint Security Management manuals provide three levels of guidance for the
users of the product.
ZENworks Endpoint Security Management Administration Guide: This guide is written for the
ZENworks Endpoint Security Management Administrators who manage the ZENworks
Endpoint Security Management services, create security policies for the enterprise, generate
and analyze reporting data, and provide troubleshooting for users. Instructions for completing
these tasks are provided in this manual. This is the guide you are currently reading.
installation instructions for the ZENworks Endpoint Security Management components and
assists the administrator in getting those components up and running.
ZENworks Endpoint Security Client 3.5 User Guide: This manual is written to instruct the end
user on the operation of the Endpoint Security Client running on Windows XP and Windows
2000. This guide can be sent to all employees in the enterprise to help them understand how to
use the Endpoint Security Client.
ZENworks Endpoint Security Client 4.0 User Guide: This manual is written to instruct the end
user on the operation of the Endpoint Security Client running on Windows Vista. This guide
can be sent to all employees in the enterprise to help them understand how to use the Endpoint
Security Client.
1.4 USB/Wireless Security
ZENworks USB/Wireless Security (UWS) is a simplified version of the product that provides
comprehensive USB control, connectivity security, and file encryption features. ZENworks USB/
Wireless Security does not include some of the additional security features that are available in
ZENworks Endpoint Security Management. If you have purchased USB/Wireless Security rather
than ZENworks Endpoint Security Management, all functionality described in this manual will be
essentially the same, with only certain policy features unavailable in the Management Console.
The unavailable features have been marked with the following notation on their respective pages:
NOTE: This feature is only available in the ZENworks Endpoint Security Management installation,
and cannot be used for USB/Wireless Security security policies.
Features without this notation are available for both ZENworks Endpoint Security Management and
UWS security policies.
To verify which version you are running, open the “About” screen from the Help menu in
Management Console (see Section 5.2, “Using the Console Menu Bar,” on page 43).
The Policy Distribution Service in Novell® ZENworks® Endpoint Security Management is a web
service application that, when requested, distributes security policies and other necessary data to
Endpoint Security Clients on endpoint computers in your enterprise. Endpoint Security Management
security policies are created and edited with the Management Service's Management Console, then
published to the Policy Distribution Service, from where they are downloaded by the client at checkin.
The following graphic illustrates the role of the Policy Distribution Service:
novdocx (en) 17 September 2009
2
The following sections contain additional information:
Section 2.1, “About the Policy Distribution Service,” on page 17
Section 2.2, “Securing Server Access,” on page 18
Section 2.3, “Running the Service,” on page 19
2.1 About the Policy Distribution Service
The Policy Distribution Service authenticates Endpoint Security Clients based on the user ID
credentials obtained from the Management Service, and supplies each client with the designated
security policy.
Reporting data is collected by Endpoint Security Clients and passed up to the Policy Distribution
Service. This data is periodically collected by the Management Service and then deleted from the
Policy Distribution Service.
The Policy Distribution Service does not initiate any communications with the other Endpoint
Security Management components, and only responds to others. It does not hold sensitive data in the
clear, nor does it hold the keys needed to decrypt the sensitive data. It does not hold user credentials
or any other user-specific data.
Section 2.1.1, “Server Selection and Installation,” on page 18
Section 2.1.2, “Server Maintenance,” on page 18
Section 2.1.3, “Upgrading the Software,” on page 18
Section 2.1.4, “Uninstall,” on page 18
Policy Distribution Service
17
2.1.1 Server Selection and Installation
See the ZENworks Endpoint Security Management Installation Guide for selection and installation
instructions.
2.1.2 Server Maintenance
It is recommended that regular disk cleanup tasks be configured to run on this server to remove
temporary files from the
generate an inordinate amount of temporary files that needlessly consume disk space.
Windows\temp
folder. Under extreme load conditions, Windows can
2.1.3 Upgrading the Software
To upgrade your software from one release to another, you must uninstall the old release and install
the new release. Complete instructions are provided in “Upgrading” in the ZENworks Endpoint
Security Management Installation Guide.
2.1.4 Uninstall
novdocx (en) 17 September 2009
To uninstall the Policy Distribution Service, use the Add/Remove Programs function in the
Windows Control Panel, or run the installation again from the ZENworks Endpoint Security
Management installation CD.
2.2 Securing Server Access
The following sections contain information to help you secure access to your ZENworks Endpoint
Security Management server:
Section 2.2.1, “Physical Access Control,” on page 18
Section 2.2.2, “Network Access Control,” on page 19
Section 2.2.3, “High Availability,” on page 19
2.2.1 Physical Access Control
Physical access to the Distribution Service Server should be controlled to prevent access by
unauthorized parties. Measures taken should be appropriate to the risks involved. There are multiple
available standards and guidelines available, including NIST recommendations, HIPAA
requirements, ISO/IEC 17799, and less formal collections of recommendations such as CISSP or
SANS guidelines. Even when a given regulatory frameworks is not applicable, it may still act as a
valuable resource and planning guide.
Likewise, Disaster Recovery and Business Continuity mechanisms to protect the Distribution Server
should be put in place to protect the server if an organizational risk assessment identifies a need for
such steps. The mechanisms best used will depend on the specifics of the organization and its
desired risk profile, and cannot be described in advance. The same standards and guidelines sources
listed above can be helpful in this decision as well.
The Distribution Server can be further protected from unauthorized access by restricting network
access to it. This may take the form of some or all of the following:
Restricting incoming connection attempts to those ports and protocols from which a valid
access attempt might be expected
Restricting outgoing connection attempts to those IP addresses to which a valid access attempt
might be expected
Restricting outgoing connection attempts to those ports and protocols to which a valid access
attempt might be expected
Such measures can be imposed through the use of standard firewall technology.
2.2.3 High Availability
High Availability mechanisms for the Distribution Server should be put in place if an organizational
risk assessment identifies a need for such steps. There are multiple alternative mechanisms for
building high availability solutions, ranging from the general (DNS round-robining, layer 3
switches, etc.) to the vendor specific (the Microsoft* web site has multiple resources on high
availability web services and clustering issues). Those implementing and maintaining a ZENworks
Endpoint Security Management solution should determine which class of high availability solution
is most appropriate for their context. Note that the Distribution Server has been architected to
function in non-high-availability situations, and does not require High Availability to provide its
services.
novdocx (en) 17 September 2009
2.3 Running the Service
The Policy Distribution Service launches immediately following installation, with no reboot of the
server required. The Management Console can adjust upload times for the Distribution Service
using the Configuration feature (see Section 5.3.1, “Infrastructure and Scheduling,” on page 44).
After you install ZENworks® Endpoint Security Management, you must create and configure a
directory service before you can start managing devices in your system.
The New Directory Service Configuration Wizard lets you create a directory service configuration
that defines the scope of your ZENworks Endpoint Security Management client installations. The
new configuration uses your existing directory service to define the logical boundary for your userbased and computer-based client installations.
The wizard guides you through the process of selecting the directory service and the containers
where current and future client accounts reside.
The wizard also lets you synchronize the directory entries included in the new configuration. This
synchronization is performed in the background so you can immediately begin using your new
configuration.
The following sections contain more information:
novdocx (en) 17 September 2009
3
Section 3.1, “Configuring the Directory Service for Novell eDirectory,” on page 21
Section 3.2, “Configuring the Directory Service for Microsoft Active Directory,” on page 28
3.1 Configuring the Directory Service for Novell
eDirectory
After installing ZENworks Endpoint Security Management, the New Directory Service
Configuration Wizard automatically displays. If you have just installed the product and the
Welcome page is displayed, skip to Step 4 in the following procedure.
To configure the directory service:
1 In the Management Console, click Too ls > Configuration.
2 Click Authenticating Directories.
3 Click New to launch the New Directory Service Configuration Wizard.
Configuring the Directory Service
21
novdocx (en) 17 September 2009
4 Click Next to display the Select Directory Service page.
5 Select Novell eDirectory as the directory service.
6 Specify a friendly name to describe the directory service configuration, then click Next to
display the Connect to Server page.
novdocx (en) 17 September 2009
7 Fill in the fields:
Host Name: Specify the DNS name or IP address of the directory server. If the DNS name
or IP address cannot be authenticated, a bind error message displays.
Port: Specify the port used to connect to the directory server.
Port 389 is the default. If you use a different port to connect to the directory server, you
can specify that port.
Enable Encryption for this Session using TLS/SSL: Select to enable encryption. If you
select this option, the port is automatically changed to 636.
8 Click Next to display the Provide Credentials page.
Configuring the Directory Service23
novdocx (en) 17 September 2009
9 Fill in the fields:
User name: Specify the account administrator to bind to the directory.
This account serves as the administrator of the directory service configuration. The login
name must be a user who has permission to view the entire directory tree. It is
recommended that this user be the OU administrator.
Password: Specify the password for the account administrator.
This account serves as the administrator of this directory service configuration.
The password should not be set to expire, and this account should never be disabled.
Context: Specify the context in which the account administrator is a member.
10 Click Next to display the Select Directory Partitions page.
11 Browse to and select the directory partitions for this configuration, then click Next to display
the Select Client Contexts page.
12 Browse to and select the context(s) for the accounts used in this configuration.
Configuring the Directory Service25
The Select Client Context(s) page lets you narrow the search to only those contexts that contain
managed users and computers, which improves performance.
Any client installation that attempts to check in with the management server the does not reside
in a selected context results in longer search times.
13 Click Next to display the Select Context(s) for Synchronization page.
novdocx (en) 17 September 2009
14 (Optional) Select the contexts to synchronize as part of the configuration process.
The synchronization is performed in the background so you can immediately begin using your
new configuration. If you have many users and computers to synchronize, this might take a few
hours.
If you do not specify contexts to synchronize, the users and computers in those contexts are
populated in the Management Console when they check in.
Synchronizing contexts pre-populates the Management Console with those users and
computers so that you can immediately perform actions such as creating security policies.
When the users or computers check in to the system, those policies are pushed down and
applied. By pre-populating the Management Console, you can immediately begin creating
policies that are specific to individual users or computers, rather than creating a policy that
applies to all users and computers in the context. If you do not synchronize the context, you
must wait until those users and computers check in to the system before creating unique
policies for different users or computers.
15 Click Next to display the Save Configuration page.
You can click Back to change any settings, if necessary.
17 Click Finish.
When you click Finish, the icon displays in your Windows notification area and the
synchronization begins. You can double-click the icon to display the Directory Services
Synchronization dialog box.
Configuring the Directory Service27
novdocx (en) 17 September 2009
The synchronization occurs in the background. If you exit the Management Console, the
synchronization stops. When you open the Management Console again, the synchronization
resumes where it left off.
3.2 Configuring the Directory Service for
Microsoft Active Directory
After installing ZENworks Endpoint Security Management, the New Directory Service
Configuration Wizard automatically displays. If you have just installed the product and the
Welcome page is displayed, skip to Step 4 in the following procedure.
To configure the directory service:
1 In the Management Console, click Too ls > Configuration.
2 Click Authenticating Directories.
3 Click New to launch the New Directory Service Configuration Wizard.