Documenting The Site Survey - Red Hat DIRECTORY SERVER 8.1 - DEPLOYMENT Deployment Manual

Hide thumbs Also See for DIRECTORY SERVER 8.1 - DEPLOYMENT:
Table of Contents

Advertisement

For information about groups and roles, see
information about access controls, see
Making these decisions for each piece of directory data defines a security policy for the directory.
These decisions depend upon the nature of the site and the kinds of security already available
at the site. For example, having a firewall or no direct access to the Internet means it is safer to
support anonymous access than if the directory is placed directly on the Internet. Additionally, some
information may only need access controls and authentication measures to restrict access adequately;
other sensitive information may need to be encrypted within the database as it is stored.
In many countries, data protection laws govern how enterprises must maintain personal information
and restrict who has access to the personal information. For example, the laws may prohibit
anonymous access to addresses and phone numbers or may require that users have the ability to
view and correct information in entries that represent them. Be sure to check with the organization's
legal department to ensure that the directory deployment follows all necessary laws for the countries in
which the enterprise operates.
The creation of a security policy and the way it is implemented is described in detail in
Designing a Secure
Directory.

2.4. Documenting the Site Survey

Because of the complexity of data design, document the results of the site surveys. Each step of the
site survey can use simple tables to track data. Consider building a master table that outlines the
decisions and outstanding concerns. A good tip is to use a spreadsheet so that the table's contents
can easily be sorted and searched.
Table 2.4, "Example: Tabulating Data Ownership and Access"
access for each piece of data identified by the site survey.
Data Name
Owner
Employee
HR
name
User
IS
password
Home
HR
phone
number
Employee
IS
location
Office
Facilities
phone
number
Table 2.4. Example: Tabulating Data Ownership and Access
Each row in the table shows what kind of information is being assessed, what departments have
an interest in it, and how the information is used and accessed. For example, on the first row, the
employee names data have the following management considerations:
Chapter 4, Designing the Directory
Section 8.7, "Designing Access
Supplier
Self Read/
Server/
Write
Application
PeopleSoft
Read-only
Directory
Read/Write
US-1
PeopleSoft
Read/Write
Directory
Read-only
US-1
Phone
Read-only
switch
Documenting the Site Survey
Control".
identifies data ownership and data
Global
HR
Read
Writable
Yes
Yes
(anonymous)
No
No
No
Yes
Yes (must
No
log in)
Yes
No
(anonymous)
Tree. For
Chapter 8,
IS Writable
Yes
Yes
No
Yes
No
17

Advertisement

Table of Contents
loading

Table of Contents