Home
Securing
This section describes security features, including execution control lists, IDs, and TLS.
Encryption
Encryption protects data from unauthorized access.
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.
Using S/MIME format when sending encrypted mail to mobile device users
You can specify that encrypted mail sent to designated mobile device users such as Blackberry® users be converted to MIME and encrypted using S/MIME. This feature provides end-to-end encryption.

Securing
This section describes security features, including execution control lists, IDs, and TLS.
- 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.
- TLS security
  Transport Layer Security (TLS) is a security protocol that provides communications privacy and authentication for Domino® server tasks that operate over TCP/IP.
- TLS and S/MIME for clients
  Clients can use a Domino® certificate authority (CA) application or a third-party CA to obtain certificates for secure TLS 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.
    - Encrypting mail
      Encrypt outgoing, incoming, and saved mail to protect messages while they are in transit and stored in mail databases on the server. Users can encrypt outgoing mail messages sent to recipients who use either Notes® or S/MIME. If recipients prefer to receive mail in MIME format, then encrypted mail will be in S/MIME format. Users can encrypt incoming and saved mail only if they use Notes mail.
    - Configuring AES for mail and document encryption
      You can set up mail document encryption with AES through the use of a Security Settings document and a policy. You can also set AES encryption as the default method of encryption for S/MIME mail, with or without SHA-2 signing, using a NOTES.INI setting in a desktop policy.
    - Viewing the signing and encryption status of Notes® mail
      There is an icon on the status bar that indicates the signing and/or encryption status of an open Notes® mail message.
    - Using X.509 certificates for mail and document encryption
      You can set up the use of X.509 certificates for mail and document encryption for users who run Notes® 8.0.1 or later. Messages retain the Notes format and full message fidelity. This configuration is particularly useful when smart cards are used.
    - Using S/MIME format when sending encrypted mail to mobile device users
      You can specify that encrypted mail sent to designated mobile device users such as Blackberry® users be converted to MIME and encrypted using S/MIME. This feature provides end-to-end encryption.
  - 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.
- Time-based one-time password (TOTP) authentication
  When users log on to a Domino Web server, you can require that they provide time-based one-time passwords in addition to their user names and passwords.
- 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 OpenID Connect (OIDC) to configure federated-identity authentication
  Federated identity is a means of achieving single sign-on, providing user convenience and helping to reduce administrative cost. One way that client applications can authenticate users is by using an OpenID Connect (OIDC) provider.
- Using a credential store to store credentials
  A Domino® server can use a credential store application as a secure artifact repository. Examples of secure artifacts include authentication credentials and security keys.
- History of supported key sizes in Notes and Domino
  Understand the RSA key sizes supported by Notes® and Domino® from past releases to the current release.

Using S/MIME format when sending encrypted mail to mobile device users

You can specify that encrypted mail sent to designated mobile device users such as Blackberry® users be converted to MIME and encrypted using S/MIME. This feature provides end-to-end encryption.

About this task

To send S/MIME-encrypted mail to a mobile device user, the sender must use a Notes® 8.0.1 or later client. To decrypt the S/MIME-encrypted mail, a recipient's Person document must have the Use S/MIME format for incoming encrypted mail setting selected. In addition, the recipient must have an Internet certificate in the Domino® Directory that has been imported into the mobile device.

To specify users to receive encrypted mail in S/MIME format, perform the following steps:

Procedure

In the Domino® Administrator client, click People & Groups.
Select the names of the Blackberry users to receive S/MIME-encrypted mail.
Click Tools > People > Encryption Capabilities.
Select Use S/MIME format for incoming encrypted mail.
Optional: Select Only do so if no loss of fidelity in Notes RTF to MIME conversion.

If you select this option, the Notes® mail format and Notes® encryption are used instead if messages contain any of the following elements which lose fidelity when converted to MIME and S/MIME: action hotspots, embedded elements, objects, buttons, or stored forms. Messages that contain visual elements such as sections, page breaks, or highlighting are converted to S/MIME format regardless of this setting.

This option takes effect only if senders use Notes® 8.5 or higher clients. If you do not select this option, or if a sender uses a release earlier than Notes® 8.5, the sender sees a warning when sending a message that contains elements that would lose fidelity.

Results

The settings are added to the Encryption Capabilities section in the Administration tab of Person documents. To change the settings, use the Encryption Capabilities tool described previously.

Note: S/MIME format will also be used to encrypt unencrypted incoming mail if recipients have selected the security option When receiving unencrypted mail, encrypt before storing in your mailfile.