Front cover - IBM Redbooks

150 Lotus Security Handbook
Channel security
When we say channel security, we mean that the session communication either
between a client and a server or between two servers is encrypted. This
generally means that SSL is required, although we have alternatives for securing
Notes client-to-Domino server and Domino server-to-Domino server using
Domino port encryption.
Data classification and access models
We briefly discussed data classification in Chapter 1, “Fundamentals of IT
security” on page 3. A key part of our interzone communication model is
dependent on using three different data classifications tied to different user
authentication types.
World-readable data access
The first data access model is for data which has been identified as public or
world-readable. A large portion of data falls into this category. The majority of the
data within your external sites does not require any formal authentication or
encryption based upon the “public” classification of the data. It does not mean we
need to allow anonymous access; however, without authentication, we do not
have a means to verify the identity of a user. We might want to note the IP
address the client appears to connect from, but it is for tracking purposes only.
There should be designated data access paths for each application. Data access
controls are consistent with those in the second and third data access models
except that no authentication is required and encryption is not used.
Simple authentication
The second model is to provide a method for the application to authenticate the
user using single-factor authentication. If the client is on the intranet network, no
encryption will be required. If the client is in any other zone, encrypt all follow-on
transactions for a session with Secure Sockets Layer (SSL). This capability is
required by applications which process sensitive data. In addition to simple
authentication and encryption, subsequent access to the application data is
provided through proxy servers and application-level access controls.
Strong authentication, encrypted data
The third, and most secure model, is to provide a method for the application to
authenticate the user and then to encrypt all follow-on transactions for a session
with Secure Sockets Layer (SSL). This capability is required by applications
which process customer’s sensitive or internal confidential data on the Internet.
In addition to strong authentication and encryption, subsequent access to the
application data is provided through proxy servers and application-level access
controls. Regardless of zone location, all confidential data will be stored on disk
using encryption at the highest key strength supported by the application.