22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

314 Lotus Security Handbook<br />

modification of the data. Most directories are designed for significantly higher<br />

proportions of read-operations to write-operations.<br />

Points of control generally have access restrictions that limit or permit certain<br />

people, servers, or applications to perform write-operations. Points of control<br />

may be exclusive or non-exclusive. The levels of exclusivity can range from an<br />

entire directory to a single record, or even to a single attribute. For a point of<br />

control to be exclusive, not other point of control can overlap its scope of what<br />

data can be written.<br />

An example of an exclusive control point would be a process that generates a<br />

unique employee number. The process must have the sole ability to determine<br />

the value of this attribute, and no other interface could provide a means to modify<br />

it. This process might fall under the control of a superior process or interface that<br />

has the sole capability to add a new employee record.<br />

An example of a non-exclusive control point might be a person’s nickname<br />

attribute. The employee might have an interface and the ability to change it<br />

themselves, in addition to other people or groups who have interfaces and<br />

abilities to modify it, such as their manager and the HR staff.<br />

Points of control must be identified in terms of directory, records, and attributes.<br />

Each directory provides for various points of control, and the centralization or<br />

decentralization of control is usually configurable to several degrees by the<br />

implementer.<br />

8.2.3 Data management<br />

In the previous sections we discussed “who” can change data (the authoritative<br />

sources), and “where” it can be changed (the points of control). Data<br />

management is the coordination of both to avoid conflicts. Data management<br />

also includes the data administration viewed as a whole, with the goal being<br />

keeping the data accurate, current, and consistent. The challenges to achieving<br />

this goal often center around the existence of multiple, independent directories<br />

that are required to store identical or similar attributes.<br />

Separate directories inherently provide separate points of control, so when<br />

attributes overlap between any pairs of directories, the probability of data<br />

inconsistency becomes quite high. The likelihood of data consistency problems<br />

increases when the access to the different points of control is distributed to<br />

several groups of administrators. Data consistency between any pairs of<br />

directories can be improved by limiting the access to points of control to a<br />

centralized administration group, but when the points of control are not<br />

integrated, data often needs to be manually entered at each point of control.<br />

There is always an element of human error each time data needs to be manually

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!