Securing
This section describes 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.
- Encryption
  Encryption protects data from unauthorized access.
  - Encryption standards
    HCL Domino® observes a number of encryption standards, in particular, standards that are required or regulated by the Federal Information Processing Standard (FIPS).
  - Configuring encryption for ID files
    Any ID used with the current HCL Notes® client benefits from the strong security provided by AES encryption.
  - Mail encryption
    Mail encryption protects messages from unauthorized access. Only the body of a mail message is encrypted; the header information such as text in the To, From, and Subject fields is not.
  - Configuring the level of port encryption and authentication
    You can control the level of port encryption and authentication that is used on an HCL Domino® server.
  - Electronic signatures
    Electronic signatures are closely associated with encryption. An electronic signature verifies that the person who originated the data is the author and that no one has tampered with the data. Users can add an electronic signature to mail messages and to fields and sections of documents. A database designer controls whether or not users can sign fields and sections of a database can be signed; individual users can choose to sign mail messages.
- 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.

Configuring the level of port encryption and authentication

You can control the level of port encryption and authentication that is used on an HCL Domino® server.

About this task

If you install Domino® 9.01 Fix Pack 7 or a later fix pack, the following notes.ini settings are available:

PORT_ENC_ADV. Use this setting to control the level of port encryption and to enable the use of AES tickets.
TICKET_ALG_SHA. Use this setting to control which cryptographic algorithm to use when constructing tickets.

Use DEBUG_PORT_ENC_ADV=1 to see detail about the new algorithms and any errors encountered when using them.

Use LOG_AUTHENTICATION=1 to determine which authentication algorithms are being used. This setting is enhanced to contain information about the new algorithms and to be easier to interpret. For example:

Authenticate {E970014}: CN=Ultraviolet/O=MiniPax
           T:RC2:128 E:1:  P:c:e S:RC4:128 A:4:1 L:N:N:N FS:
Authenticate {BA6001C}: CN=Ultraviolet/O=MiniPax
           T:RC2:128 E:1:  P:t:e S:AES-CBC:128 A:2:1 L:N:N:N FS:
Authenticate {BA6000B}: CN=Ultraviolet/O=MiniPax
           T:AES:128 E:1:  P:t:e S:AES-GCM:256 A:2:1 L:N:N:N FS:DHE-2048

T shows the ticket algorithm and key size.

S shows the session (network encryption) algorithm and key size.

FS shows the algorithm (if any) used for Forward Secrecy.

E, P, A, and L are unchanged from previous releases.