Front cover - IBM Redbooks

160 Lotus Security Handbook
The last step in our design model process is to analyze the design’s possible
data flows and data access to ensure the design meets our security policy. The
primary focus of the design validation review is to ensure:
1. Adherence to our flow control policy tables in the previous section. This
means that we need to examine all client-server and server-to-server network
data flows.
2. Data access methods used match the data classification assigned to the
data.
Next we will walk through an example of an application data flow review.
4.3.1 Data flow example
In this section we describe a fictitious infrastructure design that incorporates our
different security architecture concepts. The Acme company is designing a Web
portal for external suppliers. One part of the portal content is being served by a
Lotus Domino application. Other content will be provided by WebSphere
Application Server. The suppliers will be issued user IDs, and the credentials
(passwords) will be stored in an LDAP directory. Tivoli Access Manager will be
used for access controls to different portal content back-end URLs.
Based on the data classification policies at Acme, any data deemed “sensitive”
that is accessed from any network other than the internal network (Intranet) must
provide minimal access control of simple authentication with encryption. Data
deemed “confidential” that is accessed from any network other than the internal
network (Intranet) must provide minimal access control of strong authentication
with encryption. We have classified the supplier directory information as
“confidential,” and the portal content as “sensitive.”
Figure 4-11 depicts our logical architecture.