Home
Securing
This section describes IBM® Domino® security features, including execution control lists, IDs, and SSL.
SSL and S/MIME for clients
Clients can use a Domino® certificate authority (CA) application or a third-party CA to obtain certificates for secure SSL and S/MIME communication.
Pushing trusted certificates to Notes® clients
You can create cross-certificates in the Domino® Directory for Internet certifiers and Notes® certifiers and then push the cross-certificates to the Contacts application on Notes clients. The cross-certificates are used to establish client trust of a certifier when accessing servers, reading encrypted S/MIME mail, or installing signed Notes client plug-ins. When you push cross certificates, users are not required to create the cross-certificates or retrieve them from the Domino Directory.

Securing
This section describes IBM® Domino® security features, including execution control lists, IDs, and SSL.
- Overview of Domino security
  Setting up security for your organization is a critical task. Your security infrastructure is critical for protecting your organization's IT resources and assets. As an administrator, you need to give careful consideration to your organization's security requirements before you set up any servers or users. Up-front planning pays off later in minimizing the risks of compromised security.
- Server access for Notes® users, Internet users, and Domino® servers
  To control user and server access to other servers, Domino® uses the settings you specify on the Security tab in the Server document as well as the rules of validation and authentication. If a server validates and authenticates the Notes® user, Internet user, or server, and the settings in the Server document allow access, the user or server is allowed access to the server.
- The database access control list
  Every .NSF database has an access control list (ACL) that specifies the level of access that users and servers have to that database. Although the names of access levels are the same for users and servers, those assigned to users determine the tasks that they can perform in a database, while those assigned to servers determine what information within the database the servers can replicate. Only someone with Manager access can create or modify the ACL.
- Domino® server and Notes® user IDs
  Domino® uses ID files to identify users and to control access to servers. Every Domino server, Notes® certifier, and Notes user must have an ID.
- The execution control list
  You use an execution control list (ECL) to configure workstation data security. An ECL protects user workstations against active content from unknown or suspect sources, and can be configured to limit the action of any active content that does run on workstations.
- Domino® server-based certification authority
  You can set up a Domino® certifier that uses the CA process server task to manage and process certificate requests. The CA process runs as a process on Domino servers that are used to issue certificates. When you set up a Notes® or Internet certifier, you link it to the CA process on the server in order to take advantage of CA process activities. Only one instance of the CA process can run on a server; however, the process can be linked to multiple certifiers.
- SSL security
  Secure Sockets Layer (SSL) is a security protocol that provides communications privacy and authentication for Domino® server tasks that operate over TCP/IP.
- SSL and S/MIME for clients
  Clients can use a Domino® certificate authority (CA) application or a third-party CA to obtain certificates for secure SSL and S/MIME communication.
  - Setting up Notes® and Internet clients for SSL authentication
    You can set up Notes® or other Internet clients for server authentication to encrypt data and authenticate the server identity when connecting to an Internet server. You do not need an Internet certificate if you set up a client for server-only authentication.
  - Pushing trusted certificates to Notes® clients
    You can create cross-certificates in the Domino® Directory for Internet certifiers and Notes® certifiers and then push the cross-certificates to the Contacts application on Notes clients. The cross-certificates are used to establish client trust of a certifier when accessing servers, reading encrypted S/MIME mail, or installing signed Notes client plug-ins. When you push cross certificates, users are not required to create the cross-certificates or retrieve them from the Domino Directory.
    - Importing an Internet certifier into the Domino® Directory
      To prepare to set up Notes® clients to trust a third-party Internet certifier, first import the certifier into the Domino® Directory. The Internet certifier can be one that you purchase from a CA such as VeriSign or it can be a self-signed certificate that you create yourself using a tool such as the Key and Certificate Management Tool (keytool) provided with the Sun Java™ Software Development Kit (SDK). In either case, the certificate must be based on an RSA key algorithm or you will not be able to import it. If you create a self-signed certificate, remember to specify use of the RSA key algorithm.
    - Creating an Internet cross-certificate in the Domino Directory from a certifier document
      You can create a cross-certificate in the IBM® Domino® Directory for an Internet certificate. After completing this step, you can push the cross-certificate to IBM Notes® clients to establish trust of the certifier on the clients.
    - Pushing certificates to clients through security policy settings
      If you have created a cross-certificate in the Domino® Directory for an Internet certifier or Notes® certifier, you can use security policy settings to push it to Notes clients' Contacts. You can optionally push an Internet certifier too. Users can view the cross-certificate or certifier in Contacts but cannot edit or delete it.
    - How users can obtain trusted certificates manually
      The copy of the CA's certificate is called a trusted root certificate. After obtaining the trusted root certificate and -- if you are using a Notes® client -- an Internet cross-certificate for the root certificate, the client will trust the CA and by extension, any certificates issued by this CA. If you are setting up server authentication for an Internet client, you add this trusted root to a local file. If you are setting up server authentication for a Notes client, you add this trusted root to a Domino® Directory that users can access to generate a cross-certificate in their Contacts.
  - Internet certificates for SSL and S/MIME
    Before Internet and Notes® clients can use client authentication or send signed mail, they must have an Internet certificate. To send encrypted mail using S/MIME, they must have the recipient's Internet certificate.
  - Setting up Notes® clients for S/MIME
    You can set up an Notes® client to use S/MIME encryption and electronic signatures when sending mail to other users of mail applications that support S/MIME.
  - Setting up Notes® and Internet clients for SSL client authentication
    You can set up a Notes® or Internet client for client authentication with a server. You cannot use client authentication for SMTP and IIOP connections.
  - Setting up SSL for Notes® or Domino® using SMTP
    A Notes® client or Domino® server can act as an SMTP client when routing mail to an SMTP server. The Notes client or Domino server can use SSL to connect to a Domino server running the SMTP service or to another type of SMTP server. You cannot set up a Notes client or Domino server for SSL client authentication when connecting using SMTP.
  - Using SSL when setting up directory assistance for LDAP directories
    Directory assistance allows you to extend directory services from a server's primary Domino® Directory to other Notes® directories, such as secondary Domino Directories, and to remote LDAP directories. To set up directory assistance, you create a directory assistance database from the DA.NTF template, and then create Directory Assistance documents in the database to configure services for specific directories.
  - OCSP for X.509 certificate revocation checking
    The Online Certificate Status Protocol (OCSP) enables applications to determine the revocation state of an identified certificate. OCSP may be used to satisfy some of the operational requirements of providing more timely revocation information than is possible with certificate revocation lists (CRLs), and may also be used to obtain additional status information. An OCSP client issues a status request to an OCSP responder and suspends acceptance of the certificate in question until the responder provides a response.
- Encryption
  Encryption protects data from unauthorized access.
- Name-and-password authentication for Internet/intranet clients
  Name-and-password authentication, also known as basic password authentication, uses a basic challenge/response protocol to ask users for their names and passwords and then verifies the accuracy of the passwords by checking them against a secure hash of the password stored in Person documents in the Domino® Directory.
- Multi-server session-based authentication (single sign-on)
  Multi-server session-based authentication, also known as single sign-on (SSO), allows Web users to log in once to a Domino® or WebSphere® server, and then access any other Domino or WebSphere servers in the same DNS domain that are enabled for single sign-on (SSO) without having to log in again.
- Using Security Assertion Markup Language (SAML) to configure federated-identity authentication
  Federated identity is a means of achieving single sign-on, providing user convenience and helping to reduce administrative cost. In Domino® and Notes®, federated identity for user authentication uses the Security Assertion Markup Language (SAML) standard from OASIS.
- Using a credential store to share credentials
  In this release, the on-premises Domino® server can use a credential store application (credstore.nsf). The credential store is a secure repository for document encryption keys and other tokens necessary for Notes® client users to grant access to applications that use the OAuth (open authorization) protocol. OAuth allows user credentials to be shared with compliant applications so that users avoid extra password prompts.

Pushing trusted certificates to Notes® clients

You can create cross-certificates in the Domino® Directory for Internet certifiers and Notes® certifiers and then push the cross-certificates to the Contacts application on Notes® clients. The cross-certificates are used to establish client trust of a certifier when accessing servers, reading encrypted S/MIME mail, or installing signed Notes® client plug-ins. When you push cross certificates, users are not required to create the cross-certificates or retrieve them from the Domino® Directory.

About this task

There are two ways to push certificates to the Contacts application: through customization of the Notes® client installation media or through security policy settings. You can also push Internet certifiers to clients and enable users to create cross-certificates themselves. The security policy settings approach provides more flexibility because it allows you to more easily add, remove, or update certificates in Contacts after installation. For example, when you use security policy settings, if a certificate expires and you replace it with a new one in the Domino® Directory, you can cross-certify the new certificate and add the cross-certificate to the policy to automatically push it to clients. Or, if you revoke trust of a certificate by deleting its cross-certificate from the Domino® Directory, the cross-certificate is automatically deleted from Contacts.

Perform the following steps to push trusted certificates to clients:

Procedure

If you want to push trust of an Internet certifier, first import the certifier into the Domino® Directory.
Create cross-certificates in the Domino® Directory for any Internet and Notes® certifiers that you want clients to trust.
Use one of the following methods to push certificates to clients' Contacts:
- Customize the Notes® client install kit. For more information, see Customizing an install kit to set certifier and trust defaults.
- Configure security policy settings. For more information, see Pushing trusted certificates to clients through security policy settings.